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
5 Provide the IP address and subnet mask for the Passive and Witness nodes click Next.
You have to specify these IP addresses now even though the nodes do not exist yet. You can no
longer change these IP addresses after you click Next.
6 (Optional) Click Advanced if you want to override the failover management IP address for the
Passive node.
7 Leave the wizard window open and perform the cloning tasks.
What to do next
Create and Configure the Clones of the Active Node.
Create and Configure the Clones of the Active Node
As part of the Advanced configuration, you have to clone the Active node to create the Passive and
Witness nodes. Do not exit the Configure vCenter HA wizard while you perform the cloning tasks.
Procedure
1 Log in to the management vCenter Server, right-click the vCenter Server Appliance virtual machine
(Active node), and select Clone > Clone to Virtual Machine.
2 For the first clone, which will become the Passive node, enter the following values.
Option Value
New Virtual Machine Name Name of the Passive node. For example, use vcsa-peer.
Select Compute Resource
Select Storage
Use a different target host and datastore than for the Active node if possible.
Clone Options Select the Customize the operating system and Power on virtual machine
after creation check boxes and click the New Customization Spec icon on the
next page.
In the New Customization Spec wizard that appears specify the following.
a Use the same host name as the Active node.
b Ensure the timezone is consistent with the Active node. Keep the same
AreaCode/Location with UTC as the Active node. If you have not specified
AreaCode/Location with UTC while configuring the Active node, keep London
in AreaCode/Location during cloning. London has 0.00 offset, so it keeps the
clock to UTC without any offset.
c On the Configure Network page, specify the IP settings for NIC1 and NIC2,
which map to the management interface and the vCenter HA interface. Leave
the NIC2 Default Gateway blank.
vSphere Availability
VMware, Inc. 80