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:
- vSphere clusters must be managed by single vCenter server
- vSphere clusters must be within single DataCenter object in vCenter server
- Pre vSphere 5.1 – clusters must have an access to the same datastore.
- vMotion network is stretched between clusters.
- Processors must be from the same vendor (Inter or AMD) and family (model) on both clusters or both clusters have common EVC baseline applied.
- Virtual Machine hardware version is supported by hypervisor – very useful during migration to new hardware or new version of vSphere platform.
- If you have vDS implemented, make sure dvportgroup is span across both clusters
- See more at: http://vmwaremine.com/2012/10/21/vmotion-vm-between-vsphere-clusters/#sthash.gnFmHpcY.dpuf
Long
Distance VMotion
Requirements:
·
An IP network with a minimum bandwidth of 622 Mbps is
required.
·
The maximum latency between the two VMware vSphere servers cannot
exceed 5 milliseconds (ms).
·
The source and destination VMware ESX servers must have a private
VMware VMotion network on the same IP subnet and broadcast domain.
·
The IP subnet on which the virtual machine resides must be
accessible from both the source and destination VMware ESX servers. This
requirement is very important because a virtual machine retains its IP address
when it moves to the destination VMware ESX server to help ensure that its
communication with the outside world (for example, with TCP clients) continues
smoothly after the move.
·
The data storage location including the boot device used by the
virtual machine must be active and accessible by both the source and
destination VMware ESX servers at all times.
·
Access from VMware vCenter, the VMware Virtual Infrastructure (VI)
management GUI, to both the VMware ESX servers must be available to accomplish
the migration.
