Moving LV To New Machine

[Bryn M. Reeves]

On Fri, 2010-02-12 at 16:26 +0000, Dave Cross wrote:
> On 11 February 2010 16:04, Jamie Bohr <jamiebohr at gmail.com> wrote:
> > I've done this many times with HP-UX using vgexport and vgimport, have you
> > looked at those?
> 
> Hadn't heard of them. I'll investigate. Thanks.

All they do on LVM2 is to set/clear the EXPORTED flag on the VG and PV
status - there is no requirement to export the VG before moving storage
between machines (I normally don't).

In large environments it can be convenient to use as it makes it clear
(in the VG metadata) which VGs are imported/exported in the on-disk data
but it's not a necessary step when moving disks around.

Regards,
Bryn.

# diff -Nurp /tmp/tvg0-before-export /tmp/tvg0-after-export 
--- /tmp/tvg0-before-export	2010-02-15 11:15:10.000000000 +0000
+++ /tmp/tvg0-after-export	2010-02-15 11:15:37.000000000 +0000
@@ -1,4 +1,4 @@
-# Generated by LVM2 version 2.02.46-RHEL5 (2009-06-18): Mon Feb 15
11:14:59 2010
+# Generated by LVM2 version 2.02.46-RHEL5 (2009-06-18): Mon Feb 15
11:15:33 2010
 
 contents = "Text Format Volume Group"
 version = 1
@@ -6,12 +6,12 @@ version = 1
 description = "Created *after* executing 'vgcfgbackup tvg0'"
 
 creation_host = "pe1950-5.gsslab.fab.redhat.com"	# Linux
pe1950-5.gsslab.fab.redhat.com 2.6.18-182.el5 #1 SMP Tue Dec 15 21:28:29
EST 2009 x86_64
-creation_time = 1266232499	# Mon Feb 15 11:14:59 2010
+creation_time = 1266232533	# Mon Feb 15 11:15:33 2010
 
 tvg0 {
 	id = "5P3fkI-pH30-xV6t-EiL8-89PZ-MGaw-mjRX7t"
-	seqno = 2
-	status = ["RESIZEABLE", "READ", "WRITE"]
+	seqno = 3
+	status = ["EXPORTED", "RESIZEABLE", "READ", "WRITE"]
 	flags = []
 	extent_size = 8192		# 4 Megabytes
 	max_lv = 0
@@ -23,7 +23,7 @@ tvg0 {
 			id = "OChkmm-N0RX-ccj0-9uXU-gLUc-Y9Hc-xioVQy"
 			device = "/dev/loop0"	# Hint only
 
-			status = ["ALLOCATABLE"]
+			status = ["ALLOCATABLE", "EXPORTED"]
 			flags = []
 			dev_size = 1048576	# 512 Megabytes
 			pe_start = 384