Veritas Volume Manager 5.0.1 Migration Guide, HP-UX 11i v3, First Edition, November 2009

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.
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 () based
on this disk group name. Additional information is available on VxVM disk media
names.
See vxintro(1M).
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, avoid renaming VxVM objects. Additional
information is available on setting up symbolic links. These symbolic links are
made invalid if the underlying VxVM device node name changes.
See “Planning for new VxVM logical volume names” on page 29.
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.
33Converting LVM to VxVM
Restoring the LVM volume group configuration