HP-UX 11i v3 - LVM Volume Group Version Migration (September 2010)

9
Volume group migration from Version 2.2 to Version 2.1
Volume group migration from Version 2.2 to 2.1 fails if the volume group has bootable physical
volumes or if a snapshot logical volume is configured for any logical volume of the volume group. The
size of metadata required for a Version 2.2 volume group is greater than that of a 2.1 volume group.
Therefore, volume group migration from Version 2.2 to 2.1 frees up a few extents. Run vgmodify to
utilize the free space.
Volume group migration from Version 2.2 to Version 2.0
The migration of a Version 2.2 volume group to 2.0 is the same as that of volume group migration
from Version 2.2 to 2.1. All the conditions applicable to migration from Version 2.2 to 2.1 and from
Version 2.1 to 2.0 apply to migration of Version 2.2 to 2.0.
Recovering from failures
This section describes how to recover the volume group in case the vgversion command is
interrupted.
To simplify the recovery, vgversion creates a vgversion_vg_name_restore restore script in
the /etc/lvmconf/vgversion_vgname directory. This shell script is not used by vgversion,
and is provided for manual restoration of all physical volumes in case of failures or interruptions. HP
recommends you use the recover script in case of any failures.
If the vgversion command is interrupted while migrating a Version 1.0 volume group to 2.1,
run the restore script by providing the configuration backup file of the final volume group version
configuration. The configuration backup file is
/etc/lvmconf/vgversion_vg_name/vg_name.VG final VG version.conf
For example:
# /etc/lvmconf/vgversion_vg01/vgversion_vg01_restore vg01_2.1.conf
Volume Group configuration has been restored to /dev/rdisk/disk349
Volume Group configuration has been restored to /dev/rdisk/disk348
The Volume Group already exists in lvmtab/lvmtab_p
Exporting the Volume group
vgexport: Volume group "/dev/vg01" has been successfully removed.
vgimport: Volume group "/dev/vg01" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating
the volume group.
Completed restore of VG /dev/vg01
In case of a migration failure, remember the following:
The review operation of the vgversion command does not create or change any configuration
backup files.
During the migration operation, the vgversion command creates the latest configuration backup
file of the volume group with the current configuration; this can be used to recover the original
volume group configuration. Before applying the new configuration on the disks vgversion
creates the configuration backup file corresponding to the new configuration. This file can be used
to update the new configuration on those disks to which the new configuration could not be applied
during the vgversion operation.
The configuration files are stored in the /etc/lvmconf/vgversion_vg_name directory.