Veritas Storage Foundation 5.1 SP1 Advanced Features Administrator"s Guide (5900-1503, April 2011)

Implementing changes for new VxVM logical volume names
You must be sure that all applications and configuration files refer properly to
the new VxVM logical volumes.
See “Planning for new VxVM logical volume names” on page 409.
Restarting applications on the new VxVM volumes
After 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 you ran vxvmconvert, you need to remount
them by the new volume names. vxvmconvert 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.
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.
413Offline data migration
Converting LVM to VxVM