Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Migrating from LVM to VxVM Data Storage
Customizing Packages for VxVM
Appendix G 417
Customizing Packages for VxVM
After creating the VxVM disk group, you need to customize the
Serviceguard package that will access the storage. Use the following
procedure for disk groups that will be used with the VERITAS Volume
Manager (VxVM). If you are using the Cluster Volume Manager (CVM),
skip ahead to the next section.
1. Rename the old package control script as follows:
# mv Package.ctl Package.ctl.bak
2. Create a new package control script with the same name as the old
one:
# cmmakepkg -s Package.ctl
3. Edit the new script to include the names of the new VxVM disk
groups and logical volumes.
The new portions of the package control script that are needed for
VxVM use are as follows:
•The VXVM_DG[] array. This defines the VxVM disk groups that
are used for this package. The first VxVM_DG[] entry should be in
index 0, the second in 1, etc. For example:
VXVM_DG[0]="dg01"
VXVM_DG[1]="dg02"
•The LV[], FS[] and FS_MOUNT_OPT[] arrays are used the same
as they are for LVM. LV[] defines the logical volumes, FS[]
defines the mount points, and FS_MOUNT_OPT[] defines any
mount options. For example lets say we have two volumes
defined in each of the two disk groups from above, lvol101,
lvol102 and lvol201 and lvol202. These are mounted on
/mnt_dg0101, /mnt_dg0102, /mnt_dg0201 and /mnt_dg0202
respectfully. /mnt_dg0101 and /mnt_dg0201 are both mounted
read only. The LV[], FS[] and FS_MOUNT_OPT[] entries for these
would be as follows:
LV[0]="/dev/vx/dsk/dg01/lvol101"
LV[1]="/dev/vx/dsk/dg01/lvol0102"
LV[2]="/dev/vx/dsk/dg02/lvol0201"
LV[3]="/dev/vx/dsk/dg02/lvol0202"