Title here
Summary here
Compute Resource Protection Status
Overview
Go to Compute Resources to view the High Availability (HA) protection status of all compute resources in your cluster. This interface shows which compute resources HA protects, which ones are at risk, and which ones need attention.
High Availability Protection Status
The HA Protection column shows one of the following statuses for each compute resource:
| Status | Description |
|---|---|
 Protected | HA covers this compute resource. The system can evacuate its virtual servers in the event of a failure. |
 At risk | The compute resource does not have enough available resources, such as RAM, to guarantee the successful evacuation of all virtual servers. The system recalculates this status on a schedule and caches the result for 10 minutes, so the status can lag behind a recent capacity change by up to 10 minutes. |
 Not protected | HA does not currently protect this compute resource. For the possible causes and how to resolve them, see A compute resource shows “Not protected” HA status. |
 Eligible | This compute resource meets the High Availability requirements, and you can add it to a failover domain. |
 Not eligible | This compute resource does not meet one or more HA requirements, and you cannot add it to a failover domain. For example, compute resources that host VZ containers are not eligible because HA supports only KVM virtual servers. |
 Paused | You have disabled HA for this compute resource’s failover domain. See how to disable a failover domain. |
 Unavailable | The system cannot reach the compute resource, usually because the host is offline. This status can also appear temporarily while a compute resource joins or leaves a failover domain. |
Maintenance Mode
Use maintenance mode when you need to perform planned work on a compute resource, such as hardware upgrades or software updates, without triggering or interfering with HA events.
When you put a compute resource in maintenance mode, SolusVM excludes it from HA evacuation in both directions:
- The system does not select the compute resource as a destination for virtual server migration.
- If the compute resource goes down while in maintenance mode, the system does not trigger an HA evacuation event for the virtual servers it hosts.
Note:
Before you put a compute resource in maintenance mode, verify that the remaining compute resources in the failover domain have enough capacity to handle a failover. If capacity is insufficient, the At risk status appears for the affected virtual servers.
To enable or disable maintenance mode for a compute resource, use the Maintenance toggle on the Compute Resources interface. For more information, see Compute Resource Maintenance Mode documentation.