Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 354
Node1 panics, and when the cluster reforms, pkgA starts running on
node 4:
Figure 3-12 Automatic Failback Configuration After Failover
After rebooting, node 1 rejoins the cluster. At that point, pkgA will be
automatically stopped on node 4 and restarted on node 1.
Figure 3-13 Automatic Failback Configuration After Restart of Node 1
NOTE Setting the FAILBACK_POLICY to AUTOMATIC can result in a package
failback and application outage during a critical production period. If you
are using automatic failback, you may wish not to add the package’s
primary node back into the cluster until it is an appropriate time to allow
the package to be taken out of service temporarily while it switches back
to the primary node.