Recently VMware Announced the vSphere 6.0 & its comes with the great imporvements and feature . The Most interesting feature i want  to share here with all of you, is Fault Tolerance, which breaks the barriers of single processor and now it can operate on max 4vCPU.Some more features i want to share are given below.

VMWARE-Fault-Tolerance-6.0[1]

The new technology used by FT is called Fast Checkpointing and is basically a heavily modified version of an xvMotion (cross-vCenter vMotion) that never ends and executes many more checkpoints (multiple/sec).

The benefits of Fault Tolerance are:

  • Protect mission critical, high performance applications regardless of OS
  • Continuous availability – Zero downtime, zero data loss for infrastructure failures
  • Fully automated response

The new version of Fault Tolerance greatly expands the use cases for FT to approximately 90% of workloads with these new features:

  • Enhanced virtual disk support – Now supports any disk format (thin, thick or EZT)
  • Now supports hot configure of FT – No longer required to turn off VM to enable FT
  • Greatly increased FT host compatibility – If you can vMotion a VM between hosts you can use FT

FT logging (traffic between hosts where primary and secondary are running) is very bandwidth intensive and will use a dedicated 10G nic on each host. This isn’t required, but highly recommended as at a minimum an FT protected VM will use more . If FT doesn’t get the bandwidth it needs the impact is that the protected VM will run slower.

Use cases

Any workload that has up to 4 vCPUs and 64GB Memory that is not latency sensitive (eg. VOIP & High-Frequency trading are not good candidates for FT). Note that vSphere 6.0 introduces the capability to use FT to protect VMs with more than 1 vCPU. In vSphere 5.5 and prior versions, only VMs with 1 vCPU could be protected by FT.

There is VM/Application overhead to using FT and that will depend on a number of factors like the application, number of vCPUs, number of FT protected VMs on a host, Host processor type, etc. We will release a performance paper around launch that will get into more specifics, for now the recommendation to customers is to test out using FT and see if it works for their workloads/use cases.

The new version of Fault Tolerance greatly expands the use cases for FT to approximately 90% of workloads.

The new technology used by FT is called Fast Checkpointing and is basically a heavily modified version of an xvMotion that never ends and executes many more checkpoints (multiple/sec). Also note that in versions prior to 6.0, FT required shared storage where both the Primary and Secondary copies of the FT-protected VM would share the same VMDK files. However, in vSphere 6.0 in order to add additional protection to the FT-protected VM, the Primary & Secondary VM use unique VMDK’s.

FT logging (traffic between hosts where primary and secondary are running) is very bandwidth intensive and will use a dedicated 10G nic on each host. This isn’t required, but highly recommended as at a minimum an FT protected VM will use more . If FT doesn’t get the bandwidth it needs the impact is that the protected VM will run slower.

Here are some more. :

VSPHERE FT 6.0 NEW CAPABILITIES

FT-Comparison[1]

Thanks for Reading ..

Leave a Reply