Business Copy vgimport problems

[Juan M Leon]

Hello everyone, I hope someone can point me where i am making a mistake.
I have 2 servers, one is my prod server and the second server is my dev/qa. on the second server I have 2 s-vols ( 1 p-vol, prod server)
The second server has set 2 device groups
groupa and groupb
Groupa is my first s-vol and is the qa env.
groupb is new and will be dev env.
I just create the groupb instance and paircreate, pairdisplay and pairsplit with no problems. However when I try to vgimport I get an error indicating that the disk is in the lvmtab. the disk reported is not in the list of disk to be part of this new vg.
Please see attachement.


Thank you

[Torsten.]

What is the contents of your map file?

[Juan M Leon]

VGID ffbb40503ee5dcae
1 lv_nstarprdoraarc01
2 lv_nstarprdoradata10
3 lv_nstarprdoralog01
4 lv_nstarprdoralog02
5 lv_nstarprdoralog01m
6 lv_nstarprdoralog02m
7 lv_nstarprdorasw01
8 lv_nstarprd
9 lv_varoptoraclenstarprd
10 lvmaestro

[Eric SAUBIGNAC]

Bonsoir Juan,

-s is mutually exclusive with the disk list. With -s vgimport scans all disks an search for the vgid present in the map file. It explains why it finds /dev/dsk/c87t0d0.

Could you try without '-s' option ?

Something else : what is this "vgchgid -f /dev/rdsk/c45t7d6" on just one disk and not on all the disks that compose the VG ??? Not good at all and I Think you will have to "business copy" those LUNs again before trying an other vgimport

Regards

Eric

[likid0]

yes, The things that I can see is you have to run the vgimport without the -s and put the disk-list.

Also you should run the vgchgid on all the disks on the VG.


I am uploading the script i use to import BC disks into vgs on another machine.

[Juan M Leon]

Orange / Erick

The "-s" is good point. I guess the problem resides at the begining on BC. I am resyncing the copies now before try another vgimport.
When I execute the vgimport withoout the "-s" optino i got the following error

Beginning the import process on Volume Group "/dev/vg_nstaraecm4".
vgimport: The Physical Volumes specified on the command line
do not belong to the same Volume Group.


I am resyncing and retyr again.

Thank you

[likid0]

If you get that error, you should check that your disk-list is correct, looks like you are trying to import a disk that doesn't belong to that VG.

[likid0]

sorry, i pressed summit.

One question are you doing vgchgid on all the disks in the vg?.

And example:

2. Change the VGID on the BCV disks.

vgchgid /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d1 /dev/rdsk/c0t0d2

3. Make a new volume group using the BCV disks.

mkdir /dev/vgbcv
mknod /dev/vgbcv/group c 64 0x040000

4. Import the BCV disks into the new volume group.

vgimport /dev/vgbcv /dev/dsk/c0t0d0 /dev/dsk/c0t0d1 /dev/dsk/c0t0d2

5. Activate the new volume group.

vgchange -a y /dev/vgbcv

[Juan M Leon]

Orange,
Yes I created the directorya nd the group file.
also did the vgchgid -f and the next step was the vgimport

[Eric SAUBIGNAC]

Bonjour Juan,

You said "Beginning the import process on Volume Group "/dev/vg_nstaraecm4".
vgimport: The Physical Volumes specified on the command line do not belong to the same Volume Group."

It is obviously due to your vgchgid on only one disk. So synchronize again, vgchgid on all BC disks, then vgimport without -s. It will work fine

Eric