Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Creating the Storage Infrastructure and Filesystems with LVM and VxVM
Chapter 5 215
Distributing Volume Groups to Other Nodes
After creating volume groups for cluster data, you must make them
available to any cluster node that will need to activate the volume group.
The cluster lock volume group must be made available to all nodes.
Deactivating the Volume Group At the time you create the volume
group, it is active on the configuration node (
ftsys9 , for example). Before
setting up the volume group for use on other nodes, you must first
unmount any filesystems that reside on the volume group, then
deactivate it. At run time, volume group activation and filesystem
mounting are done through the package control script.
Continuing with the example presented in earlier sections, do the
following on
ftsys9 :
# umount /mnt1
# vgchange -a n /dev/vgdatabase
Distributing the Volume Group with LVM Commands 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
4. Still on ftsys10, create a control file named group in the directory
/dev/vgdatabase, as follows:
# mknod /dev/vgdatabase/group c 64 0x hh 0000
Use the same minor number as on ftsys9 . Use the following
command to display a list of existing volume groups:
# ls -l /dev/*/group