Managing HP Serviceguard for Linux, Seventh Edition, July 2007

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 3 55
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 want to wait to add the package’s
primary node back into the cluster until you can 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, HP recommends 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.