HP-UX 11i v3 - LVM Volume Group Version Migration (September 2010)
6
2. The vgversion command creates the configuration backup file corresponding to the final volume
group version and saves that as /etc/lvmconf/vgversion_vg_name/vg_name_final VG
version.conf. The following is the output for this step:
New Volume Group configuration for "/dev/vg01" has been saved in
"/etc/lvmconf/vgversion_vg01/vg01_2.1.conf"
Note
At this point, the volume group is not modified. Even if the vgversion
command is killed for any reason, there is no need for any recovery.
3. The vgversion command removes the volume group entries from /etc/lvmtab in case of
Version 1.0 volume groups or from /etc/lvmtab_p in case of Version 2.x volume groups. The
following is the output for this step:
Removing the Volume Group /dev/vg01 from /etc/lvmtab # Version 1.0 volume groups
Removing the Volume Group /dev/vg01 from /etc/lvmtab_p # Version 2.x volume groups
4. The vgversion command removes the /dev/vg_name directory and its contents. They are
recreated later with new major numbers and minor numbers.
5. The vgversion command applies the configuration to all the physical volumes in the reverse
order in which they are listed in the /etc/lvmtab or /etc/lvmtab_p file. If vgversion
fails to apply the configuration on any of the physical volumes, it undoes all previous changes. The
following is the output for this step:
Applying the configuration to all Physical Volumes from
"/etc/lvmconf/vgversion_vg1/vg1_2.1.conf"
Volume Group configuration has been restored to /dev/rdisk/disk378
Note
If the vgversion command is killed while applying the configuration
to the disks, the volume group might not be found in either the
/etc/lvmtab or /etc/lvmtab_p file. It is possible that some of the
disks have the new configuration and some disks have the old
configuration. HP recommends you run the restore script to recover the
volume group. For more information, see Reverting back to Version 1.0.
6. The vgversion command recreates the /dev/vg_name directory and device special files of the
logical volumes.
7. The vgversion command adds the volume group entries to the /etc/lvmtab_p file. This
completes the volume group version migration.
8. Beginning with the HP-UX 11i v3 September 2010 Update release, the vgversion command
automatically backs up the configuration file, if the file is already present in its default
/etc/lvmconf location or in a user-defined location specified by the
LVMP_CONF_PATH_NON_BOOT variable in the /etc/lvmrc file. For more information, see
vgcfgbackup(1M).
Note
If you have configured the LVMP_CONF_PATH_NON_BOOT variable in
the /etc/lvmrc file to a non-existent path, vgversion does not
backup the volume group configuration file after the migration.