13.6. Moving a volume group to another system
It is quite easy to move a whole volume group to another system if, for example, a user department acquires a new server. To do this we use the vgexport and vgimport commands.
 | vgexport/vgimport is not necessary to move drives from one system to another. It is an administrative policy tool to prevent access to volumes in the time it takes to move them. |
13.6.1. Unmount the file system
First, make sure that no users are accessing files on the active volume, then unmount it
# unmount /mnt/design/users
|
13.6.2. Mark the volume group inactive
Marking the volume group inactive removes it from the kernel and prevents any further activity on it.
# vgchange -an design
vgchange -- volume group "design" successfully deactivated
|
13.6.3. Export the volume group
It is now necessary to export the volume group. This prevents it from being accessed on the ``old'' host system and prepares it to be removed.
# vgexport design
vgexport -- volume group "design" successfully exported
|
13.6.4. Import the volume group
When plugged into the new system it becomes /dev/sdb so an initial pvscan shows:
# pvscan
pvscan -- reading all physical volumes (this may take a while...)
pvscan -- inactive PV "/dev/sdb1" is in EXPORTED VG "design" [996 MB / 996 MB free]
pvscan -- inactive PV "/dev/sdb2" is in EXPORTED VG "design" [996 MB / 244 MB free]
pvscan -- total: 2 [1.95 GB] / in use: 2 [1.95 GB] / in no VG: 0 [0]
|
If you are importing on an LVM 2 system, run:
# vgimport design
Volume group "vg" successfully imported
|
If you are importing on an LVM 1 system, add the PVs that need to be imported:
# vgimport design /dev/sdb1 /dev/sdb2
vgimport -- doing automatic backup of volume group "design"
vgimport -- volume group "design" successfully imported and activated
|