VERITAS Volume Manager 5.0 Migration Guide (September 2006)

19Converting LVM to VxVM
Converting LVM volume groups to VxVM disk groups
For this release, a volume group containing the /usr file system cannot be
converted because
vxvmconvert needs access to files in /usr.
■ Volume groups with any dump or primary swap volumes.
vxvmconvert will not convert any volume group with dump or primary swap
volumes. These are volumes known to the boot process. However, swap volumes on
volumes other than the root volume can be converted (as long as this volume is not in
the same volume group as the root volume).
■ Volume group disks used in MC/ServiceGuard clusters.
The conversion process does not support conversion of any volume group that is
marked as a member of a MC/ServiceGuard or OPS Edition high availability cluster.
The volume group must be deactivated and removed from membership in the high
availability cluster before it can be converted.
■ Volume groups used for cluster lock disks.
The conversion process does not support conversion of a volume group that contains
a disk that is being used for a cluster lock disk for an MC/ServiceGuard cluster.
■ Volume groups with any disks that have bad blocks in the bad block directory.
Unlike LVM, VxVM does not support bad block revectoring at the physical volume
level. If there appear to be any valid bad blocks in the bad block directory of any disk
used in an LVM volumegroup, the group cannot be converted. See Appendix A,
Conversion Error Messages, for actions to take in this situation.
■ Volume groups with mirrored volumes.
A conversion fails if the LVM volume group being converted has mirrored volumes,
but the system does not have a valid license installed that enables mirroring for
VxVM.
The analyze option in vxvmconvert, which is described in later sections, aids you in
identifying which volume groups can be converted.