VERITAS Volume Manager 3.1 Migration Guide

Converting LVM to VxVM
Converting LVM Volume Groups to VxVM Disk Groups
Chapter 236
the only object naming that is done through vxvmconvert. For details on
modifying VxVM volume names, see “step “11. Tailoring your VxVM
configuration”.
As described earlier in “step “2. Analyzing an LVM volume group to see if
conversion is possible”,” on page 12, the volume groups selected for
conversion are analyzed to ensure that conversion is possible. After a
successful analysis phase, vxvmconvert will ask you to commit to the
change or abort the conversion. When you select to commit to conversion,
the new VxVM metadata is written.
NOTE It is good practice to convert one volume group at a time to avoid errors
during conversion.
The details of the conversion process are shown in “Examples”.
8. Taking actions if conversion fails
Conversion can fail for any of the reasons detailed in the “Volume Group
Conversion Limitations”” section. Messages from vxvmconvert will
explain the type of failure, and any actions you can take before retrying
the conversion.
See Appendix A, Conversion Error Messages, for complete details of
specific error messages.
9. 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 step “5. Planning for new
VxVM logical volume names” for details.
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.