Ignite-UX recovery automation of mirroring

[John Pyle]

Is there a default for which drive is recovered during make_recovery -r
I have a standard K370 with the root disks configured as listed below (lvlnboot -v). If I were to recover from a make_recovery tape which drive would be overwritten with the tape information? I ask this to help me understand after reading the document "Ignite-UX and Mirrored Disks" (I pasted the script mentioned in this doc below) and finding that I can automate this process. I don't see how I can know in advance which disk to place in the script to be pvcreated and then added into vg00. It seems to me if I guessed wrong I would over wright the good disk and then re-mirror root with the bad? I looked through the man page and the admin guide for IUX but can seem to find this information.

***** lvlnboot -v *****
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t5d0 (10/0.5.0) -- Boot Disk
/dev/dsk/c2t6d0 (10/0.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t5d0
/dev/dsk/c2t6d0
Root: lvol3 on: /dev/dsk/c2t5d0
/dev/dsk/c2t6d0
Swap: lvol2 on: /dev/dsk/c2t5d0
/dev/dsk/c2t6d0
Dump: lvol2 on: /dev/dsk/c2t5d0, 0

** Script to be added at the end of config.recover **
vgreduce /dev/vg00 /dev/dsk/c0t5d0
# Make the disk contain a boot area.
pvcreate -f -B /dev/rdsk/c0t5d0
# Add the mirrored disk back to the group.
vgextend /dev/vg00 /dev/dsk/c0t5d0
# Copy the boot area to the disk.
mkboot /dev/rdsk/c0t5d0
# Turn off the quorum requirement
mkboot -a \"hpux -lq\" /dev/rdsk/c0t5d0
# Allocate the mirrors. Mirrors must be allocated for all
# logical volumes that were previously mirrored. This
# example illustrates primary swap and root. You should
# add others as needed. If /stand is in a separate volume, you
# should do an lvextend for it first.
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c0t5d0
lvextend -m 1 /dev/vg00/lvol2 /dev/dsk/c0t5d0
# Update the BDRA and the LABEL file.
lvlnboot -R

[Patrick Wallek · Accepted solution]

The best way to be sure about which drive your system is being restored to when recovering with a make_recovery tape is to make sure you do the Interactive install and select which drive you want the system recovered to. This would then allow you to script the re-mirroring of the root drive a be comfortable that your mirroring is being done correctly.

I personally am not a big fan of automating the re-mirror of the root drive should I have to recover from the ignite tape. The way I figure it is that if I have to recover from the tape, I probably want to get the system back up ASAP and the mirroring will only add time to that. I can always re-mirror the drives manually at a later time, after the system is back up and running.

[James R. Ferguson]

Hi John:

Patrick said it for me too!

...JRF...

[John Pyle]

Very good point. Thank you for the quick responce.

[magnus linner]

If you use make_recovery and chose to run the restore in interactive mode. Ignite will do a reset on a lot of the systemfiles. I think that Ignite do not even restore all the files.
Use the new tool make_tape_recovery which restore all the files and do not reset the system files if you chose to use the interactice mode.