VERITAS Volume Manager 3.1 Migration Guide

Converting LVM to VxVM

Restoring the LVM Volume Group Conﬁguration

Chapter 2 39

NOTE The name changes that vxvmconvert makes as part of the conversion

are managed by rollback, and do not count as VxVM conﬁguration

changes for the purposes of choosing a restoration method.

NOTE vgrestore (1M) should not be confused with the LVM command,

vgcfgrestore (1M). vgcfgrestore is used to restore the LVM

conﬁguration information saved by vgcfgbackup (1M), but it will not

restore your device ﬁles and /etc/fstab entries. It also will not import

and activate the volume group, nor will it clean up any VxVM

information left around. However, vgrestore will do all of this for you.

Rollback to LVM Using vxvmconvert

Rollback replaces the VxVM disk groups with the original LVM volume

groups. During conversion, vxvmconvert saves a “snapshot” of the

original LVM metadata and associated conﬁguration ﬁles, such as

/etc/fstab and LVM device ﬁles. It restores only the LVM metadata and

conﬁguration ﬁles from this snapshot; user data is not changed. This

method can only be used if no changes have been made to the

conﬁguration since the conversion.

For example, if a disk has been added to the disk group or if the names of

any logical volumes have changed, you cannot use the rollback method.

NOTE In many cases, if you choose the rollback method and the conﬁguration

has changed, you receive an error and must use the full restore method.

If you used the workaround of creating symbolic links from the old LVM

names to the new VxVM names described in “step “5. Planning for new

VxVM logical volume names” you must remove the symbolic links you

created before beginning the rollback.

This “snapshot” is kept on the root ﬁle system. The presence of this

snapshot should not be taken as assurance that full off-line backups will

not be needed. See '4. Backing up your LVM conﬁguration and user data'

for speciﬁc information on backups.