Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 121
# /dev/vg01/lvoldb1 /applic1 ext2 defaults 0 1 # These six entries are
# /dev/vg01/lvoldb2 /applic2 ext2 defaults 0 1 # for information purposes
# /dev/vg01/lvoldb3 raw_tables ignore ignore 00#only. They record the
# /dev/vg01/lvoldb4 /general ext2 defaults 0 2 # logical volumes that
# /dev/vg01/lvoldb5 raw_free ignore ignore 0 0 # exist for Serviceguard's
# /dev/vg01/lvoldb6 raw_free ignore ignore 0 0 # HA package. Do not uncomment.
Create an entry for each logical volume, indicating its use for a file
system or for a raw device.
CAUTION Do not use /etc/fstab to mount file systems that are used by
Serviceguard packages.
For information about creating, exporting, and importing volume groups,
see “Creating the Logical Volume Infrastructure” on page 158.
Planning for Expansion
You can add packages to a running cluster. This process is described in
Chapter 7, “Cluster and Package Maintenance,” on page 241.
When adding packages, be sure not to exceed the value of
max_configured_packages as defined in the cluster configuration file
(see “Cluster Configuration Parameters” on page 110). You can modify
this parameter while the cluster is running if you need to.
Choosing Switching and Failover Behavior
To determine the failover behavior of a failover package (see “Package
Types” on page 50), you define the policy that governs where
Serviceguard will automatically start up a package that is not running.
In addition, you define a failback policy that determines whether a
package will be automatically returned to its primary node when that is
possible.