HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

1. On ftsys9, copy the mapping of the volume group to a specified file.
vgexport -p -s -m /tmp/vgdatabase.map /dev/vgdatabase
2. Still on ftsys9, copy the map file to ftsys10:
rcp /tmp/vgdatabase.map ftsys10:/tmp/vgdatabase.map
3. On ftsys10, create the volume group directory:
mkdir /dev/vgdatabase
4. Still on ftsys10, create a control file named group in the directory /dev/vgdatabase,
as follows:
mknod /dev/vgdatabase/group c 64 0xhh0000
Use the same minor number as on ftsys9. Use the following command to display a list of
existing volume groups:
ls -l /dev/*/group
5. Import the volume group data using the map file from node ftsys9. On node ftsys10,
enter:
vgimport -s -m /tmp/vgdatabase.map /dev/vgdatabase
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 183).
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:
182 Building an HA Cluster Configuration