Managing Serviceguard 12th Edition, March 2006

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 165
• 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.
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:
# /dev/vg01/lvoldb1 /applic1 vxfs defaults 0 1 # These six entries are
# /dev/vg01/lvoldb2 /applic2 vxfs defaults 0 1 # for information purposes
#/dev/vg01/lvoldb3raw_tablesignoreignore00#only.Theyrecordthe
# /dev/vg01/lvoldb4 /general vxfs 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.
NOTE Do not use /etc/fstab to mount file systems that are used by
Serviceguard packages.
Planning VERITAS Cluster Volume Manager and
Cluster File System
If you have a failover package in a cluster that uses the VERITAS
Volume Manager or the VERITAS Cluster File System (CFS), you
configure system multi-node packages to handle the volume groups and
file systems.