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

As described earlier, the volume groups selected for conversion are analyzed to
ensure that conversion is possible.
See “Analyzing an LVM volume group to see if conversion is possible” on page 26.
After a successful analysis phase, vxvmconvertprompts you to commit to the
change or abort the conversion. When you select to commit to conversion, the
new VxVM metadata is written. Before the conversion is committed, the
vxvmconvert operation displays the estimated required time as:
VxVM INFO V-5-2-4906
The expected time for convert is: 0 hrs 0 mins 7 secs.
Note: The time required for conversion is an estimate and is not a calculated time.
The actual conversion time may differ depending on factors like number of CPUs,
Memory, I/O throughput etc.
More information is available on the details of the conversion process.
See “Examples” on page 37.
Taking actions if conversion fails
There are several reasons why conversion can fail.
See “Volume group conversion limitations” on page 22.
Messages from vxvmconvert explain the type of failure, and any actions you can
take before retrying the conversion.
Complete details of specific error messages are available.
See “About conversion error messages” on page 79.
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 29.
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
Converting LVM to VxVM
Converting LVM volume groups to VxVM disk groups
32