cancel
Showing results for 
Search instead for 
Did you mean: 

vgexport/vgimport

 
SOLVED
Go to solution
toni osta
Frequent Advisor

vgexport/vgimport

Hi
I have an HP server connected to an HPEVA storage
there is one volume group crated on the storage with their file systems
I need to move these file systems to an other HPux server connected to the same EVA

can i present the same LUN to the new server , vgexport the volume group on the initial node by saving the map file then vgimporting it to the new node ? can i do it even if the volume groups does not have the same minor number ?

Thnak you
12 REPLIES 12
Pete Randall
Outstanding Contributor
Solution

Re: vgexport/vgimport

1) Deactivate the vg:
vgchange -a n /dev/vgYY

2) Export
vgexport -s -m /tmp/vgYYmap /dev/vgYY

3) Copy the map to the new server and present the LUN to the new server

4) mkdir /dev/vgYY

5) mknod /dev/vgYY/group c64 0xYY0000

6) vgimport -s -m /tmp/vgYYmap /dev/vgYY

7) vgchange -a y /dev/vgYY


Pete

Pete
toni osta
Frequent Advisor

Re: vgexport/vgimport

Thank you Pete
but i need these two infos :

- it will work even the volume groups does not have the same minor number ?
- is it necessary to have the same volume group name ?
- is it necessary to use -s

Thank you
Pete Randall
Outstanding Contributor

Re: vgexport/vgimport

The new server knows nothing of the VG's past history so you can change the name from vgNN to vgYY and the minor number from NN to YY with no problem at all. Using the -s option is simply a convenience so that you don't have to specify the device(s) that will make up the VG. It is not necessary.


Pete

Pete
P Arumugavel
Respected Contributor

Re: vgexport/vgimport

- it will work even the volume groups does not have the same minor number ?
Yes, it will work.
- is it necessary to have the same volume group name ?
No, It can be any as you desire.
- is it necessary to use -s
No, it is not essential.
Simple steps:
1.Make the volume group unavailable
# vgchange -a n /dev/vgxx
2.Export the the disk while creating a logical volume map file.
# vgexport -v -m data_map /dev/vgxx
3.Move the data_map file to the new system.
4.On the new system recreate the volume group directory
# mkdir /dev/vgyy
# mknod /dev/vgyy/group c 64 0xyy000
5.Import the disks to the new system
# vgimport -v -m data_map /dev/vgyy /dev/dsk/c2t1d0 /dev/dsk/c2t2d0
7.Enable the new volume group
#vgchange -a y /dev/vgyy
Rgds...
Benoy Daniel
Trusted Contributor

Re: vgexport/vgimport

You cannot make sure the device file is going to be same when you try to import in another node. So it is better to use -s option while doing vgexport and vgimport.
P Arumugavel
Respected Contributor

Re: vgexport/vgimport

Hi BD...
Please get me understood, what is -s going to do when device file is getting changed. Note that the volume group is removed from the exporting system and will be used by the importing system only.

Rgds...
johnsonpk
Honored Contributor

Re: vgexport/vgimport

It is better and recomanded to use -s option during vgexport and vgimport process as it will scan and identify the correct disk which you moved from the previous node .

You can also do it without -s option .. but in that case you have to identify the correct disk which you moved from the first node and need to give it with vgimport command (It is not necessary that the device file for the disk which you moved from first node to second node will have identical device file )

regards!
Johnson
toni osta
Frequent Advisor

Re: vgexport/vgimport

the HPUX version is 11iV1 so all the commands above are supported ?
James R. Ferguson
Acclaimed Contributor

Re: vgexport/vgimport

Hi Toni:

> the HPUX version is 11iV1 so all the commands above are supported ?

Yes. I suggest you inspect the 11.11 manpages for more information:

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01911800/c01911800.pdf

Regards!

...JRF...