Ignite-UX and MirrorDisk/UX

To integrate the configuration of disk mirrors into the recovery process we will be using a feature of
the make_tape_recovery command. The make_tape_recovery command automatically
includes the /var/opt/ignite/recovery/config.local file, if it exists, into any
make_tape_recovery configuration.
Caution:
If you perform a preview when using these instructions (using the –p
option) there is a defect in
make_tape_recovery that prevents
the
config.local file from being included into the configuration
when you resume the
make_tape_recovery command (using
the
–r option). If you plan on performing a preview and resume
operation you should upgrade to Ignite-UX version C.6.2 or later where
this defect has been addressed.
After creating or modifying /var/opt/ignite/recovery/config.local, it's a good
practice to run "instl_adm -T -f /var/opt/ignite/recovery/config.local", to
ensure that the syntax is correct. If the syntax is incorrect this will prevent the creation of the
recovery tape.
The section “
An Example config.local File” presents example config.local files for both HP Integrity
systems and HP 9000 systems.
How to Recover Mirrored Disk Systems with Ignite-UX via
make_net_recovery
The make_net_recovery command will create a network recovery archive for a system with
mirrored disks, but it will not preserve the mirror configurations.
After recovering from the network recovery archive, disk mirrors are lost and must be reconfigured
using LVM commands. There are two methods to reconfigure your mirrored disks:
• You can wait until the system is recovered, and then execute the necessary LVM commands or
use SAM/SMH. If you choose to use SAM/SMH, be aware that it cannot re-mirror a boot disk.
You must reestablish mirroring on a boot device as described in “
How to mirror the root disk on
an HP 9000 system
,” or “How to mirror the root disk on an HP Integrity Server.”
• You can create an Ignite-UX configuration file such that the LVM commands are executed as part
of the recovery process.
In either case, the LVM commands are the same.
The following sections will show example configurations that can be used on HP 9000 and HP
Integrity systems. To use these examples you must create a new Ignite-UX configuration file named:
/var/opt/ignite/clients/0x{LLA}/recovery/config.local
This config.local file is automatically included into your recovery configuration for this client
each time you run the make_net_recovery command.
Note:
The make_net_recovery command is automatically executed when
you use the Ignite-UX GUI for network recovery.
9