VERITAS Volume Manager 3.5 Migration Guide (September 2004)

Chapter 2

Converting LVM to VxVM

Converting LVM Volume Groups to VxVM Disk Groups

10. Restarting applications on the new VxVM volumes

Once the conversion to VxVM is complete, ﬁle systems can be mounted on the new devices and applications

can be restarted.

If you had unmounted ﬁle 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 ﬁle systems mounted that are associated with the volumes you converted.

vxvmconvert remounts these with the new VxVM volume names.

11. Tailoring your VxVM conﬁguration

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 preﬁx vg in the volume group name with the

preﬁx 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 conﬁguration after you are fully satisﬁed with that

conﬁguration. 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” on page 15, avoid

renaming VxVM objects. These symbolic links are made invalid if the underlying VxVM device

node name changes.