vSphere 6 which is in public beta now includes the following Improvements:
- Fault Tolerance in vSphere 6 will support 4 vCPUs;
- vSphere 6 will support cross vCenter vMotion;
- vSphere 6 long distance vMotion is enhanced;
- Using VMware NSX, network properties will now be vMotioned as well when using long distance vMotion.
VMware Fault Tolerance
First of all, VMware Fault Tolerance (FT) is going to support multiprocessor virtual machines. VMware FT allows continuous availability of multiprocessor virtual machines with literally zero downtime and zero data loss, even surviving server failures, while staying completely transparent to the guest software stack, requiring absolutely no configuration of in-guest software. This feature has been available from VMware vSphere 4 but it was only supported with single processor virtual machines. This has been the primary reason that VMware FT is seldom implemented.
Multiprocessor support for VMware FT has been the number one improvement for VMware FT requested by end-users.
With VMware vSphere 6 VMware FT will support 4 vCPU virtual machines.
VMware vMotion enhancements
vMotion is one the features which pushed VMware VI/vSphere into enterprise IT infrastructures. vMotion is the one feature which instantly shows the power of virtualization. From VMware VI to the latest vSphere 5.5, vMotion was only possible within the boundaries of the same Datacenter and vCenter. So vMotion could be performed in a single cluster and across clusters in the same Datacenter managed by a single vCenter Server.
With vSphere 6.0 it will be possible to perform a vMotion across vCenters Servers, across virtual switches, across long distances and routed vMotion networks aligning vMotion capabilities with larger data center environments. vMotion across vCenters will simultaneously change compute, storage, networks, and management. This leverages vMotion with unshared storage and will support local, metro and cross-continental distances.
When a VM moves across vCenters, HA properties are preserved and DRS anti-affinity rules are honoured. The standard vMotion compatibility checks are executed. Cross vCenter vMotion requires 250 Mbps network bandwidth per vMotion operation.
Before VMware vSphere 6, vMotion required Layer 2 connectivity for the vMotion network. With vSphere 6.0 vMotion can be performed using routed vMotion networks.
Another great addition in vSphere 6.0 is being able to do Long-distance vMotion. The idea is to be able to support cross-continental US distances with up to 100+ms RTTs while still maintaining standard vMotion guarantees. Use cases are:
- Disaster avoidance
- SRM and disaster avoidance testing
- Multi-site load balancing and capacity utilisation
- Follow-the-sun scenarios
You can also use Long-distance vMotion to live move virtual machines onto vSphere-based public clouds, including VMware VCHS now called vCloud Air.
VMware vSphere 6.jpg