Managing Serviceguard A.11.20, March 2013

If you use configured_node as the failover policy, the package will start up on the highest
priority node in the node list, assuming that the node is running as a member of the cluster. When
a failover occurs, the package will move to the next highest priority node in the list that is available.
Failback Policy
The use of the failback_policy parameter allows you to decide whether a package will return
to its primary node if the primary node becomes available and the package is not currently running
on the primary node. The configured primary node is the first node listed in the package’s node
list.
The two possible values for this policy are automatic and manual. The parameter is set in the
package configuration file:
As an example, consider the following four-node configuration, in which failover_policy is
set to configured_node and failback_policy is automatic:
Figure 19 Automatic Failback Configuration before Failover
Table 3 Node Lists in Sample Cluster
FAILBACK POLICYFAILOVER POLICYNODE_NAME ListPackage Name
AUTOMATICCONFIGURED_NODEnode1, node4pkgA
AUTOMATICCONFIGURED_NODEnode2, node4pkgB
AUTOMATICCONFIGURED_NODEnode3, node4pkgC
node1 panics, and after the cluster reforms, pkgA starts running on node4:
56 Understanding Serviceguard Software Components