Managing Serviceguard Sixteenth Edition, March 2009
be performed on this node because of a disaster on the primary node and an LVM
problem with the volume group.) Do this as shown in the example below:
vgchange -a y /dev/vgdatabase
vgcfgbackup /dev/vgdatabase
vgchange -a n /dev/vgdatabase
6. If you are using mirrored individual disks in physical volume groups, check the
/etc/lvmpvg file to ensure that each physical volume group contains the correct
physical volume names for ftsys10.
NOTE: When you use PVG-strict mirroring, the physical volume group
configuration is recorded in the /etc/lvmpvg file on the configuration node. This
file defines the physical volume groups which are the basis of mirroring and
indicate which physical volumes belong to each physical volume group. Note that
on each cluster node, the /etc/lvmpvg file must contain the correct physical
volume names for the physical volume groups’s disks as they are known on that
node. Physical volume names for the same disks could be different on different
nodes. After distributing volume groups to other nodes, make sure each node’s
/etc/lvmpvg file correctly reflects the contents of all physical volume groups on
that node. See the following section, “Making Physical Volume Group Files
Consistent.”
7. Make sure that you have deactivated the volume group on ftsys9. Then enable
the volume group on ftsys10:
vgchange -a y /dev/vgdatabase
8. Create a directory to mount the disk:
mkdir /mnt1
9. Mount and verify the volume group on ftsys10:
mount /dev/vgdatabase/lvol1 /mnt1
10. Unmount the volume group on ftsys10:
umount /mnt1
11. Deactivate the volume group on ftsys10:
vgchange -a n /dev/vgdatabase
Making Physical Volume Group Files Consistent Skip ahead to the next section if
you do not use physical volume groups for mirrored individual disks in your disk
configuration.
Different volume groups may be activated by different subsets of nodes within a
Serviceguard cluster. In addition, the physical volume name for any given disk may
be different on one node from what it is on another. For these reasons, you must
carefully merge the /etc/lvmpvg files on all nodes so that each node has a complete
and consistent view of all cluster-aware disks as well as of its own private
Preparing Your Systems 211