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
2 Right-click the virtual machine and select Fault Tolerance > Migrate Secondary.
3 Complete the options in the Migrate dialog box and confirm the changes that you made.
4 Click Finish to apply the changes.
The Secondary VM associated with the selected fault tolerant virtual machine is migrated to the specified
host.
Test Failover
You can induce a failover situation for a selected Primary VM to test your Fault Tolerance protection.
This option is unavailable (dimmed) if the virtual machine is powered off.
Procedure
1 In the vSphere Client, browse to the Primary VM for which you want to test failover.
2 Right-click the virtual machine and select Fault Tolerance > Test Failover.
3 View details about the failover in the Task Console.
This task induces failure of the Primary VM to ensure that the Secondary VM replaces it. A new
Secondary VM is also started placing the Primary VM back in a Protected state.
Test Restart Secondary
You can induce the failure of a Secondary VM to test the Fault Tolerance protection provided for a
selected Primary VM.
This option is unavailable (dimmed) if the virtual machine is powered off.
Procedure
1 In the vSphere Client, browse to the Primary VM for which you want to conduct the test.
2 Right-click the virtual machine and select Fault Tolerance > Test Restart Secondary.
3 View details about the test in the Task Console.
This task results in the termination of the Secondary VM that provided Fault Tolerance protection for the
selected Primary VM. A new Secondary VM is started, placing the Primary VM back in a Protected state.
Upgrade Hosts Used for Fault Tolerance
Use the following procedure to upgrade hosts used for Fault Tolerance.
Prerequisites
Verify that you have cluster administrator privileges.
vSphere Availability
VMware, Inc. 59