Overview

High Availability (HA) automatically recovers protected virtual servers when a compute resource fails. HA uses the shared-storage lock to confirm a failure and prevent false failover events. After HA confirms the failure and the grace period expires, it places the affected virtual servers on a healthy compute resource within the same failover domain.

A failover domain is a named group of compute resources that share storage and provide capacity for HA recovery.

This section explains how to enable the HA protection feature, create and configure a failover domain, and prepare compute resources for automatic failover during a failure.

In This Section#

The following documentation covers HA in reading order:

• How High Availability Works describes the recovery process and the conditions that trigger an evacuation.
• Requirements and Limitations lists what High Availability requires and what it does not support.
• Enabling High Availability Globally explains how to turn on the feature and configure the grace period and concurrent failure limit.
• Managing Failover Domains explains how to create, edit, disable, and delete failover domains.
• Compute Resource Protection Status describes each protection status and how to use maintenance mode.
• Offering High Availability to Users explains how to include High Availability in a plan and enable it per virtual server.
• Monitoring High Availability Activities describes the evacuation event log, its statuses, and webhook notifications.
• Recovering After a Failover Event explains how to move virtual servers back and retry a failed evacuation.
• Troubleshooting High Availability resolves the most common High Availability problems.

Before you offer HA protection to users, review the requirements and limitations.