Dynamic Root Disk and MirrorDisk/UX

• A copy of Dynamic Root Disk
DRD is available at no charge by searching for “DRD” on HP’s software depot:
http://software.hp.com/.
• Two disks that are currently in use as the boot disk and the boot mirror
(If the boot mirror has not already been created, the procedure described below in
How
to Mirror vg00 – HP 9000 System
can be used.)
• Two disks available that can be used for the DRD clone and the clone mirror
Each disk must be large enough to contain all the logical volumes that are currently in
vg00. The logical volumes in the clone volume group, drd00, will be the same sizes as
those in vg00. In the case of an Integrity system, the disks must also be large enough to
hold Extensible Firmware Interface (EFI) and HP Service Partition (HPSP) partitions of the
same size as the current root disk.
The disks must be “standalone” disks, as opposed to disk partitions, but they may actually
be areas in a Storage Area Network that have been presented to the HP-UX operating
system as a single disk.
When the necessary resources have been identified, execute the following command:
# /opt/drd/bin/drd clone –t target_disk –x mirror_disk=mirror_disk
Where target_disk is the block device special file of the target disk and mirror_disk is the
block device special file of the mirror.
The DRD clone disk is then mirrored from its creation, through its modification by drd runcmd, and
its activation as a boot disk by drd activate. For customers with sufficient internal disks or the
ability to use SAN allocations, this is the ideal scenario.
Three Disk Scenario – Mirroring the Clone When it is
Booted
In this scenario, the customer has a mirrored boot disk and wants to use DRD for either offline
patching or hot recovery. (For more information on using DRD for offline patching and hot recovery,
see the Using the Dynamic Root Disk Toolset white paper, which is located at:
http://docs.hp.com/en/oshpux11iv2.html#Dynamic%20Root%20Disk.) However, due to the
limitation of three available disks, or policies preventing use of SAN storage for boot disks, the clone
cannot be mirrored when it is created. In this case, the clone will be mirrored when it is booted. The
steps below describe a procedure that can be used after booting the clone.
In this case, the system administrator needs to check for the following resources:
• A licensed copy of MirrorDisk/UX