Dynamic Root Disk Frequently Asked Questions (August 2010)

uname -a
Look at the contents of the log files under /var/opt/drd. It may be helpful to have the data for the entire session. In DRD log
files, sessions are delineated with ========. If there is too much data in the log, locate the first sign of trouble and the next
several error messages.)
Make available information from the swagent.log files stored in depots (for example, /var/spool/sw/swagent.log). The
swagent daemon creates these when it reads or writes from a depot containing information written by swagent. Depots at
other locations have a similarswagent.log.
If you are troubleshooting a problem with drd runcmd, you may also want to consult the contents of the logfiles on the inactive
system image located at:
/var/opt/drd/mnts/sysimage_001/var/adm/sw/sw*.log
or
/var/opt/drd/mnts/sysimage_000/var/adm/sw/sw*.log
top
3-3. Q: I can't remember which disk was used as the target of my clone operation. How can I identify it?
A: The disk that was used for the clone is displayed by the drd status command.
drd status
The Clone Disk field specifies the target disk used to clone the original image.
top
3-4. Q: I issued a drd activate command but changed my mind and do not want to boot the clone. How can I undo
the drd activate command?
A: If you run drd activate and then decide not to boot the inactive image on the next reboot, use the drd deactivate command to set
the primary boot disk to the currently booted disk.
For further information on the drd deactivate command, see the drd-deactivate(1M) manpage.
top
3-5. Q: Can I change file system sizes when I create a clone?
A: This release of DRD does not provide a mechanism for resizing file systems during a drd clone operation. However, after the clone is
created, you can manually change file system sizes on the inactive system without needing an immediate reboot. The white paper,
Dynamic Root Disk: Quick Start and Best Practices white paper at http://www.hp.com/go/drd-docs
, describes resizing file systems other
than /stand and resizing the boot (/stand) file system on an inactive system image.
top
3-6. Q: How will fbackup|frecover handle “busy” files?
A: DRD does utilize fbackup and frecover, however, we have not encountered a problem with busy files. While frecover can fail to
overwrite busy files, this is not a problem in DRD because it is cloning a fresh volume group. fbackup can fail if files are changing
during the fbackup operation, but this is more common with spool files and log files. If you are concerned, use the drd runcmd
swverify \* command to check the integrity of the clone after it is created.
top
3-7. Q: What happens with the configuration scripts if I install patch A and later install patch B, which then
supersedes patch A?
A: If you install both Patch A and Patch B before booting, only Patch B is configured. This should not present a problem unless you later
remove patch B with swremove, thereby exposing Patch A in an unconfigured state. You would then need to swconfig or reinstall
Patch A.
top
3-8. Q: If I use the IgniteUX server; is it aware of the DRD clone?
A: The Ignite server will only be aware of the clone if it is mounted during a make_*_recovery operation. Most customers will probably
prefer to keep the clone unmounted so that only the active system image is archived by Ignite. In addition, the customer will probably
want to keep a record of the clone hardware path to enable Hot Recovery using DRD.