6.7
Table Of Contents
- vSphere Availability
- Contents
- About vSphere Availability
- Business Continuity and Minimizing Downtime
- Creating and Using vSphere HA Clusters
- Providing Fault Tolerance for Virtual Machines
- How Fault Tolerance Works
- Fault Tolerance Use Cases
- Fault Tolerance Requirements, Limits, and Licensing
- Fault Tolerance Interoperability
- Preparing Your Cluster and Hosts for Fault Tolerance
- Using Fault Tolerance
- Best Practices for Fault Tolerance
- Legacy Fault Tolerance
- Troubleshooting Fault Tolerant Virtual Machines
- Hardware Virtualization Not Enabled
- Compatible Hosts Not Available for Secondary VM
- Secondary VM on Overcommitted Host Degrades Performance of Primary VM
- Increased Network Latency Observed in FT Virtual Machines
- Some Hosts Are Overloaded with FT Virtual Machines
- Losing Access to FT Metadata Datastore
- Turning On vSphere FT for Powered-On VM Fails
- FT Virtual Machines not Placed or Evacuated by vSphere DRS
- Fault Tolerant Virtual Machine Failovers
- vCenter High Availability
- Plan the vCenter HA Deployment
- Configure the Network
- Configure vCenter HA With the Basic Option
- Configure vCenter HA With the Advanced Option
- Manage the vCenter HA Configuration
- Set Up SNMP Traps
- Set Up Your Environment to Use Custom Certificates
- Manage vCenter HA SSH Keys
- Initiate a vCenter HA Failover
- Edit the vCenter HA Cluster Configuration
- Perform Backup and Restore Operations
- Remove a vCenter HA Configuration
- Reboot All vCenter HA Nodes
- Change the Appliance Environment
- Collecting Support Bundles for a vCenter HA Node
- Troubleshoot Your vCenter HA Environment
- Patching a vCenter High Availability Environment
- Using Microsoft Clustering Service for vCenter Server on Windows High Availability
Fault Tolerance Interoperability
Before configuring vSphere Fault Tolerance, you must be aware of the features and products Fault
Tolerance cannot interoperate with.
vSphere Features Not Supported with Fault Tolerance
When configuring your cluster, you should be aware that not all vSphere features can interoperate with
Fault Tolerance.
The following vSphere features are not supported for fault tolerant virtual machines.
n
Snapshots. Snapshots must be removed or committed before Fault Tolerance can be enabled on a
virtual machine. In addition, it is not possible to take snapshots of virtual machines on which Fault
Tolerance is enabled.
Note Disk-only snapshots created for vStorage APIs - Data Protection (VADP) backups are
supported with Fault Tolerance. However, legacy FT does not support VADP.
n
Storage vMotion. You cannot invoke Storage vMotion for virtual machines with Fault Tolerance turned
on. To migrate the storage, you should temporarily turn off Fault Tolerance, and perform the storage
vMotion action. When this is complete, you can turn Fault Tolerance back on.
n
Linked clones. You cannot use Fault Tolerance on a virtual machine that is a linked clone, nor can you
create a linked clone from an FT-enabled virtual machine.
n
Virtual Volume datastores.
n
Storage-based policy management. Storage policies are supported for vSAN storage.
n
I/O filters.
n
Disk encryption.
n
TPM.
n
VBS enabled VMs.
n
UPIT.
Features and Devices Incompatible with Fault Tolerance
Not all third party devices, features, or products can interoperate with Fault Tolerance.
For a virtual machine to be compatible with Fault Tolerance, the Virtual Machine must not use the
following features or devices.
vSphere Availability
VMware, Inc. 51