vgexport and vgimport with different device name

[Ricky_4]

Hi All,

We have common storage which eva3000 and using secure path. And there is only one lun defined. Since there is secure path, the rp5470 recognized the single luns from eva3000 as /dev/dsk/c5t1d0 while L2000 as /dev/dsk/c10t1d0. Could we successfully vgexport the rp5470 to L2000 even recognized it with different device name?if yes how could we do it?

Thanks in advance.

Adriatico

[Tom Danzig]

Use the -s option with vgexport. This will add a disk identifier and upon import will only select the devices based on this identifier. See man vgexport for details.

[Sundar_7]

Yes, that is the way to go.

But since this is only one LUN, you can as well mention it in the command line

in rp5XXX

# vgexport -p -s -m /root/mapfile /dev/vgname

in L2000

# mkdir /dev/vgname
# mknod /dev/vgname/group c 64 0xYY0000

# vgimport -v -s -m /root/mapfile /dev/vgname

or

# vgimport -v -m /root/mapfile /dev/vgname /dev/dsk/c10t1d0

-- Sundar

[Prashant Zanwar_4]

Hi,
I didnt get the question properly.
There is a vgchgid command which changes the VGID on given phyisal device disk. Then you can do a vgimport onto a different volume group the same physical disk device.
But do backup your data before doing the vgexport.

vgexport -s -p -m -v vg02.mymap /dev/vgXX -f /path/outfile

vgexport like above is in preview mode, you can take this created mapfile to other host and do a vgimport to create defination of your exisitng VG on other host.

Or

you can omit -p option and do a vgexport on existing volume group, change the VGID on Physical volume. and do a vgimport onto a different VG.

Let us know what exactly you want to do.
Thanks
Prashant

[Sundar_7]

Prashant, I think you have misunderstood the question. No need to execute vgchgid. Adriatico is concerned that the LUN is seen as different device files by the two systems.


Adriatico: You can successfully vgimport (refer my post above) even if the device files are different.

[Todd McDaniel_1]

Just to clarify,

Tom is correct as is Sundar.

IF You include the -s option in both your vgexport from the original box, and vgimport on the new box.

You dont need the disk device defined on import. The VGID of the disk will be read during the vgimport -s command, and the new host will "Find" the disk based on the mapfile you cp'd over to the new host.

[Prashant Zanwar_4]

I got it now and I agree with others that this VG can be imported to the other system irrespective of disk device file.
Cheers
Rgdz
Prashant