Dynamic Root Disk: Quick Start & Best Practices

24
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk6_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk6_p2
Root: lvol3 on: /dev/disk/disk6_p2
Swap: lvol2 on: /dev/disk/disk6_p2
Dump: lvol2 on: /dev/disk/disk6_p2, 0
Boot Definitions for Volume Group /dev/drd00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk7_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk7_p2
Root: lvol3 on: /dev/disk/disk7_p2
Swap: lvol2 on: /dev/disk/disk7_p2
Dump: lvol2 on: /dev/disk/disk7_p2, 0
26. Set the clone to be the primary boot disk and boot to it:
# /opt/drd/bin/drd activate -x autoreboot=true
HP recommends that you create a shutdown script that runs drd sync so that files changed on
the original image after the clone was created will be propagated to the clone. See the “DRD
sync” section below for more details.
Viewing Log Files
When you use drd runcmd to run commands that modify the inactive system image, logging occurs
in several places that correspond to the locations at which the processes were executed. Because DRD
runs on the booted system, a DRD log is created on the active image. Any sw* command that you run
on an inactive image appends to the sw* logs on the inactive image.
For example, the command:
# /opt/drd/bin/drd runcmd swinstall -s depotserver:/patch_depot PHKL_9999
results in new messages in each of the following log files:
• In /var/opt/drd/drd.log (the original log file, located on the booted system)
• In the copy of /var/adm/sw/swinstall.log on the clone
• In the copy of /var/adm/sw/swagent.log on the clone
Because drd.log is located in the /var file system, it is copied during the clone operation to the
/var file system on the clone. However, because the clone’s file systems must be unmounted before
the final ending banner message of the operation is written to the log, the record of the clone
operation in the clone’s log is truncated at the message indicating that file systems are being copied.
The next message in the clone’s log is issued by the next DRD command run on the clone itself—after
it is booted. The log on the booted system will be complete, ending with the final banner message.
sw* logs for a given image produce a complete picture of all software operations on that image. If
the image was created by a clone, then the initial copies of the logs were copied by the clone
operation. New records might have been appended to the logs by subsequent drd runcmd sw*
operations or by sw* commands run after the image was booted.
Note the following important factors about log files created from a drd runcmd operation: