HP-UX System Administrator's Guide: Logical Volume Management (762803-001, March 2014)

VG Version 1.0
VG Max Size 81856m
VG Max Extents 20464
The VG Version field indicates the target volume group is Version 1.0
3.3.3.2 Command Syntax
The vgversion syntax is:
vgversion [-r] [-v] –V [-U unshare_unit] vg_version_new vg_name
where
-r is Review mode. This allows you to review the operation before
performing the actual volume group version migration.
-v is Verbose mode.
-U unshare_unit sets the unit at which data will be unshared between a logical volume
and its snapshots, in the new volume group. This is only applicable
for migration to volume group Version 2.2 or higher. For more
information about snapshots see “Creating and Administering Snapshot
Logical Volumes” (page 108).
-V vg_version_new is the new version to which you are migrating (2. x).
vg_name is the target volume group (for example, vg01)
TIP:
• For a successful migration, the target volume group must meet certain conditions at execution
time; for example, the target volume group must be inactive. However, these conditions do
not need to be met when you are using Review mode (the –r option). For more information
on using the –r option, see “Review Mode: vgversion -r” (page 50).
• Immediately after vgversion completes, run the following to check the exit value (success
= 0, failure = non-zero) similar to other commands that run at the HP-UX shell level:
# echo $?
0
3.3.3.3 Review Mode: vgversion -r
vgversion allows you to review (–r) its stdout and stderr messages to determine whether
an attempted migration will succeed or fail without performing the actual migration.
Migration Success
In Review mode, when the migration will succeed, you should get messages that conclude with
text similar to the following:
...
Volume Group version can be successfully changed to ...
Review complete. Volume group not modified.
Migration Failure
A migration of a volume group can fail for various reasons, including:
• the target volume group must not be active
• the target volume group must be cluster-unaware
• no physical volumes of the target volume group should be used as the cluster lock disk
• the physical volumes of the volume group must have enough space for the new metadata
• the existing volume group has any features that are not supported in the target volume group
version
50 Administering LVM