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
Table 2‑4. vSphere HA Advanced Options (Continued)
Option Description
das.reregisterrestartdisabledvms
When vSphere HA is disabled on a specific VM this option
ensures that the VM is registered on another host after a failure.
This allows you to power-on that VM without needing to re-
register it manually.
Note When this option is used, vSphere HA does not power on
the VM, but only registers it.
das.respectvmvmantiaffinityrules
Determines if vSphere HA enforces VM-VM anti-affinity rules.
The default value is "true" and rules are enforced even if
vSphere DRS is not enabled. In this case, vSphere HA does not
fail over a virtual machine if doing so violates a rule, but it issues
an event reporting there are insufficient resources to perform the
failover. This option can also be set to "false", whereby the rules
are not enforced.
See vSphere Resource Management for more information on
anti-affinity rules.
Note If you change the value of any of the following advanced options, you must disable and then re-
enable vSphere HA before your changes take effect.
n
das.isolationaddress[...]
n
das.usedefaultisolationaddress
n
das.isolationshutdowntimeout
Customize an Individual Virtual Machine
Each virtual machine in a vSphere HA cluster is assigned the cluster default settings for VM Restart
Priority, Host Isolation Response, VM Component Protection, and VM Monitoring. You can specify
specific behavior for each virtual machine by changing these defaults. If the virtual machine leaves the
cluster, these settings are lost.
Procedure
1 In the vSphere Client, browse to the vSphere HA cluster.
2 Click the Configure tab.
3 Under Configuration, select VM Overrides and click Add.
4 Use the + button to select virtual machines to which to apply the overrides.
5 Click OK.
vSphere Availability
VMware, Inc. 43