High Availability

high availability (ha) provides a built in backup node that keeps litmus edge running when the primary node goes down or is taken offline the secondary node stays in sync and takes over automatically if the primary fails to protect your configuration and state high availability works reliably even with low bandwidth or uncertain connectivity high availability gives you continuous data collection with predictable recovery times and less unplanned downtime after configuring ha, the system ensures that the backup node is not the same as the primary node (not the self) and checks for version compatibility and license status ha also provides handling for offline scenarios with either the primary node or backup node disabling and enabling high availability again when enabled, high availability performs a heartbeat check at 2 second intervals failover triggers when 3 consecutive missed heartbeats occur the system waits 6 seconds (2 seconds times 3) before initiating failover the failure count is recorded in a log file log files also record the current role, rsync success or failure, last sync timestamp, and heartbeat note high availability is available as a beta feature only enable high availability first enable the primary node, then enable the backup node, and finally provide backup information to the primary to enable high availability on the instance that you will use as the backup node navigate to system > high availability enable high availability configuration click configure as backup copy the hostname and token values to a text editor these values will not display again after you close this page click close on the instance that you will use as the primary node navigate to system > high availability paste the hostname and token values from the backup node into the backup hostname and backup token fields click save to save the configuration in the confirmation dialog, click enable high availability is now enabled