Logical Volumes from a make_recovery

[Pamela Hammitt]

Hi my server crashed hard, I think it's dead. In the meantime I'm trying to restore the OE and data disks from a make_recovery tape. (Using another server) I used the command
make_recovery -v -AC -d /dev/rmt/1m (HPUX 10.20)

When I boot from the recovery tape to make a new system harddrive It only restores vg00 The other three harddrives are listed as unused and the other volume groups and lvols don't show up....They are in /etc/fstab. They don't list in SAM. When I remove them from fstab, and try to recreate them, I says that the /dev files already exist and won't create...

HELP!!!

Thanks

[Robert-Jan Goossens]

Hi Pamela,

Could you post

# ll /dev/*/group

Do you still have the disks which where connected to the old server ?

Regards,
Robert-Jan

[Pamela Hammitt]

Yes. I only replaced the system disk dsk6. the other 3 are the data disks from the old system.

[Pete Randall · Accepted solution]

Then you should just need to import them. The device files seem to already be there, so just run vgimport against them.


Pete

[Robert-Jan Goossens]

ok,

you could vgimport the disks, but you need to know what volume group was on what disk.

Otherwise you need to create dummy vg's

Check this doc for more info.

US
http://www2.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000072570325

Europe
http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000072570325

[Bill Hassell]

This is exactly normal. VG00 is restored because that's what is needed in order to bootup again. Assuming that the other volume groups are still intact, you would normally run SAM and import the other volume groups. However, since you have /dev vgXX directories, I would remove them, then start SAM and import them. SAM's VG import capability is quite interactive and will show you which disk(s) belong to a volume group. NOTE: the disks have a unique serial number that is used to bind the disk(s) into a single volume but the name of the original volume group is not stored on the disk. So you need to know which disks belong to a specific VG. One way to do this (if you are reasonable up to date on patches for this obsolete opsystem) is to look at the /etc/lvmconf directory. LVM was patched a long timne ago to automatically run the vgcfgbackup command when creating or changing volume groups. To list all your volume group information, create this script into a file:

for VG in /etc/lvmconf/*.conf
do
VGCONF=${VG##*/}
VG=${VGCONF%%.*}
echo
vgcfgrestore -n $VG -l
cat $VG.mapfile
done

It will summarize what your volume groups were the last time any of them were changed. NOTE: The disk device file names may have changed after your Ignite restoration. But the lvol names will match the VG name, and the VG serial number will bind all the disks in a single VG together.

Or you can just name each VG in sequence (vg01 vg02...) as you import them in SAM and then temporarily mount one of the lvols to identify the file/directories. Now modify fstab for the (possibly) new VG names and lvol names.

[Bill Hassell]

Oops, one minor fix: The cat for mapfiles works only if you are cd into the /etc/lvmconf directory. Use this version which will work anywhere:

for VG in /etc/lvmconf/*.conf
do
VGCONF=${VG##*/}
VG=${VGCONF%%.*}
echo
echo $VG
vgcfgrestore -n $VG -l
cat /etc/lvmconf/$VG.mapfile
done

[Steven E. Protter]

If in the future you used make_tape_recovery and included only vg00, on restore the recovery tape would activate untouched all your other volume groups.

This is a little easer than the process laid out by Bill. make_recovery does work, but its obsolete and recommended that you use make_tape_recovery.

If your Ignite version is anywhere near current, its been putting warnings on the screen and in the log about this.

Good luck, you've gotten good instructions that worked well for me years ago.

SEP