Ignite-UX Any issues with Mirror/UX?

[Gino Castoldi_2]

Hi,

I am concerned about recovery
in general because we are planning to upgrade and so if anything does wrong I want to make sure we can recover from a software point of view.

(Of course if there's any H/W boot issues then we need to recover too).

10 point to any good answer.
Thank you
Gino

[Bryan D. Quinn]

Hey Gino,

NO POINTS HERE, THIS IS STRICTLY A FYI ADDITION TO YOUR THREAD.

I have succesfully recovered our V-2600 production server at our Philly hotsite for Disaster Recovery testing purposes, using an Ignite of the box and our backup tapes. It worked like a charm, I did have to do a little manual massaging because of the differences in device files, but everything else was great. If you are restoring to the same hardware it will be seamless, no interaction required. Oh yeah, and this V server is in a MC/SG cluster with another V for failover.

Hope this helps!
-Bryan

[Patrick Wallek]

What exactly are your concerns? Ignite/UX is an excellent tool for recovering a messed up VG00. If you create your tape like this:

# /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00

The above will archive your ENTIRE VG00 volume group, which should comprise your whole OS. If you blow something up and need to recover then you pop in the tape, boot the system from the tape and let Ignite go to work. When it is done you will have your system back to the state it was in when you created the make_tape_recovery tape, with the exception of any VG00 mirroring you may have done.

[Marco Santerre]

As Patrick already mentionned, Ignite/UX is a GREAT tool to recover your OS. If you're planning to upgrade, it is definitely a very good idea to create an Ignite tape.

What this will do is it will recreate your OS and if you incude the inc_entire=vg00, it will recover your whole vg00. Just make sure you have every bit of infortmation concerning other VGs you might have on that system, so you can vgimport them afterward.

[Helen French]

Again, in the event of an upgrade you will be safe if you have the Ignite tape. If you are going to upgrade the OS, then I will also break the mirror, remove primary disk from vg00 and then install new OS on the free'd primary disk. This way you don't need to worry about recovering anything since you have the old OS mirror disk untouched. Once everything is back and running, you can remirror the new OS.

If it's a h/w upgrade, these steps are not required and you will be safe with a good Ignite tape.

[Tim D Fulford]

Remember to pvcreate -B the boot disk & put on the lif info

pvcreate -B /dev/rdsk/
vgextend vg00 /dev/dsk/
mkboot -l /dev/dsk/
cd /usr/sbin/diag/lif
mkboot ???b ./updatediaglif ???p ISL ???p AUTO ???p HPUX ???p LABEL ???p PAD /dev/dsk/
mkboot ???a ???hpux ???lq (;0)/stand/vmunix??? /dev/dsk/

and on the primary disk
cd /usr/sbin/diag/lif
mkboot ???b ./updatediaglif ???p ISL ???p AUTO ???p HPUX ???p LABEL ???p PAD /dev/dsk/
mkboot ???a ???hpux ???lq (;0)/stand/vmunix??? /dev/dsk/

lastly use "setboot" to assign the primary & mirrordisks
setboot -p
setboot -a

Tim

[Isaac_4]

3. Antes de generar la cinta de recuperaci??n, debemos hacer algunas modificaciones al archivo de configuraci??n de Ignite/UX para que al final de la recuperaci??n ejecute los comando LVM para crear el espejo del disco de boot. Para integrar la creaci??n del espejo al proceso de recuperaci??n, debemos primero ejecutar el comando make_recovery en modo preview para luego agregar los comandos LVM para la creaci??n del espejo:

# /opt/ignite/bin/make_recovery ???Apvi ???d /dev/rmt/c2t1d0BEST
4. En el paso anterior es creado el archivo /var/opt/ignite/recovery/config.recover. Este script tiene una secci??n post_config_cmds que es donde se incluyen los comandos para crear el disco espejo despu??s de la recuperaci??n. Edite este archivo y poner los siguientes comandos:

# vi /var/opt/ignite/recovery/config.recover
post_config_cmd +=???
vgreduce /dev/vg00 /dev/dsk/c3t6d0
pvcreate ???f ???B /dev/rdsk/c3t6d0
vgextend /dev/vg00 /dev/dsk/c3t6d0
mkboot /dev/rdsk/c3t6d0
mkboot ???a \???hpux ???lq\??? /dev/rdsk/c0t6d0
mkboot ???a \???hpux ???lq\??? /dev/rdsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol1 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol2 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol3 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol4 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol5 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol6 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol7 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol8 /dev/dsk/c3t6d0
lvextend ???m 1 /dev/vg00/lvol9 /dev/dsk/c3t6d0
lvlnboot ???b /dev/vg00/lvol1
lvlnboot ???s /dev/vg00/lvol2
lvlnboot ???r /dev/vg00/lvol3
lvlnboot -R
???

5. Revise que la sintaxis del script est?? bien:

# instl_adm ???T ???f config.recover


Good Look

Isaac Smith