/en/solusvm2/administrator-guide/high-availability/Recent content in High Availability on SolusVM DocumentationHugoenCopyright (c) 2020-2024 Thulite/en/solusvm2/administrator-guide/high-availability/overview/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/overview/High Availability recovers protected KVM virtual servers on a healthy compute resource in the same failover domain after a failure, using the shared-storage lock to confirm the failure and prevent false failover events. Requires Shared LVM (iSCSI) or NFS storage./en/solusvm2/administrator-guide/high-availability/how-high-availability-works/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/how-high-availability-works/The High Availability recovery process confirms a compute resource failure through the shared-storage lock, waits out the grace period, then places affected virtual servers on healthy compute resources in the same failover domain while preserving their disks and IP addresses./en/solusvm2/administrator-guide/high-availability/requirements-and-limitations/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/requirements-and-limitations/High Availability requires a failover domain with at least two KVM compute resources on Shared LVM (iSCSI) or NFS storage, plus spare CPU and memory for evacuation. Limitations cover the 2,000 compute resource cap, dedicated storage per domain, and unsupported Virtuozzo hosts./en/solusvm2/administrator-guide/high-availability/enabling-high-availability-globally/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/enabling-high-availability-globally/Enabling High Availability globally in Settings activates all failover domain configuration and sets the grace period (default 300 seconds, minimum 140) and maximum concurrent failures (default 3, minimum 1). Disabling it preserves failover domain and plan configuration./en/solusvm2/administrator-guide/high-availability/managing-failover-domains/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/managing-failover-domains/Failover domains group compute resources that recover each other’s virtual servers. Covers creating a domain with a location, network storage, at least two compute resources and matching IP blocks, reading the domain health summary, and disabling or deleting a domain./en/solusvm2/administrator-guide/high-availability/compute-resource-protection-status/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/compute-resource-protection-status/The HA Protection column reports each compute resource as Protected, At risk, Not protected, Eligible, Not eligible, Paused, or Unavailable. Maintenance mode excludes a compute resource from evacuation in both directions during planned hardware or software work./en/solusvm2/administrator-guide/high-availability/offering-high-availability-to-users/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/offering-high-availability-to-users/Include High Availability in a plan through the Offer high availability per CR checkbox and an optional percentage price, then enable it per virtual server from the Settings tab or the Edit Server form. The ha_priority API parameter sets recovery order from 0 to 65535./en/solusvm2/administrator-guide/high-availability/monitoring-high-availability-activities/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/monitoring-high-availability-activities/The High Availability Activities interface lists past and ongoing evacuation events with event statuses such as Pending, Running, and Partially evacuated, plus per-server statuses including Evacuating and Moved back. Webhooks notify when HA recovery starts and completes./en/solusvm2/administrator-guide/high-availability/recovering-after-a-failover-event/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/recovering-after-a-failover-event/After an evacuation event, High Availability never returns virtual servers automatically. Use Move back on the Activities interface once the source compute resource is online, retry failed migrations there, or delete an unrecoverable compute resource to avoid IP conflicts./en/solusvm2/administrator-guide/high-availability/troubleshooting-high-availability/Mon, 01 Jan 0001 00:00:00 +0000/en/solusvm2/administrator-guide/high-availability/troubleshooting-high-availability/Covers High Availability problems including evacuations that never trigger, enabling HA failing on NFS storage because the virtual server needs a storage lease, compute resources stuck in Not protected, virtual servers marked Not evacuated, and failed move back actions.