 |
» |
|
|
|
The following procedure shows how to do the migration of individual volume
groups for packages that are configured to run on a given node. You
should convert all the volume groups for a package at the same time. It is assumed that VxVM software and an appropriate version
of HP-UX and Serviceguard have been installed on the node, and that
the node has rebooted and rejoined the cluster. It is further assumed
that you have created a rootdg on the node as described above under “Creating
a Root Disk Group.” Halt the
package that activates the volume group you wish to convert to VxVM: # cmhaltpkg PackageName Activate the LVM volume group in read-only mode: # vgchange -a r VolumeGroupName 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. Back up the volume group configuration: # vgcfgbackup 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 http://www.docs.hp.com. 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. | | | | |
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.
|
Printable version
