X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=ha-manager.adoc;h=d8489cb232652a4e2e0c04c30c8b3162749e4852;hp=6ebba70e2290082f861186fc437e6a478419e19b;hb=a9c77fec9239c1dd979bb0fd025a4d9186ae6449;hpb=fd9e89846d93099c3240124893a4708c39271842 diff --git a/ha-manager.adoc b/ha-manager.adoc index 6ebba70..d8489cb 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -105,15 +105,20 @@ hard and costly. `ha-manager` has typical error detection and failover times of about 2 minutes, so you can get no more than 99.999% availability. + Requirements ------------ +You must meet the following requirements before you start with HA: + * at least three cluster nodes (to get reliable quorum) * shared storage for VMs and containers * hardware redundancy (everywhere) +* use reliable “server” components + * hardware watchdog - if not available we fall back to the linux kernel software watchdog (`softdog`) @@ -291,13 +296,16 @@ the list of resources managed by `ha-manager`. A resource configuration inside that list look like this: ---- -: +: ... ---- -It starts with the service ID followed by a collon. The next lines -contain additional properties: +It starts with a resource type followed by a resource specific name, +separated with colon. Together this forms the HA resource ID, which is +used by all `ha-manager` commands to uniquely identify a resource +(example: `vm:100` or `ct:101`). The next lines contain additional +properties: include::ha-resources-opts.adoc[]