I tried to migrate my Microsoft clustered vritual machines to another server but failed due to SCSI bus-sharing conflict. The machine had to be switched off prior to vmotion.
Any idea as to what could be wrong with the vm/s?
Hello,
Could you let us know the version of ESX you are using? In general, however Microsoft Cluster components cannot be vMotioned as the vMotion breaks the SCSI bus-sharing. You instead fail over a node to the other node, shutdown and move the failed-node, then repeat. In many cases, you use SCSI Bus clustering to gain availability, which HA provides for you so there has always been a debate on using MSCS or not. Both forms of clustering have their uses and I have used both.
Best regards,
Edward L. Haletky
Communities Moderator, VMware vExpert,
Author: VMware vSphere and Virtual Infrastructure Security,VMware ESX and ESXi in the Enterprise 2nd Edition
Podcast: The Virtualization Security Podcast Resources: The Virtualization Bookshelf
Hello,
Could you let us know the version of ESX you are using? In general, however Microsoft Cluster components cannot be vMotioned as the vMotion breaks the SCSI bus-sharing. You instead fail over a node to the other node, shutdown and move the failed-node, then repeat. In many cases, you use SCSI Bus clustering to gain availability, which HA provides for you so there has always been a debate on using MSCS or not. Both forms of clustering have their uses and I have used both.
Best regards,
Edward L. Haletky
Communities Moderator, VMware vExpert,
Author: VMware vSphere and Virtual Infrastructure Security,VMware ESX and ESXi in the Enterprise 2nd Edition
Podcast: The Virtualization Security Podcast Resources: The Virtualization Bookshelf
how aditional information - http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100379...
Please, don't forget the awarding points for "helpful" and/or "correct" answers.
Mauro Bonder - Moderator
Hi,
The version used on the platform is ESX 3.5.0 207095.
Kindest regards,
Hi,
My environment runs on ESX 3.5 version.
Hello,
THank you for the version of ESX. The limitation on vMotion of clustered VMs still holds. I would investigate why you are clustering the VMs and whether ESX can fullfill that need, else you will have to do the shutdown, etc. A few things to check however:
1) Network Labels
2) Is the heartbeat network on the target box
3) Is the quorum lun available to the target box. You are using RDMs for Quorum?
4) the target box is also not already being used by a cluster node (that is NOT suggested as it uses a different mechanism)
There are quite a few caveats with clustered VMs.
Have you been through http://www.vmware.com/pdf/vsphere4/r41/vsp_41_mscs.pdf as that has some very good information on shared-disk-clusters.
Best regards,
Edward L. Haletky
Communities Moderator, VMware vExpert,
Author: VMware vSphere and Virtual Infrastructure Security,VMware ESX and ESXi in the Enterprise 2nd Edition
Podcast: The Virtualization Security Podcast Resources: The Virtualization Bookshelf
Hi, Guys. I have the same problem and using the same ESX version. I will try and check the points you said, however, I would like to get some updates from Chiloabt if his concerns have been fixed.