Managing Serviceguard 13th Edition, February 2007

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 384
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-12 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.
On Combining Failover and Failback Policies Combining a
FAILOVER_POLICY of MIN_PACKAGE_NODE with a FAILBACK_POLICY of
AUTOMATIC can result in a package’s running on a node where you did not
expect it to run, since the node running the fewest packages will
probably not be the same host every time a failover occurs.
Using Older Package Configuration Files
If you are using package configuration files that were generated using a
previous version of Serviceguard, we recommend you use the cmmakepkg
command to open a new template, and then copy the parameter values
into it. In the new template, read the descriptions and defaults of the
choices that did not exist when the original configuration was made. For
example, the default for FAILOVER_POLICY is now CONFIGURED_NODE and
the default for FAILBACK_POLICY is now MANUAL.