|Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
May the source be with you, but remember the KISS principle ;-)
Bigger doesn't imply better. Bigger often is a sign of obesity, of lost control, of overcomplexity, of cancerous cells
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.
First, make sure that no users are accessing files on the active volume, then unmount it
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 deactivatedIt is now necessary to export the volume group. This prevents it from being accessed on the ``old'' host system and prepares disks to be physically removed.
# vgexport design vgexport -- volume group "design" successfully exportedWhen the machine is next shut down, the disk can be removed and then connected to it's new machine
When plugged into the new system those disks will 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 We can now import the volume group (which also activates it) and mount the file system.
# vgimport design Volume group "vg" successfully imported
You must activate the volume group before you can access it.
# vgchange -ay design # mkdir -p /mnt/design/users # mount /dev/design/users /mnt/design/users
Moving a Volume Group to Another System
You can move an entire LVM volume group to another system. It is recommended that you use the
vgimportcommands when you do this.
vgexport command makes an inactive volume group
inaccessible to the system, which allows you to detach its physical
vgimport command makes a volume group accessible
to a machine again after the
vgexport command has made
To move a volume group form one system to another, perform the following steps:
-a nargument of the
vgchangecommand to mark the volume group as inactive, which prevents any further activity on the volume group.
vgexportcommand to export the volume group. This prevents it from being accessed by the system from which you are removing it.
After you export the volume group, the physical volume will
show up as being in an exported volume group when you execute
pvscan command, as in the following example.
pvscanPV /dev/sda1 is in exported VG myvg [17.15 GB / 7.15 GB free] PV /dev/sdc1 is in exported VG myvg [17.15 GB / 15.15 GB free] PV /dev/sdd1 is in exported VG myvg [17.15 GB / 15.15 GB free] ...
When the system is next shut down, you can unplug the disks that constitute the volume group and connect them to the new system.
vgimportcommand to import the volume group, making it accessible to the new system.
-a yargument of the
Linux Online - Moving a volume group to another system
vgexport - Linux Command - Unix Command
LVM Export - lvm, export
Creating and Exporting LVM Volume Groups
Moving a volume group to another system
Common LVM Tasks
LVM – An introduction " Server Management Tips by SupportPRO