HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
v
vgimport(1M) vgimport(1M)
NAME
vgimport - import an LVM volume group onto the system
SYNOPSIS
/usr/sbin/vgimport [-m mapfile][-p][-v][-f infile] vg_name pv_path ...
/usr/sbin/vgimport -m mapfile -s -v vg_name
DESCRIPTION
The vgimport command adds the specified volume group to the system. The physical volumes, specified
as pv_path ..., are scanned to obtain the volume group information and logical volume information. This
command works much like vgcreate by requiring that the volume group device directory and the
group special file be created before the command is executed (see vgcreate(1M)). The vg_name is added
from the /etc/lvmtab file, and the associated logical volume device files are added to the system.
vgimport assumes that the volume group information has already been created on the physical volumes.
This command is useful in conjunction with the vgexport command (see vgexport(1M)), to move volume
groups from one system to other systems within a high availabilitycluster.
vgimport creates logical volume devices files under the vg_name directory using the naming convention
given in mapfile or using the default naming convention used by the
lvcreate command (see
lvcreate(1M)).
Sharable Option, Series 800 Only
In the second format of the command line shown in
SYNOPSIS, the volume group specified in the mapfile
is shared.
vgimport does not activate the imported volume group due to the many possible options at volume group
activation time. To activate the volume group once it has been successfully imported, use the vgchange
command (see vgchange(1M)).
Options and Arguments
vgimport recognizes the following options and arguments:
pv_path The block device path names of a physical volume. This argument is not used with
the -s and related options.
vg_name The path name of the volume group.
-m mapfile Specify the name of the file from which logical volume names and numbers are to be
read. This option is optional when used as in the first command line format of the
SYNOPSIS. If this option is not specified, logical volume names are created using the
default naming convention lvolnn where nn is the logical volume minor number.
When used with the -s option, the volume group specified in the mapfile can be
shared among the exporting system and the importing systems.
-s Sharable option, Series 800 only. When the -s option is specified, then the -p, -v,
and -m options must also be specified. The specified mapfile is the same mapfile
specified by using the vgexport command also using the -p, -m, and -s options.
The mapfile is used to create the volume groups on the importing systems.
-p Preview the actions to be taken but do not update the
/etc/lvmtab file or add the
devices file. This option is best used in conjunction with the
-v option.
-v Print verbose messages including names of the logical volumes.
-f infile Import the set of pv_paths held in the infile into the volume group. This option is
used as an alternative to specifying the pv_paths on the command line. Each pv_path
must appear on a new line in the infile. This option may not be used together with
the
-s option.
WARNINGS
The following warnings should only apply to the -s option when importing devices such as (NIKE) or disks
with alternate path:
Since the -s option causes a search on the system for each disks with the same
vg_id. When vgim-
port
reconstruct the newly imported volume group entry in /etc/lvmtab file, the order of disks could
be different than it was before. And the following will happen:
HP-UX Release 11i: December 2000 − 1 − Section 1M−−1027
___
___