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
Procedure
1 Log in to the Active node vCenter Server Appliance and click Configure.
2 Under Settings select vCenter HA and click Edit.
3 Select Remove vCenter HA cluster.
n
The vCenter HA cluster's configuration is removed from the Active, Passive, and Witness nodes.
n
The Active node continues to run as a standalone vCenter Server Appliance.
n
You cannot reuse the Passive and Witness nodes in a new vCenter HA configuration.
n
If you performed configuration using the Advanced options, or if the Passive and Witness nodes
are not discoverable, you must delete these nodes explicitly.
n
Even if the second virtual NIC was added by the configuration process, the removal process does
not remove the virtual NIC.
Reboot All vCenter HA Nodes
If you have to shut down and reboot all nodes in the cluster, you must follow a specific shutdown order to
prevent the Passive node from assuming the role of Active node.
Procedure
1 Shut down the nodes in this order.
n
Passive node
n
Active node
n
Witness node
2 Restart each node.
You can restart nodes in any order.
3 Verify that all nodes join the cluster successfully, and that the previous Active node resumes that role.
Change the Appliance Environment
When you deploy a vCenter Server Appliance, you select an environment. For vCenter HA, Small,
Medium, Large, and X-Large are supported for production environments. If you need more space and
want to change the environment, you have to delete the Passive node virtual machine before you change
the configuration.
Procedure
1 Log in to the Active node with the vSphere Web Client, edit the cluster configuration, and select
Disable.
2 Delete the Passive node virtual machine.
vSphere Availability
VMware, Inc. 87