AutoRestore Mirrored Disks Using Ignite

[Doug_85]

Running HP-UX 11.0 on LServer

I've used "make_recovery -p" to generate a recovery file in the following directory.
/var/opt/ignite/recovery/config.recover

I'm using the "post_config_cmds" to automatically restore the mirrors after the system has been restored. I will also be running "instl_adm -T -f config.recover" to check my syntax.

I've modified the original script to reflect the 2 drives that are currently mirrored. I noticed that the script does not show which disks they will be mirrored to. Does the script
automatically find the same drive size and establish a mirror when using lvextend?

Attached is the post_config_cmd that's been modified to match both my mirror drives.

Thanks,
Doug

[Steven E. Protter]

make_recovery is obsolete

If you use make_tape_recovery and boot off that mirroring will be preserved.

I've done it several times on rp5450 servers and with an rp5450 tape on a rp5470 server in HP's performance center.

SEP

[Pete Randall]

Unless that is a new enhancement, I don't believe that mirrors are recovered. From the man page:

"The make_tape_recovery tool will create a recovery backup for a system with mirrored disks but it will not restore the mirrored disk configuration. If the system is later recovered, previously mirrored volumes will no longer be mirrored. They can be manually re-mirrored after the system is up. Using the config.local file in the clients directory, you can specify the LVM commands to restore mirrored disks to be executed automatically after the system has been restored. For more details, see the white paper /opt/ignite/share/doc/diskmirror.pdf."


Pete

[Doug_85]

Since we're currently using make_recovery -A to create the ignite tape. Should we update to make_tape_recovery? As stated above, the new application will enable us to save mirror configurations? Also is the new application backwards compatible with make_recovery?

Thanks,
Doug

[Patrick Wallek]

Yes, you should start using make_tape_recovery.

But, NO it still will not restore your mirror configuration. I have always preferred to rebuild my mirrors by hand afterwards. My logic for that is -- If you have to use an Ignite tape to recover a production system, you want to get it back up and runnin ASAP. Re-mirroring would only add unnecessary time to that. Mirroring the VG00 does not use many CPU cycles so it shouldn't be a problem doing it on a live system.

[Pete Randall]

Doug,

The standard answer from Forums folk and HP folk is to upgrade to the latest version of Ignite:

http://www.software.hp.com/products/IUX/index.html

There have been numerous enhancements and fixes incorporated into the newer versions and it's definitely worth the time to upgrade. Once you do, your syntax will change to something like "make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00".

You will have to manually re-create the mirrors or follow the document I pointed out in my previous post.


Pete

[Doug_85]

Would it be less labor intensive to use SAM to re-establish the mirrors after restoring the system?

[Patrick Wallek · Accepted solution]

I wouldn't use SAM for that. There are very things I trust SAM to do.

Re-establishing mirrors is not hard.

This is how I create my VG00 mirrors and make them bootable:

# pvcreate -B /dev/rdsk/c?t?d?
# vgextend /dev/vg00 /dev/dsk/c?t?d?
# mkboot /dev/rdsk/c?t?d?

Do this step for the original and mirror disk
# mkboot -a "hpux -lq" /dev/rdsk/c?t?d?

If you have diagnostics installed:

If HP-UX is 64-bit:
# mkboot -b /usr/sbin/diag/lig/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If HP-UX is 32-bit:
# mkboot -b /usr/sbin/diag/lig/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

# for LV in 1 2 3 4 5 6 7 8
>do
>lvextend -m 1 /dev/vg00/lvol${LV} /dev/dsk/c?t?d?
>done

If you have more than LVOL1 thru LVOL8 in VG00 modify the for statement above as appropriate.

To verify that everything looks OK do an:

# lvlnboot -v

You can also verify and set your boot paths via the 'setboot' command.

[Sanjay_6]

Hi Doug,

Maybe this link will help,

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000073094375

The itrc doc id is KBRC00012813.

You will have to do a little custom scripting and use "post_config_cmd " section of the recovery process.

Hope this helps.

Regds

[Steven E. Protter]

Mirroring by hand is much more fun. Its also educational.

pvcreate -B /dev/rdsk/c1t0d0 #use real disk

mkboot -l /dev/rdsk/c1t0d0
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c1t0d0 # use real disk


# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If you are running 64-bit OS:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?


vgextend /dev/vg00 /dev/dsk/c1t0d0 # same thing
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t0d0

# real disk. repeat for other lvols

lvlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk


Let me confirm to Pete that I have done a boot tape recovery with make_tape_recovery vg00 at least five times and come out of it with mirroring preserved.

I'm not in a position to test that right not, but I've got notes that are very clear on the topic. It would be nice if someone else confirmed. I might need to get my brain mri'd tonight instead of my sore ankle.

I'm 99.8% sure. I'm never 100% sure any more.

SEP

[Pete Randall]

Steve,

As of September, 2004, Edition 3 of the man pages ( http://www.software.hp.com/product/IUX/docs/5187-4555.pdf ) still contains the quote I referenced above that states that mirrors are not recovered.


Pete

[Michael Roberts_3]

Ignite does not contain mirror specific options in the prodcut; however the ability to use the post_config_cmd hooks to create mirrors is documented in the Ignite product. On your Ignite server look in /opt/ignite/share/doc for diskmirror.pdf