Dynamic Root Disk Frequently Asked Questions (766143-001, March 2014)

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?