Product Features
System
High Availability
4 min
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 regular heartbeat checks at 2 second intervals when the threshold for consecutive missed heartbeats is reached, the system initiates failover (3 missed heartbeats) heartbeat activity, current role, rsync status, and sync timestamps are recorded in log files the following information displays on the primary node after you configure high availability last sent last heartbeat sent to the backup node last received last heartbeat received from the backup node consecutive failures number of consecutive missed heartbeats peer reachable whether the backup is reachable from the primary interval frequency of heartbeat signals in seconds failure threshold maximum number of missed heartbeats that trigger a backup 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