← Back to Articles
Enable or disable Auto Failback
Last Updated: July 07, 2026
The Auto Failback option is available only when you create N:1 (hot_cold) redundancy cluster. Enabling Auto Failback ensures that the Initial Active Server recovers from a failure, the system automatically transitions back from the Standby Server to the initially Active Server.
The Initial Active Server becomes eligible for auto failback after it has been recovered from one the following conditions:
  • A failed NIC and/or link
  • Restarted any failed software containers or processes
  • Re-established Heartbeat messages
  • Has no alarms present that would affect the server becoming fully operational, such as loss of link or interface
  • Loss of heartbeat

Suspending the RC shall prevent Auto Failback, if the Standby server has taken over another Initial Active server. For more information, see Enable or disable suspension on redundancy cluster.

Use the Auto Failback Delay parameter to control the time period to wait before auto-failing back once the active server has been recovered. The Auto Failback Delay period (or time to wait before failback) is measured from the time the Initially Active server has been recovered.

NOTE: Before you begin, ensure you suspend the cluster before you modify or edit a cluster.
  1. Login to Element Manager, https://<VPS #2_IP_address>:5557.
  2. Click RC-Server on the left navigation pane.
  3. Under Redundancy Cluster, view the list of the clusters available in the system.
  4. Click the ellipsis menu (More options button) of the corresponding redundancy cluster.
  5. Click Suspend/Un-suspend from the pull-down list. Click Yes to confirm the suspension.
  6. Click Modify from the pull-down list. The Modify Redundancy Clusters dialog is displayed
  7. Select the Auto Failback checkbox and enter the desired time period in the Auto Failback Delay field.
  8. Click Submit.