Ignite-UX and MirrorDisk/UX
• The primary disk has a hardware failure and the mirror also fails before the primary can be
replaced.
• You are about to update your system to a new operating system release or add new patches to
the system. Creating a recovery archive allows you to get back to a working system if the update
does not succeed.
During such a recovery, Ignite-UX will not automatically re-create the LVM mirrors. The mirrors need
to be created via LVM commands or SAM/SMH after the recovery is complete.
Note:
Later in this white paper we will be discussing how you can add
configuration into a recovery archive to automatically reestablish LVM
mirroring of the root volume group.
How to Deploy Mirrored Disk Systems with Ignite-UX
When you're specifying how your disks should be configured in the Ignite-UX user interface, any
disks that will eventually be mirrors should not be specified.
Once the cold install process has completed, you can set up your disk mirrors via the SAM/SMH
command or by using the LVM commands directly. Note that SAM/SMH cannot be used to mirror
the root disk.
It is important to understand the steps involved in mirroring the root volume group on HP 9000 and
HP Integrity servers in order to apply these concepts to the use of Ignite-UX with mirrored disks.
How to mirror the root disk on an HP 9000 system
1. Run the pvcreate command on the disk that you will be mirroring to, you must use the –B
option to make this disk bootable, it is a common mistake when mirroring the root volume group
to not use the –B option when running pvcreate on the alternate boot disk.
Note:
If your setup requires more than one disk to complete mirroring, the
second and any subsequent disks should not have pvcreate executed
on them with the –B option. You may need to use the –f option to force
pvcreate to operate on the disk if it has been used by LVM previously.
# pvcreate -B /dev/rdsk/<second disk>
2. Extend the disk into the root volume group, at this point you should also extend any other disks
required into the root volume group.
# vgextend /dev/vg00 /dev/dsk/<second disk>
3