auto_failback directive - set failback policy

The auto_failback option determines whether a resource[1] will automatically fail back[2] to its "primary[3]" node[4], or remain on whatever node is serving it until that node fails, or an administrator intervenes.

The possible values for auto_failback are:

• on - enable automatic failbacks

• off - disable automatic failbacks

• legacy - enable automatic failbacks in systems where all nodes in the cluster do not yet support the auto_failback option.

Both the auto_failback on and off are backwards compatible with the old "nice_failback on" setting.

See the FAQ[5] document for information on how to convert from "legacy" to "on" without a flash cut (i.e., using a RollingUpgrade[6] process)

The default value for auto_failback is "legacy", which will issue a warning at startup. So, make sure you put an auto_failback directive in your ha.cf[7] file (note: auto_failback can be any HeartbeatBoolean[8] value or legacy). Typically, you want to set auto_failback on for an ActiveActive[9] cluster, and commonly to off for an ActivePassive[10] cluster.

NOTE: auto_failback does not have any effect on a Release 2 CRM-style cluster (one configured with crm on[11]). For CRM-style clusters, this has been replaced with the default_resource_stickiness[12] attribute in the CIB.

---

This information provided courtesy of the Linux-HA project at http://linux-ha.org/