vMotion VM between vSphere clusters

vMotion VM between vSphere clusters

Few days ago I had discussion with one of my colleagues about possibility to migrate VM’s between vSphere clusters. I was trying to persuade him that is possible and I did that operation hundreds times, unfortunately unsuccessfully. I decided to write blog article to resolve all doubts.

vMotion VM between vSphere clusters – vSphere 4.X and vSphere 5.X

Yes, you can migrate VM’s between vSphere clusters (even between different versions) as long as below conditions are met:

[box type=”info”]

  1. vSphere clusters must be managed by single vCenter server
  2. vSphere clusters must be within single DataCenter object in vCenter server
  3. Pre vSphere 5.1 – clusters must have an access to the same datastore.
  4. vMotion network is stretched between clusters.
  5. Processors must be from the same vendor (Inter or AMD) and family (model) on both clusters or both clusters have common EVC baseline applied.
  6. Virtual Machine hardware version is supported by hypervisor – very useful during migration to new hardware or new version of vSphere platform.
  7. If you have vDS implemented, make sure dvportgroup is span across both clusters[/box]
Use case #1 – vMotion between two vSphere 4.1 clusters
  • Both CL01 and CL02 clusters are managed by single instance if vCenter server and under single DataCenter object in vCenter
  • All ESXi hosts from CL01 and CL02 clusters are connected to single datastore
  • Validation of Ubuntu01 VM vMotion between clusters CL02 and CL01 succeeeded.

  • vMotion completed successfully

  • After vMotion Ubuntu01 VM running on CL01 cluster.
As you can see, based on above use case it is possible to vMotion VM’s between clusters without any problems.
Use case #2 – vMotion between vSphere 4.1 and vSphere 5.1 clusters

Use case used for migration to new hardware or software version (e.g from vSphere 4.1 to vSphere 5.1)

  • vCenter VC01 has two clusters CL01 – vSPhere 5.1 and CL02 – vSphere 4.1

  • Cluster CL02 has two VM’s

  • vMotion two VM’s from CL02 to CL01, validation succeeded

  • vMotion successful

  •  both VM’s were vMotion’ed on CL01 – vSphere 5.1 – without outage

Artur Krzywdzinski

Artur is Consulting Architect at Nutanix. He has been using, designing and deploying VMware based solutions since 2005 and Microsoft since 2012. He specialize in designing and implementing private and hybrid cloud solution based on VMware and Microsoft software stacks, datacenter migrations and transformation, disaster avoidance. Artur holds VMware Certified Design Expert certification (VCDX #077).