Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4108
• What volume groups are needed?
• How much disk space is required, and how should this be allocated in
logical volumes?
• What file systems need to be mounted for each package?
• Which nodes need to import which logical volume configurations.
• If a package moves to an adoptive node, what effect will its presence
have on performance?
Create a list by package of volume groups, logical volumes, and file
systems. Indicate which nodes need to have access to common file
systems at different times.
It is recommended that you use customized logical volume names that
are different from the default logical volume names (lvol1, lvol2, etc.).
Choosing logical volume names that represent the high availability
applications that they are associated with (for example, lvoldatabase)
will simplify cluster administration.
# /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/lvoldb3raw_tablesignoreignore00#only.Theyrecordthe
# /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.
To further document your package-related volume groups, logical
volumes, and file systems on each node, you can add
commented lines to
the /etc/fstab file. The following is an example for a database
application:
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.
Details about creating, exporting, and importing volume groups in
Serviceguard are given in the chapter on “Building an HA Cluster
Configuration.”