Dynamic Root Disk A.3.10.* Release Notes (January 2012)

QXCR1001041894. Prior to the fix for QXCR1001041894, DRD sync incorrectly
recorded files with special characters in the DRD registry. This caused the
registry to be unreadable, making subsequent "drd sync" operations fail.
After the fix, files containing special characters are handled correctly.
DRD version A.3.6 and A.3.7 contain fixes for the following defects:
QXCR1000894322. ACLs that are set on LVM volume mount points in the root
group will now be copied to the clone providing the mount point has a journal
filesystem.
QXCR1000933863. Signals (SIGINT, SIGQUIT, SIGHUP and SIGTERM) to 'drd runcmd'
will no longer have extraneous fsdaemon and swagentd processes running.
QXCR1000985412. Prior to the fix for QXCR1000985412, customers who had
release B.11.xx.3.4 or prior installed on the inactive image and B.11.xx.3.4
or above on the booted system could get an error similar to the following
when running "drd runcmd": "One or more postcommands for xxx failed." The fix
to QXCR1000985412 resolves this problem.
QXCR1001037278. With this fix, execution of 'drd umount' no longer creates a
file called 'mapfile' in the current directory on LVM root systems.
QXCR1001023408: The help messages displayed drd runcmd -? have been changed
to show that “drd runcmd” takes a DRD-safe command as an argument, and to
display the list of currently-supported DRD-safe commands.
QXCR1000801373: This was a defect in VxVM that affected DRD. Before this
issue was addressed, the drd clone command failed on a VxVM-managed system
with a root group volume name ending in another root group volume name. For
example, the root volume group names varoptvol and optvol caused the drd
clone command to fail. The following HP-UX patches for VxVM, or appropriate
superseding patches, resolve this issue:
• VxVM 5.0 on HP-UX 11i v3 (11.31): PHCO_40294
• VxVM 5.0 on HP-UX 11i v2 (11.23): PHCO_38570
• VxVM 4.1 on HP-UX 11i v3 (11.31): PHCO_38654
• VxVM 4.1 on HP-UX 11i v2 (11.23): PHCO_38464
2.5 Version A.3.5 (March 2010)
DRD version A.3.5 contains the following new features:
• sync command to compare and synchronize the clone with the original OS disk. After
creating a DRD clone but prior to activating the clone, you can use DRD sync to compare
the original image to the clone, identifying and optionally applying any changes made to
the original image that need to be propagated to the clone. Examples would be changes
to password files, log files, etc.
DRD version A.3.5 contains fixes for the following defects:
QXCR1000950254: The drd clone command succeeds when a device file is missing
for a disk other than the clone target.
QXCR1000961233: Cloning a fully allocated LVM disk to an identical sized
target can fail due to space issues if the LVM parameters for extent size,
max physical vols, or max logical vols are set to non default values.
# /opt/drd/bin/drd clone -v -x overwrite=true -t /dev/dsk/c3t5d0