Dynamic Root Disk A.3.12.* Release Notes

2. Supported DRD Releases
The first release of DRD, version A.1.0 was posted to the Web in January 2007. For each
release in the last two years, this chapter lists the new features and defect fixes. Note that all
releases are cumulative, and that all releases of DRD are compatible with previous versions of
DRD, unless otherwise noted.
Versions of DRD are supported for at least 2 years. Versions not listed in this section of the latest
Release Notes are no longer supported. This means that while it is recommended to use the latest
version of DRD possible, since there are more quality improvements in each release, it is even
more strongly recommended to use a version of DRD that is listed as supported in the most recent
version of this document.
2.1 Version A.3.12 (March 2013)
DRD version A.3.12 contains the following new features:
• DRD now supports SoftReboot feature
DRD version A.3.12 contains fixes for the following defects:
QXCR1001164981: Enhancement to “drd activate” to allow users to boot the
clone disk with SoftReboot feature. This option is supported with SoftReboot
new core functionality product installed on Itanium-based systems. It reduces
the system downtime as compared to the normal reboot.
QXCR1001242324: DRD will not core dump anymore if there is a hardware path
with no DSFs associated with it. It issues a warning and lets the clone
succeed.
2.2 Version A.3.11 (September 2012)
DRD version A.3.11 contains only defect fixes and quality improvements. DRD version A.3.11
contains fixes for the following defects:
QXCR1001186489: Prior to this fix for this CR, “drd activate” command was
setting a standby hardware path as the primary bootpath, resulting in a
boot failure. With this fix “drd activate” command will not select
standby hardware path.
2.3 Version A.3.10 (March 2012)
DRD version A.3.10 contains only defect fixes and quality improvements. DRD version A.3.10
contains fixes for the following defects:
QXCR1001080540. Prior to this fix a “drd clone” operation might
hang when cloning a system that contained LVM snapshot volumes.
With this fix the “drd clone” operation will issue an error when
attempting to clone a system with LVM snapshot volumes.