Configuring HA in Acropolis

  • 15 April 2020
  • 0 replies

Userlevel 3
Badge +4

Did you know that in Acropolis (AHV) you can enable high availability for the cluster to ensure that VMs can be migrated and restarted to another node in case of a failure?

Best effort VM availability is enabled by default in Acropolis.

Virtual Machine High Availability (VM HA)

VM HA is a feature designed to ensure that critical VMs are restarted on another Acropolis Hypervisor (AHV) host within the cluster if a host fails.




There are two VM high availability modes:

  • Default - This does not require any configuration and is included by default when an Acropolis Hypervisor-based Nutanix cluster is installed. When an AHV host becomes unavailable, VMs that were running on the failed AHV host are restarted on the remaining hosts, based on the available resources. Not all of the failed VMs will restart if the remaining hosts do not have sufficient resources.

  • Guarantee - This non-default configuration reserves space to guarantee that all failed VMs will restart on other hosts of the cluster during a host failure.

The Guarantee mode configuration will reserve resources to protect against either

  • One Acropolis host failure, if the cluster is configured for Nutanix Fault Tolerance 1 (Redundancy Factor 2).

  •  Up to two Acropolis host failures, if the Nutanix cluster is configured for Nutanix Fault Tolerance 2 (Redundancy Factor 3).

When a failed AHV host comes back online after a VM HA event, VMs that were previously running on the host will be migrated back to the original host to maintain data locality.

Check this article to know how to enable HA for Acropolis managed clusters.

Enabling high availability for the custer


To know more about HA in Acropolis check these links:

VM High Availability In Acropolis

Best Practices for Acropolis Hypervisor

This topic has been closed for comments