Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Note that the disk device names onftsys10 may be different from their names on ftsys9.
Make sure the physical volume names are correct throughout the cluster.
When the volume group can be activated on this node, perform a vgcfgbackup. (This backup
will be available in the unlikely event that a vgcfgrestore must 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 “Making
Physical Volume Group Files Consistent” (page 173).
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 this section if you do not use physical volume groups for mirrored individual disks in your disk
configuration, or if you are using cDSFs; see “About Cluster-wide Device Special Files (cDSFs)”
(page 99) for more information about cDSFs.
Different volume groups may be activated by different subsets of nodes within a Serviceguard
cluster. In addition, if you are not using cDSFs, 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 (non-cluster-aware) disks. To make merging the
files easier, be sure to keep a careful record of the physical volume group names.
Use the following procedure to merge files between the configuration node (for example, ftsys9)
and a new node (for example, ftsys10) to which you are importing volume groups:
1. Copy /etc/lvmpvg from ftsys9 to /etc/lvmvpg.new on ftsys10.
2. If there are volume groups in /etc/lvmpvg.new that do not exist on ftsys10, remove all
entries for that volume group from /etc/lvmpvg.new.
Preparing Your Systems 173