importing vg after system crash

[Kip Cooper]

I'm working on disaster & recovery plans. After a system goes down I am attaching the external storage to another box and trying to import the VG's. I'm not using a map file. Here is the message I'm getting when I do vgimport.
# vgimport /dev/vg04 /dev/dsk/c7t0d0
Creating "/etc/lvmtab".
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.
vgimport: Quorum not present, or some physical volume(s) are missing.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating
the volume group.

This is what vgchange comes back with.
# vgchange -a y /dev/vgdc
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk
/c7t0d0":
Cross-device link
vgchange: Warning: couldn't query physical volume "/dev/dsk/c7t0d0":
The specified path does not correspond to physical volume attached to this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg03":
Quorum not present, or some physical volume(s) are missing.

I would appreciate any help I can get.
Thanks

[Peggy Fong]

Kip

Since you are attaching the disks to another processor you can ignore the CPU messages. However you are specifying a disk name. The disk name on the new system is probably not the same name as on the old system. So you either need to know the name on the recovery system and use that disk name (plus the vg error message indicates there is more than one disk in this vg).

Look at man on vgimport. I believe you can use the "-s" option with or without a map file. So if you do a vgimport -s vg04 then all the disks will be scanned for the id's on the disks that belong to vg04.

HTH,
Peggy

[Kip Cooper]

I made a few typos in my posting. The VG names are all the same.

[James R. Ferguson]

Hi Kip:

Perchance do have alternate links to this disk?

...JRF...

[Kip Cooper]

JRF

The disk is a LUN on a fiber channel array that is being served up to the HPUX box by SAN software. The SAN software is also mirroring the LUN before serving it up. Hope this helps.

Kip

[KapilRaj · Accepted solution]

hi Kip,

I have the solution for you. As per my understanding the prob. is You don't have a VGs to PVs map okay. and you are trying to import. Okay. Follow the procedure

#vgscan

Actually this command is used to recreate /etc/lvmtab but here it will not create the lvmtab. but the command will segregate the disks into some sets. like,

/dev/dsk/c0t5d0
/dev/dsk/c1t4d0

these disks belong to a single vg

/dev/dsk/c8t4d0
/dev/dsk/c4t8d0
/dev/dsk/c5t5d0

these disks belongs to a single vg

then do a vgimport
#mkdir /dev/vgXX
#mknod /dev/vgXX/group c 64 0xNN0000
#vgimport /dev/vgXX /dev/dsk/c8t4d0 /dev/dsk/c4t8d0 /dev/dsk/c5t5d0


Do the same for all the sets and mount each and every filesystem and segregate them.

Best of luck

Kaps

[KapilRaj]

hi kip,

can you throw some light abt your LUN. is it a mirro set / RAID set ? if yes do a rebuild and try to activate the volume group. have you removed any controller from the LUN BOX ?. if yes put it back. Are you sure there is only one LUN in the BOX. can you send ioscan -fnC disk out put ?.

Best of luck

Kaps

[Kip Cooper]

Thanks to all who responded. I appreciate you taking the time, especially Kaps who had the solution to the my problem. As stated in his response I needed to import each PV into the VG.

Thanks Again
Kip