Managing Serviceguard Eighteenth Edition, September 2010

3. Back up the volume group’s data, using whatever means are most appropriate for
the data contained on this volume group. For example, you might use a
backup/restore utility such as Omniback, or you might use an HP-UX utility such
as dd.
4. Back up the volume group configuration:
vgcfgbackup
5. Define the new VxVM disk groups and logical volumes. You will need to have
enough additional disks available to create a VxVM version of all LVM volume
groups. You should create VxVM logical volumes that have the same general
layout as the LVM configuration. For example, an LVM mirrored volume might
have one mirror copy on one SCSI controller and a second copy on another
controller to guard against a single controller failure disabling an entire volume.
(Physical volume groups are sometimes used in LVM to enforce this 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 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 279).
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
472 Migrating from LVM to VxVM Data Storage