VERITAS Volume Manager 5.0 Migration Guide (September 2006)
27Converting LVM to VxVM
Restoring the LVM volume group configuration
10. Restarting applications on the new VxVM volumes
Once the conversion to VxVM is complete, file systems can be mounted on the new
devices and applications can be restarted.
If you unmounted file systems before running vxvmconvert, you need to remount them
by the new volume names.
vxvmconvert will have updated /etc/fstab with the new
names. When you started
vxvmconvert, you may have left file systems mounted that are
associated with the volumes you converted.
vxvmconvert remounts these with the new
VxVM volume names.
11. Tailoring your VxVM configuration
vxvmconvert provides a default name for naming the newly formed VxVM disk group
during conversion only as an option. However, you will be given the choice of choosing
your own VxVM disk group name. By default,
vxvmconvert renames the LVM volume
group by replacing the prefix
vg in the volume group name with the prefix dg. For
example,
vg08 would become dg08. If there is no vg in the LVM volume group name,
vxvmconvert simply uses the same volume group name for its disk group.
The disks in the new VxVM disk group are given VxVM disk media names (see
vxintro(1M)) based on this disk group name. If your new VxVM disk group is dg08, it
will have VxVM disks with names like
dg0801, dg0802, etc. The VxVM plexes within
the logical volumes will be
dg0801-01, dg0801-02, etc.
If you do not like the default object names generated by the conversion, use the standard
VxVM utilities to rename these objects. See the rename option in the vxedit(1M) man
page for more details on renaming the disk groups.
Note: You must only rename objects in the VxVM configuration after you are fully
satisfied with that configuration. In particular, you should never use menu option 3 of
vxvmconvert (Roll back) after name changes. If you have chosen to set up symbolic
links to the VxVM volumes as described in “step 5. Planning for new VxVM logical
volume names,” avoid renaming VxVM objects. These symbolic links are made invalid if
the underlying VxVM device node name changes.
Restoring the LVM volume group configuration
In some circumstances, you may need to restore the LVM configuration that existed
before you converted to VxVM with
vxvmconvert. For example:
■ If something went wrong during the conversion, such as a system crash or a disk
crash that caused the conversion to be unworkable.
■ If during a conversion only some of a set of volume groups converted successfully,
then you may want to restore the LVM configuration for the entire set.