$NetBSD: vgimportclone.8,v 1.1.1.1 2009/12/02 00:26:57 haad Exp $

vgimportclone - import and rename duplicated volume group (e.g. a hardware snapshot) vgimportclone [-n|--basevgname VolumeGroupName] [-i|--import] PhysicalVolume [PhysicalVolume...] vgimportclone is used to import a duplicated VG (e.g. hardware snapshot). Duplicate VG(s) and PV(s) are not able to be used until they are made to coexist with the origin VG(s) and PV(s). vgimportclone renames the VG associated with the specified PV(s) and changes the associated VG and PV UUIDs. See lvm for common options.

-n|--basevgname VolumeGroupName By default the snapshot VG will be renamed to the original name plus a numeric suffix to avoid duplicate naming (e.g. 'test_vg' would be renamed to 'test_vg1'). This option will override the base VG name that is used for all VG renames. If a VG already exists with the specified name a numeric suffix will be added (like the previous example) to make it unique.

-i|--import Import exported Volume Groups. Otherwise VGs that have been exported will not be changed (nor will their associated PVs).

LVM_BINARY The LVM2 binary to use. Defaults to "lvm".

If origin VG test_vg has PVs /dev/loop0 " and " /dev/loop1 and /dev/loop2 " and " /dev/loop3 are respective snapshot PVs of the origin PVs. To rename the VG associated with /dev/loop2 " and " /dev/loop3 from test_vg to test_vg_snap (and change associated VG and PV UUIDs):

\ vgimportclone --basevgname test_vg_snap /dev/loop2 /dev/loop3

lvm (8)