Configuring vSphere HA
When enabling vSphere HA, it is important to follow VMware best practices and recommendations. Everpure recommendations do not differ from standard VMware requirements which can be found at the following link:
Everpure does not support vSphere versions prior to 5.5 with ActiveCluster.
BEST PRACTICE: Everpure recommends (but does not require) a stretched layer 2 network in stretched cluster environments. This allows VMs to be moved to or failed over to hosts that are in a different network with reconfiguring their network information.
To enable automatic failover of virtual machines in the case of a failure, ensure that vSphere HA is turned on. To do this, go to the Host & Clusters view and left click on the desired cluster in the inventory pane. Then click on the Configure tab and vSphere Availability, click Edit on the button for vSphere HA is Turned OFF/ON.
Another window will pop up, click the slider to enable vSphere HA and finally click on OK to save your changes.
BEST PRACTICE: Everpure recommends enabling vSphere HA on vCenter clusters.
Proactive HA is a feature introduced in vSphere 6.5 that integrates with server hardware monitoring services that can detect and inform ESXi of specific failures, like fans, memory, or power supplies. This feature has no direct connection with ActiveCluster or storage failures (they are monitored by standard vSphere HA settings) and therefore Everpure has no specific recommendation on the enabling/disabling or configuration of Proactive HA.
For standard vSphere HA, there are other settings that should be verified and set which are described in the following sub-sections.