How to migrate the LVM Configuration and VGs from 11iv2 to 11iv3 (HP-UX)

LVM config migration to 11i v3

While migrating VGs from 11iv2 to 11iv3, make sure that you have the latest LVM patches also and have a look at (only) few limitations of 11iv2 Vgs being migrated to 11iv3.

Refer to compatibilty notes on page 14 of 

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01919369/c01919369.pdf (BSC link updated by admin)

Please note that the above link may have changed refer to the latest if so.

Also it is to be understood that the New generation Mass storage stack on 11iv3 has inbuilt Dynamic multipathing in it. While the legacy device files are well supported on 11iv3, you can choose to have the persistent DSFs that is agile view reflecting in your VGs.

-

Create MAP files of the VGs on 11iv2 using the command as below.

on 11iv2: (please note -p is for preview mode which just creates the map file and does not export the VG physically as such)

vgexport -p -v -s -m <map_file_name> <vg_name>

Keep these map files handy.

Post that import the VGs using the map file on 11iv3 OS

mkdir /dev/vg01

mknod /dev/vg01/group c 64 0x0Y0000

make sure that 0x0y0000 is unique on the system.

vgimport -p -v -s -m <map_file_name> <vg_name>

When the preview is satisfactory and there are no errors. 

Import without the -p option as below

vgimport -v -s -m <map_file_name> 

So once you have imported those VGs from the 11iv2 system to the 11iv3 system, once again re-export and import that VG in the following way. (This is not mandatory though and is needed only if you want to have support of persistent DSF on the VGs)

After you have imported the vgs to the 11iv3 system, say vg01 then re-export

It is worth noting that in general before actual export of a VG the VG has to be deactivated (using vgchange -a n which can be done only if the LVs in the VG are not open that is unmounted).

vgexport -p -v -s -N -m /tmp/vg01.map /dev/vg01

vgexport /dev/vg01

mkdir /dev/vg01

mknod /dev/vg01/group c 64 0x0Y0000

make sure that 0x0y0000 is unique on the system.

vgimport -v -s -N -m /tmp/vg01.map /dev/vg01

Activate the VGs using vgchange -a y <VG_NAME>


Mount the File systems.

For more see man pages of the command vgimport and vgexport also the 11iv3 Next Generation Mass Storage Stack

More on the vgexport/vgimport command on HP-UX

Please note: -f and -s options are mutually exclusive for the commands vgimport and vgexport.

vgexport -p -v -s -N -m /tmp/vg01.map /dev/vg01

this shall create the map file with the VGID of the VG in this.

after this

vgimport -v -s -N -m /tmp/vg01.map /dev/vg01

this shall scan all the disks on the system to match the VGID as in the specified map file and shall import those disks in the specified VG.

-f option of vgexport creates a file that keeps the device files in an file file.out

when this file.out is used with a vgimport command this shall scan the disks and those matching the device files in file.out shall be imported in the VG.

note that the Device Files as in 11iv2 can be different to that while the OS is 11iv3, in that case -f option can be erroneous if that can not match the device files in the target OS.

so it is better to use the -s option.