HP-UX Reference (11i v1 05/09) - 1M System Administration Commands N-Z (vol 4)
v
vgimport(1M) vgimport(1M)
The designated primary and alternate link might not be the same as it was configured before.
Alternate links will be added to the importing volume group even if they might not be configured in
the volume group initially.
If the original primary path of a disks become an alternate path after the newly imported volume group
entry is created in /etc/lvmtab, the order can be easily reverted by using
vgreduce to remove the
primary path and then use
vgextend to add the path back again.
If additional alternate paths were added to the newly imported volume group, use
vgreduce to reduce
any alternate paths that were added but they were not needed.
ADDITIONAL WARNINGS
Starting at 10.20, the
vgimport command is supporting additional EMC Symmetrix disk product func-
tionality (see vgchgid(1M)). The vgimport command will be enforcing a new rule such that the group of
disks to be imported must have the same EMC Symmetrix attributes. Clearly this checking only applies if
the disks involved in the operation are EMC Symmetrix. Should the command find an incompatibility, a
message of the following type will be produced:
"Attempt to mix incompatible EMC Symmetrix disk types failed. Physical volume /dev/dsk/cxtxdx is
EMC BCV disk, but physical volume /dev/dsk/cxtxdx is a standard disk. Please consult the EMC Sym-
metrix documentation, if applicable".
If duplicate VGIDs (volume group id) were found in different types of EMC Symmetrix disks during the
vgimport -s operation, the above error message will appear, and the command will fail. Please refer to
vgchgid(1M) on how to modify VGID on the EMC Symmetrix disk.
Note that EMC Symmetrix disks which do not have any of the additional attributes can still be mixed with
non-EMC disks in a single volume group.
Cross-Cabinet Volume Group Warnings
On multi-cabinet V-Class systems, it is possible to create a volume group using physical volumes that are
physically attached to different cabinets. However, due to limitations in the HP-UX boot sequence, such a
cross-cabinet volume group cannot contain root, boot, swap, or dump logical volumes. If the physical
volumes specified by pv_path make up a cross-cabinet volume group that contains a root, boot, swap, or
dump logical volume, then vgimport will fail to import that volume group. This should only occur as the
result of a hardware reconfiguration. If this does occur, the hardware configuration will need to be
modified again to connect the physical volumes to the same cabinet.
EXTERNAL INFLUENCES
Environment Variables
LANG determines the language in which messages are displayed.
If LANG is not specified or is null, it defaults to "C" (see lang(5)).
If any internationalization variable contains an invalid setting, all internationalization variables default to
"C" (see environ(5)).
EXAMPLES
Import the volume group
/dev/vg01 that is located on physical disks /dev/dsk/c0t1d0 and
/dev/dsk/c0t3d0:
vgimport -v /dev/vg01 /dev/dsk/c0t1d0 /dev/dsk/c0t3d0
Activate the volume group following a successful import:
vgchange -a y vg01
Import the volume group /dev/vg01 using the mapfile, /tmp/vg01.mymap. mymap was previously
specified by the
vgexport command on another system. The volume group, /dev/vg01 , is specified in
mymap and will be used by the importing system only:
vgimport -v -m /tmp/vg01.mapfile /dev/vg01 \
/dev/dsk/c0t5d0 /dev/dsk/c0t7d0
Import the volume group /dev/vg02 using the mapfile, /tmp/vg02.mymap. mymap was previously
specified by the vgexport command on another system. The volume group, /dev/vg02 , is specified in
mymap and will be shared among the exporting system, this system, and other systems importing the
volume group as shared:
Section 1M−−1082 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005