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
vCenter HA Clone Operation Fails During Deployment
If the vCenter HA configuration process does not create the clones successfully, you have to resolve that
cloning error.
Problem
Clone operation fails.
Note Cloning a Passive or Witness VM for a VCHA deployment to the same NFS 3.1 datastore as the
source Active node VM fails. You must use NFS4 or clone the Passive and Witness VMs to a datastore
different from the Active VM.
Cause
Look for the clone exception. It might indicate one of the following problems.
n
You have a DRS-enabled cluster, but do not have three hosts.
n
The host or database connection is lost.
n
Not enough disk space.
n
Other Clone Virtual Machine errors
Solution
1 Resolve the error that caused the problem.
2 Remove the cluster and start configuration again.
vCenter HA Deployment Fails with an Error
Deployment failures can be caused by configuration issues, especially problems with the networking
setup.
Problem
You start a vCenter HA cluster configuration, and it fails with an error. The error might show the cause of
the problem, for example, you might see an SSH Connection Failed message.
Solution
If deployment fails, take steps to resolve the network issues.
1 Verify that the Passive and Witness nodes can be reached from the Active node.
2 Verify that routing between the nodes is set up correctly.
3 Check network latency.
vSphere Availability
VMware, Inc. 89