Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Building an HA Cluster Configuration
Preparing Your Systems
Chapter 5170
Storing Volume Group Configuration Data
When you create volume groups, LVM creates a backup copy of the
volume group configuration on the configuration node. In addition, you
should create a backup of configuration data on all other nodes where the
volume group might be activated by using the vgcfgbackup command:
vgcfgbackup vgpkgA vgpkgB
If a disk in a volume group must be replaced, you can then restore the
disk’s meta data by using the vgcfgrestore command. The procedure is
described under “Replacing Disks” in the “Troubleshooting” chapter.
Preventing Boot-Time vgscan and Ensuring Serviceguard
Volume Groups Are Deactivated By default, Linux will perform
LVM startup actions whenever the system is rebooted. These include a
vgscan (on some Linux distributions) and volume group activation. This
can cause problems for volumes used in a Serviceguard environment (for
example, a volume group for a Serviceguard package that is not
currently running may be activated). To prevent such problems, proceed
as follows on the various Linux versions.
NOTE You do not need to perform these actions if you have implemented VG
activation protection as described under “Creating the Logical Volume
Infrastructure” on page 158.
SUSE Linux Enterprise Server
Prevent a vgscan command at boot time by removing the
/etc/rc.d/boot.d/S07boot.lvm file from all cluster nodes.
NOTE Be careful if you use YAST or YAST2 to configure volume groups, as that
may cause all volume groups to be activated. After running YAST or
YAST2, check that volume groups for Serviceguard packages not
currently running have not been activated, and use LVM commands to
deactivate any that have. For example, use the command vgchange -a n
/dev/sgvg00 to deactivate the volume group sgvg00.