-[[chapter-ha-manager]]
+[[chapter_ha_manager]]
ifdef::manvolnum[]
-PVE({manvolnum})
-================
+ha-manager(1)
+=============
include::attributes.txt[]
+:pve-toplevel:
NAME
----
ha-manager - Proxmox VE HA Manager
-SYNOPSYS
+SYNOPSIS
--------
include::ha-manager.1-synopsis.adoc[]
DESCRIPTION
-----------
endif::manvolnum[]
-
ifndef::manvolnum[]
High Availability
=================
include::attributes.txt[]
+:pve-toplevel:
endif::manvolnum[]
-
Our modern society depends heavily on information provided by
computers over the network. Mobile devices amplified that dependency,
because people can access the network any time from anywhere. If you
* optional hardware fencing devices
+[[ha_manager_resources]]
Resources
---------
a watchdog reset.
+[[ha_manager_fencing]]
Fencing
-------
unresponsive node and as a result a chain reaction of node failures in the
cluster.
+[[ha_manager_groups]]
Groups
------
group. If no group node member is available the resource will be
placed in the stopped state.
Example;;
- A Service can run just on a few nodes, as he uses resources from only found
- on those, we created a group with said nodes and as we know that else all
- other nodes get implicitly added with lowest priority we set the restricted
- option.
+ Lets say a service uses resources only available on `node1` and `node2`,
+ so we need to make sure that HA manager does not use other nodes.
+ We need to create a 'restricted' group with said nodes:
+[source,bash]
+ ha-manager groupset mygroup -nodes "node1,node2" -restricted
nofailback::
Examples;;
* You need to migrate a service to a node which hasn't the highest priority
in the group at the moment, to tell the HA manager to not move this service
- instantly back set the nofailnback option and the service will stay on
+ instantly back set the 'nofailback' option and the service will stay on
+ the current node.
- * A service was fenced and he got recovered to another node. The admin
- repaired the node and brang it up online again but does not want that the
+ * A service was fenced and it got recovered to another node. The admin
+ repaired the node and brought it up online again but does not want that the
recovered services move straight back to the repaired node as he wants to
first investigate the failure cause and check if it runs stable. He can use
- the nofailback option to achieve this.
+ the 'nofailback' option to achieve this.
Start Failure Policy
* *after* you fixed all errors you may enable the service again
+[[ha_manager_service_operations]]
Service Operations
------------------