Managing Serviceguard Eighteenth Edition, September 2010

NOTE: You can distribute the volume groups by means of the cmpreparestg (1m)
command. See “Using Easy Deployment Commands to Configure the Cluster” (page 211)
for more information. If you use cmpreparestg, you can skip to “Making Physical
Volume Group Files Consistent” (page 238).
Deactivating the Volume Group
NOTE: If you plan to use cmpreparestg, you can skip this step and proceed to
“Making Physical Volume Group Files Consistent” (page 238).
At the time you create the volume group, it is active on the configuration node (ftsys9,
for example). The next step is to unmount the file system and deactivate the volume
group; for example, on ftsys9:
umount /mnt1
vgchange -a n /dev/vgdatabase
NOTE: Do this during this setup process only, so that activation and mounting can
be done by the package control script at run time. You do not need to deactivate and
unmount a volume simply in order to create a map file (as in step 1 of the procedure
that follows).
Distributing the Volume Group
NOTE: If you use cmpreparestg, you can skip the procedure that follows and
proceed to “Making Physical Volume Group Files Consistent” (page 238).
Use the following commands to set up the same volume group on another cluster node.
In this example, the commands set up a new volume group on ftsys10 which will
hold the same physical volume that was available on ftsys9. You must carry out the
same procedure separately for each node on which the volume group's package can
run.
To set up the volume group on ftsys10, use the following steps:
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
236 Building an HA Cluster Configuration