VERITAS Volume Manager 5.0 Migration Guide (September 2006)

26 Converting LVM to VxVM
Converting LVM volume groups to VxVM disk groups
Note: The LVM logical volumes to be converted must all be available to the
vxvmconvert process. You should not deactivate the volume group or any logical
volumes before running vxvmconvert.
To activate a volume group
If you are not certain if the LVM volumes or the corresponding volume groups are active,
you can activate them with the following command:
# vgchange -a y vol_grp_name
7. Converting a volume group
To do the actual conversion of LVM volume groups to VxVM disk groups, choose option
2 of the
vxvmconvert utility.
vxvmconvert will prompt for a name for the VxVM disk group that will be created to
replace the LVM volume group you are converting. This is the only object naming that is
done through
vxvmconvert. For details on modifying VxVM volume names, see “step
11. Tailoring your VxVM configuration,” on page 27.
As described earlier in “step 2. Analyzing an LVM volume group to see if conversion is
possible,” on page 21, 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” on page 31.
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 “Conversion error messages” on page 71 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 on
page 23” for details.