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
vSphere HA and DRS Affinity Rules
If you create a DRS anity rule for your cluster, you can specify how vSphere HA applies that rule during a
virtual machine failover.
The two types of rules for which you can specify vSphere HA failover behavior are the following:
n
VM anti-anity rules force specied virtual machines to remain apart during failover actions.
n
VM-Host anity rules place specied virtual machines on a particular host or a member of a dened
group of hosts during failover actions.
When you edit a DRS anity rule, select the checkbox or checkboxes that enforce the desired failover
behavior for vSphere HA.
n
HA must respect VM rules during failover -- if VMs with this rule would be placed
together, the failover is aborted.
n
HA should respect VM to Host rules during failover --vSphere HA aempts to place VMs
with this rule on the specied hosts if at all possible.
N vSphere HA can restart a VM in a DRS-disabled cluster, overriding a VM-Host anity rules
mapping if the host failure happens soon (by default, within 5 minutes) after seing the rule.
Other vSphere HA Interoperability Issues
To use vSphere HA, you must be aware of the following additional interoperability issues.
VM Component Protection
VM Component Protection (VMCP) has the following interoperability issues and limitations:
n
VMCP does not support vSphere Fault Tolerance. If VMCP is enabled for a cluster using Fault
Tolerance, the aected FT virtual machines will automatically receive overrides that disable VMCP.
n
VMCP does not detect or respond to accessibility issues for les located on vSAN datastores. If a virtual
machine's conguration and VMDK les are located only on vSAN datastores, they are not protected
by VMCP.
n
VMCP does not detect or respond to accessibility issues for les located on Virtual Volume datastores. If
a virtual machine's conguration and VMDK les are located only on Virtual Volume datastores, they
are not protected by VMCP.
n
VMCP does not protect against inaccessible Raw Device Mapping (RDM)s.
IPv6
vSphere HA can be used with IPv6 network congurations, which are fully supported if the following
considerations are observed:
n
The cluster contains only ESXi 6.0 or later hosts.
n
The management network for all hosts in the cluster must be congured with the same IP version,
either IPv6 or IPv4. vSphere HA clusters cannot contain both types of networking conguration.
n
The network isolation addresses used by vSphere HA must match the IP version used by the cluster for
its management network.
n
IPv6 cannot be used in vSphere HA clusters that also utilize vSAN.
vSphere Availability
26 VMware, Inc.