HP Serviceguard manual Customizing Packages for VxVM, Mntdg0202, respectively

separation.) The same mirroring pattern should be followed in creating the VxVM plexes, with different plexes configured on disks that are attached to different buses.

As an alternative to defining the VxVM disk groups on a new set of disks, it is possible to convert existing LVM volume groups into VxVM disk groups in line using the vxvmconvert(1M) utility. This utility is described along with its limitations and cautions in the Veritas Volume Manager Migration Guide for your version, available from http:// www.hp.com/go/hpux-core-docs. If using the vxconvert(1M) utility, then skip the next step and go ahead to the following section.

NOTE: Remember that the cluster lock disk, if used, must be configured on an LVM volume group and physical volume. If you have a lock volume group containing data that you wish to move to VxVM, you can do so, but do not use vxvmconvert, because the LVM header is still required for the lock disk.

6.Restore the data to the new VxVM disk groups. Use whatever means are most appropriate for the way in which the data was backed up in step 3 above.

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 a legacy package that will you use with the Veritas Volume Manager (VxVM) disk groups. If you decide to create a new package, see Chapter 6: “Configuring Packages and Their Services ” (page 227).

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 -sPackage.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 let's say we have two volumes defined in each of the two disk groups from above, lvol101 and lvol102, and lvol201 and lvol202. These are mounted on /mnt_dg0101 and /mnt_dg0102, and /mnt_dg0201 and

/mnt_dg0202, respectively.

/mnt_dg0101and /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/lvol102"

LV[2]="/dev/vx/dsk/dg02/lvol201"

LV[3]="/dev/vx/dsk/dg02/lvol202"

FS[0]="/mnt_dg0101" FS[1]="/mnt_dg0102" FS[2]="/mnt_dg0201" FS[3]="/mnt_dg0202"

FS_MOUNT_OPT[0]="-o ro" FS_MOUNT_OPT[1]="-o rw" FS_MOUNT_OPT[2]="-o ro" FS_MOUNT_OPT[3]="-o rw"

Customizing Packages for VxVM 375