Move JBOD to another system

[Coolmar]

Hi everyone,

I have a system that died with a bunch of disks attached (JBOD) with a SCSI cable. The system has died (hardware error) and I need to move the JBOD to another system. Can someone tell me the steps or point me to a document that will guide me through bringing up these disks (vgs, lvols, etc) on another system?

Thanks!

[Pete Randall · Accepted solution]

Sally,

It's really just a matter of running vgimport. Hopefully, you've got some kind of map of what VG's and LV's existed - that will make it easier.

mkdir /dev/vg01
mknod /dev/vg01/group c 64 0x010000 (the minor number (01) has to be unique)
vgimport -s -m /tmp/vg01map /dev/vg01
vgchange -a y /dev/vg01

Now, the vgimport command may well not work with the -s option and you'll have to specify which disks belong to the VG and you probably don't have a map file so you can leave off the -m option. The -m is only really useful if you had non-standard logical volume names (other than lvol1, lvol2, etc).

So, probably in your case, it will be:

vgimport -v /dev/vg01 /dev/dsk/c0t1d0 /dev/dsk/c0t3d0

or something similar.


Pete

[Coolmar]

Thanks for the reply. Unfortunately, this is not a system that I have managed or even seen. Therefore, I can guarantee there is no map...I am assuming these disks are part of vg01 but I really don't know. They could all have been added to vg00 even. So I don't want to clobber what is already there.

[Pete Randall]

Ouch! Isn't there someone who can give you a hint? I suppose you could try vgimporting all of them into one VG and see what happens. The logical volumes are *probably* standard names, so we don't have to worry about them, it's just figuring out the VG layout. It doesn't matter what the vg name was by the way, you can call it whatever you want this time around.


Pete

[Pete Randall]

Actually, try the -s option! That just might do it:

vgimport -s /dev/vg01


Pete

[Devender Khatana]

Sally,

Is it resolved ? If not you can try the SAM options to import VG , it will automatically scan all the disks and will provide the nos. of VGs to be imported under Importable VG's Column. It is a very good practice when you do not know about the past configuration. But beware disk ID's should not be changed and all the disk should be accessible.
Full Path is
SAM->Disks and File Systems->Volumes Groups->Action->Import

HTH,
Devender