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
n
Use deterministic teaming policies to ensure particular traffic types have an affinity to a particular NIC
(active/standby) or set of NICs (for example, originating virtual port-id).
n
Where active/standby policies are used, pair traffic types to minimize impact in a failover situation
where both traffic types will share a vmnic.
n
Where active/standby policies are used, configure all the active adapters for a particular traffic type
(for example, FT Logging) to the same physical switch. This minimizes the number of network hops
and lessens the possibility of oversubscribing the switch to switch links.
Note FT logging traffic between Primary and Secondary VMs is unencrypted and contains guest network
and storage I/O data, as well as the memory contents of the guest operating system. This traffic can
include sensitive data such as passwords in plaintext. To avoid such data being divulged, ensure that this
network is secured, especially to avoid 'man-in-the-middle' attacks. For example, you could use a private
network for FT logging traffic.
Homogeneous Clusters
vSphere Fault Tolerance can function in clusters with nonuniform hosts, but it works best in clusters with
compatible nodes. When constructing your cluster, all hosts should have the following configuration:
n
Common access to datastores used by the virtual machines.
n
The same virtual machine network configuration.
n
The same BIOS settings (power management and hyperthreading) for all hosts.
Run Check Compliance to identify incompatibilities and to correct them.
Performance
To increase the bandwidth available for the logging traffic between Primary and Secondary VMs use a
10Gbit NIC, and enable the use of jumbo frames.
You can select multiple NICs for the FT logging network. By selecting multiple NICs, you can take
advantage of the bandwidth from multiple NICs even if all of the NICs are not dedicated to running FT.
Store ISOs on Shared Storage for Continuous Access
Store ISOs that are accessed by virtual machines with Fault Tolerance enabled on shared storage that is
accessible to both instances of the fault tolerant virtual machine. If you use this configuration, the CD-
ROM in the virtual machine continues operating normally, even when a failover occurs.
Avoid Network Partitions
A network partition occurs when a vSphere HA cluster has a management network failure that isolates
some of the hosts from vCenter Server and from one another. See Network Partitions. When a partition
occurs, Fault Tolerance protection might be degraded.
vSphere Availability
VMware, Inc. 61