vgversion.1m (2010 09)

v
vgversion(1M) vgversion(1M)
The migration of volume group version 1.0 to 2.0 or higher requires the kernel driver, which supports
volume group version 2.0 or higher, to be loaded.
During migration of volume group version 1.0 to 2.0 or higher, all device special files associated with
the vg_name may get recreated. The applications need to take care of recreating the symlinks or
hardlinks to the new device special files of the volume group vg_name post successful migration.
FILES
/etc/lvmconf/vgversion_
vg_name
/vg_name_vg_version_old
.conf
Holds the existing volume group configuration having volume group version vg_version_old.
/etc/lvmconf/vgversion_
vg_name
/vg_name_vg_version_new
.conf
This file contains the existing volume group configuration of volume group version vg_version_new.
/etc/lvmconf/vgversion_
vg_name
/mapfile_vg_name_1.0
Holds the mapfile information for the original volume group. This file contains the names of logical
volumes of the volume group.
/etc/lvmconf/vgversion_
vg_name
/mapfile_vg_name_2.x
Holds the mapfile information for the volume group version vg_version_new. This file contains the
names of logical volumes of the volume group.
/etc/lvmconf/vgversion_
vg_name/vg_name _disks
Holds the list of physical volumes in the volume group. The order of physical volumes is decided by
the order in which they are added in the
/etc/lvmtab or /etc/lvmtab_p
.
/etc/lvmconf/vgversion_
vg_name/vgversion_vg_name _restore
A script created by vgversion before making any update, to be used if the vgversion command
is interrupted while committing the configuration changes to the physical volumes. See the
Recovery section for its usage.
SEE ALSO
boot(1M), lvlnboot(1M), mkboot(1M), pvcreate(1M), pvmove(1M), vgcfgbackup(1M), vgcfgrestore(1M),
vgchange(1M), vgcreate(1M), vgdisplay(1M), vgextend(1M), vgmodify(1M), vgreduce(1M), lvm(7).
6 Hewlett-Packard Company 6 HP-UX 11i Version 3: September 2010