vSphere 6.0 not only comes with great scalability but also with a various new features, which unlocks your existing limitations with the vMotion. With the earlier versions of vSphere, vMotion requires an exact similar network configuration between the ESXi hosts and also at the vSwitch level. In previous versions of vSphere, we were not allowed to perform the vMotion between the vSphere distributed Switches. It was only limited within the dvswitch. with vSphere 6.0, vMotion is allowed across vSwitches and even vCenter Servers. Let’s take a detailed look at vSphere 6.0 vMotion enhancements.
vMotion Across Virtual Switches
vMotion is no longer restricted by the network configured with vSwitch. with vSphere 6.0, It is possible to perform vMotion across Virtual switches (Standard switch or Distributed Switch),Which transfers all the VDS port metadata during the vMotion. It is entirelytransparent to the Guest VM’s and No downtime is required to perform this vMotion operation across vSwitches. Only one requirement for the vMotion across vSwitches is that you should have L2 VM Connectivity.
With vSphere 6.0, It is possible to perform vMotion of VM’s in 3 different ways:
- vMotion of VMs from Standard switch to Standard switch (VSS to VSS)
- vMotion of VMs from Standard switch to Distributed Switch (VSS to VDS)
- vMotion of VMs from Distributed Switch to Distributed switch (VDS to VDS)
vMotion Across vCenter Servers
With vSphere 6.0, vMotion across vCenter server allows you to simultaneously change the Compute, Storage, Networks and management. It leverage the vMotion with unshared Storage. In simple terms, VM1 is running on certain Host/Cluster running on certain Datastore and managed by vCenter 1 can be vMotioned to different ESXi host having different datastores managed by another vCenter server called vCenter 2.
Requirement for vMotion Across vCenter Servers:
- Support for vMotion across vCenter server supports from vSphere 6.0 and later versions
- Destination vCenter server instance should havesame SSO domain as source vCenter and this operation is possible via UI. Using API, it is possible with different SSO domain.
- 250 Mbps network bandwidth per vMotion operation
Properties of vMotion Across vCenter Servers:
- Same VM UUID is maintained across vCenter Server instances
- All the VM related historical data like Events, Alarms and Tasks are preserved after the vMotion operation
- HA properties are Preserved and DRS anti-affinity rules are honored during the vMotion operation
Long Distance vMotion
With vSphere 6.0, vMotion for Long-Distance supports upto 100+ms RTTs(which was only 10 ms in previous versions). Long-Distance vMotion allows you to vMotion your VMs from one datacenter to other datacenter of your organization. Below are few of the use cases of the Long Distance vMotion:
- SRM/DA testing
- Permanent migrations
- Disaster avoidance
- Multi-site load balancing
- Migration between Datacenters or Cloud Platform
Network Requirements of Long Distance vMotion:
- All the vCenters servers must connect via Layer 3 Network.
- VM network should have L2 connectivity and same VM IP address available at destination location
- vMotion network should haveL3 connectivity and 250 MBps per vMotion Operation
- For NFC network,routed L3 through Management Network or L2 connection
- For Networking, L4-L7 services manuallyconfigured at destination