Ignite-UX and MirrorDisk/UX

# mkdir /var/HPSP
# dd if=/dev/dsk/<boot disk>s3 bs=1024k | gzip > \
> /var/HPSP/<boot disk>.save.gz
# dd if=/dev/dsk/<second disk>s3 bs=1024k | gzip > \
> /var/HPSP/<second disk>.save.gz
Run make_tape_recovery or make_net_recovery ensuring that /var/HPSP (or where
you have placed the copies of the HPSP partitions) is included into the recovery archives. After
recovery you can then restore the diagnostics as in the following example:
# gzcat < /var/HPSP/<boot disk>.save.gz | \
> dd of=/dev/dsk/<boot disk>s3 bs=1024k
# gzcat < /var/HPSP/<second disk>.save.gz | \
> dd of=/dev/dsk/<second disk>s3 bs=1024k
Note:
If you include configuration into Ignite-UX configuration files to perform
these actions automatically after a recovery, you should ensure that this
recovery archive will not be used to clone a system on which these
offline diagnostics will not work.
After creating an alternate boot disk using LVM, HP recommends that you test that it can boot and
operates as expected.
How to Recover Mirrored Disk Systems with Ignite-UX using
make_tape_recovery
The make_tape_recovery command creates a recovery tape for a system with mirrored disks
but it will not preserve the mirror configurations. After booting from the system recovery tape, disk
mirrors are lost and must be reconfigured using LVM commands.
There are two methods to do this. First, you can wait until the system is recovered and then execute
the necessary LVM commands, or use SAM/SMH (note SAM/SMH cannot re-mirror a boot disk –
see the instructions given previously for how to reestablish mirroring on a boot device on HP 9000
and HP Integrity systems).
Second, it is possible to make some manual changes to an Ignite-UX configuration file referenced
by make_tape_recovery such that the LVM commands are executed as part of the recovery
process.
Important:
If you choose to pursue the second option a recovery tape created in
this way should NOT be used to clone systems unless they contain very
similar hardware.
8