Dynamic Root Disk A.3.13 * Release Notes (766141-001, March 2014)

DRD updates from multiple-DVD media
Issue
DRD updates directly from media require the September 2010 OE (or later) versions of DRD, SWM
and SW-DIST products
Workaround
In order to use a media depot to do a DRD update, you will need to first install September 2010
or later versions of DRD, SWM, and SW-DIST products from the media. This must be done before
the clone is created, so the new DRD, SWM, and SW-DIST are on the active system and on the
clone.
To install these products execute a command like to following. This assumes that the first DVD of
the September 2010 or later release is mounted to /SD_CDROM.
swinstall -x autoselect_dependencies=false -s /SD_CDROM \ DRD SWM SW-DIST
PHCO_36525
Now you can create the clone, then perform an OE update from the media on the clone.
Rehosting issues
Issue
DRD status reports error on rehosted boot disk
After rehosting a clone disk using "drd rehost" and booting that disk, running DRD commands may
result in the following error. The new rehosted machine may not recognize the disks that were on
the previous system and which are now specified in the /var/opt/drd/registry/
registry.xml file.
ERROR: Cannot display clone information: either the registry
data is corrupted or there is no clone on the system.
- Could not display the clone information.
- The disk "/dev/disk/disk12" cannot be associated with
a disk with an EFI partition.
- The command "/usr/sbin/diskinfo/dev/rdisk/disk12_p1"
fails with the return code 1. The error message from
the command is "diskinfo: can't open /dev/rdisk/disk12_p1:
No such device or address
Workaround
In order to clear out the outdated information on your new system, simply remove the registry file,
which is used by DRD to hold pertinent clone and disk information. Once a system is rehosted,
this information no longer applies. To remove the registry file:
# rm /var/opt/drd/registry/registry.xml
Status: plan to fix this in a future release.
Limitations due to OS interactions
Issue
LVM 2.x awareness not available on 11i v3 releases prior to September 2008
Prior to release B.11.31.A.3.4 of DRD, a disk specified in a DRD command as a target or mirror
was not checked for LVM 2.x usage or formatting. Release B.11.31.A.3.4 of DRD recognizes
LVM 2.x disk formatting on all releases of LVM 2.x. However, it only determines disk usage of
LVM 2.x for the September 2008 release and later.
16 Known problems and workarounds