Data Migration -- attempting vgexport/vgimport

[Bill Schultz_1]

We are migrating from an Xp 256 to and EMC DMX 1000.

I have a 2 node cluster that I am moving from the 256 to the DMX.

One of the nodes is running 11.00 and is currently live on the XP, the other node has just been upgraded to 11.11 and is now connected to the DMX.

I am attempting to export out the VG information from Node 1 and import it on node 2 so I can move the data.

The commands I used to do both are:

on node 1:
vgexport -p -m vg13.map vg13

on node 2:
vgimport -m vg13.map vg13 /dev/dsk/c10t3d2 /dev/dsk/c10t3d3 /dev/dsk/c10t3d4

I am doing it this way so I don't have to add all of the lvols. While there aren't many lvols in this cluster, I have to do this many more times and there are 100 of lvols on the other clusters.

Anyway, this is the error I get:

Physical Volume "/dev/dsk/c10t3d2" is not part of a Volume Group
Physical Volume "/dev/dsk/c10t3d3" is not part of a Volume Group
Physical Volume "/dev/dsk/c10t3d4" is not part of a Volume Group

In preparation for the vgimport I did the following:

pvcreate the disk
mkdir /dev/vg13
mknod /dev/vg13/group c 64 0x0100000

Am I missing something?

Thanks for the advise and help.

[Sanjay_6]

Hi Bill,

The vgexport and vgimport command helps when you want to move the vg on one storage to another vg on another/same server on the same storage.

This means if you are doing vgexport on node1 for a vg on xp256 and trying to do a vgimport for this vg on node2, you should have the xp 256 connected to node2 and the pv names be specified if the path to these pv's is different on node2.

You cannot use vgexport/vgimport to move the vg/lvs from one node to another if the storage is different or to save you the trouble of creating the vg and lv on node2 for another storage.

If you have EMC connected to node2 and you want to recreate the same luns and all on node2, you'll have to do pvcreate/vgcreate/vgextend/lvcreate to create the luns on the new storage. vgexport/vgimport is not going to work for you in this situation.

Hope this helps.

Regds

[Bill Schultz_1]

Yeah, I kind of thought you someone was going to tell me that....DOG GONE IT....Uugh.

Thanks.

[Sanjay_6]

Hi,

Take a look at this thread,

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000075725050

The itrc doc id is KBRC00014628.

this link shows you how to move the vg from one node to another. Which means how to move the storage from one server to another.

Also remember you have to use the -s option while doing a vgexport/vgimport if you are moving the storage from one node to another.

Hope this helps.

Regds

[Bill Schultz_1]

It's not letting me log in.

[Sanjay_6]

Hi,

I see that you are in USA, so you should be able to access the doc since the link is from US itrc. Try and see if you can open the doc using the doc id in this link,

http://www1.itrc.hp.com/service/cki/enterService.do

Hope this helps.

Regds

[Bill Schultz_2]

I was able to get in, I had to create a new account, but I finally got in.

I've seen that before. The -s would only be used if the disk/controller numbers were the same and here they are not.

[Sanjay_6]

Hi Bill,

The -s option adds the VGID of the vg in the map file. The VGID is a unique identifier for the vg and all the disks/luns or disks that are part of this has this VGID.

I do not think what the -s option only applies to vgexport/vgimport in situations where the lun/controller numbers are same.

ITRC doc is "3100632244" tells you how to import a vg that was exported without the -s option in vgexport.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062904811

However, in your situation this whole things is of no use, unless you are migrating the storage from one node to another (which you are not, at present).

I do not think there is any option for you other than to create the vg and lv's on the EMC. vgexport/vgimport is not the solution for you in this situation.

Hope this helps.

Regds

[Rita C Workman]

Greetings Bill,

Not so long ago I had to migrate everything off one disk array onto another (albeit same mfg). But I think what we did, and the great tips that JRF and John Poff gave will be helpful to you.

Here's the thread:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=51818

Rgrds,
Rita

..by they way, - it went off clean as could be !...

[Edgar_8]

Hi Rita,

I know it has been some time back, but can you recall the process you guys followed to migrate the data from old array to new array?

Thanks in advance!