6.5.1
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
- 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
- Index
Prerequisites
Verify the interoperability of vCenter HA and the backup and restore solution. One solution is
vCenter Server Appliance le-based restore.
Procedure
1 Back up the Active node.
Do not back up the Passive node and Witness node.
2 Before you restore the cluster, power o and delete all vCenter HA nodes.
3 Restore the Active node.
The Active node is restored as a standalone vCenter Server Appliance.
4 Recongure the vCenter HA.
Remove a vCenter HA Configuration
You can remove a vCenter HA conguration from the vSphere Web Client. If you are using an Advanced
conguration, or if any of the nodes are not discoverable, you might have to perform additional cleanup
steps.
Procedure
1 Log in to the Active node vCenter Server Appliance and click .
2 Under select vCenter HA and click Edit.
3 Select Remove vCenter HA cluster.
n
The vCenter HA cluster's conguration 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 conguration.
n
If you performed conguration 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 conguration 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 specic 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.
vSphere Availability
72 VMware, Inc.