Example Recovery - HP -UX 11i Administrator's Manual

Logical volume management
Hide thumbs Also See for HP-UX 11i:
Table of Contents

Advertisement

CAUTION:
fails, such as an interruption during migration execution.
The recovery script should not be used to "undo" a successful migration. For a successful
vgversion migration, you should use only a subsequent vgversion execution (and not
the recovery script) to reach the newly desired volume group version. Note that a migration
to 1.0 is not supported, so no return path is available once a migration from Version 1.0 to
Version 2.x is successful.
Further, when needed, the recovery script should be run only immediately after the attempted
migration fails. Because the recovery script contains only configuration information
corresponding to the time of migration, any volume group configuration changes subsequent
to the migration would not be included in the recovery script, and therefore will be lost when
the recovery script is run.
File Location
The backup files, including the recovery script, exist in
/etc/lvmconf/vgversion_vg_name
where
is the name of the target volume group at the time of the actual conversion.
vg_name
Command Syntax
The syntax for the recovery script is:
vgversion_vg_name_restore vg_name_vg_version_old.conf
where
vg_name
vg_version_old
NOTE:
The target volume group should be de-activated or all physical volumes of the target
volume group should be detached prior to running the recovery script.

Example Recovery

Assume there was an unexpected interruption, such as a power failure, during the above migration
of vg01 and that we need to return the volume group to its pre-migration state, where the volume
group was of version 1.0:
1.
If needed, de-activate the target volume group:
# vgchange -a n vg01
2.
cd to the directory where the configuration backup files and recovery script exist. Using the
above file location naming convention:
# cd /etc/lvmconf/vgversion_vg01
3.
Run the recovery script. Using the above syntax:
# vgversion_vg01_restore vg01_1.0.conf
4.
Once the recovery has successfully completed, you can now re-attempt the migration using
vgversion:
# vgversion -v -V 2.1 vg01
For more information on recovery, see the vgversion(1M) manpage.
50
Administering LVM
The recovery script should be run only in cases where the migration unexpectedly
is the name of the target volume group
is the original version number of the volume group (1.0 or 2.x)

Advertisement

Table of Contents
loading

Table of Contents