vgmove.1m (2010 09)

vgmove(1M) vgmove(1M)

using this diskmapﬁle .

-i diskfile Specify the name of the ﬁle containing the list of destination disks. This

option is used with the -f

option to generate the diskmapﬁle.

When the

-i option is used, no volume group data is moved.

-p Preview the actions to be taken but do not move any volume group data.

Shared Volume Group Considerations

For volume group version 1.0 and 2.0,

vgmove cannot be used if the volume group is activated in shared

mode. For volume groups version 2.1 (or higher),

vgmove can be performed when activated in either

shared, exclusive, or standalone mode.

Note that the

lvmpud daemon must be running on all the nodes sharing a volume group activated in

shared mode. See lvmpud(1M).

When a node wants to share the volume group, the user must ﬁrst execute a

vgimport,ifphysical

volumes were moved in or out of the volume group at the time the volume group was not activated on that

node.

LVM shared mode is currently only available in Serviceguard clusters.

Note that for volume group version 2.2 or higher,

vgmove is disallowed in shared mode if it has

snapshots associated with it. See lvm (7) for more information about snapshots.

EXTERNAL INFLUENCES

Environment Variables

LANG determines the language in which messages are displayed.

LANG is not speciﬁed 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

Move data in volume group

/dev/vg00 from /dev/disk/disk1

to /dev/disk/disk2. After the

migration, remove

/dev/disk/disk1

from the volume group:

echo "/dev/disk/disk1 /dev/disk/disk2" > diskmap.txt

vgmove -f diskmap.txt /dev/vg00

Generate a source to destination disk map ﬁle for /dev/vg00, where the destination disks are

/dev/disk/disk3 and

/dev/disk/disk4:

cat>newdisks.txt

/dev/disk/disk3

/dev/disk/disk4

vgmove -i newdisks.txt -f diskmap.txt /dev/vg00