DRD (Dynamic Root Disk) Release Notes (Release March 2014, 766141-001a) (Edition 2, April 2015)

DRD (Dynamic Root Disk) Release Notes
Version: A.3.13
HP-UX 11i v2 and HP-UX 11i v3
HP Part Number: 766141-001a

Published: March 2014
Edition: 2 (March 2015)
© Copyright 2007, 2015 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial
Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products
and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as
constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Links to third-party websites
take you outside the HP website. HP has no control over and is not responsible for information outside HP.com.
Intel® Itanium® Logo, Intel, Intel Inside and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the U.S. and
other countries.
UNIX® is a registered trademark of The Open Group.
Revision History
DRD (Dynamic Root Disk)

Document Part Number Version Supported Operating Systems Publication Date
766141-001a A.3.13 HP-UX 11i v2 March 2015

nl
HP-UX 11i v3 (Replaced document)

nl
(Current version of the

document)
766141-001 A.3.13
nl
HP-UX 11i v2 March 2014
nl
(Original edition) HP-UX 11i v3 (Document retired)

Contents
HP secure development lifecycle......................................................................4
1 Overview..................................................................................................5
Product features........................................................................................................................5
2 Supported DRD (Dynamic Root Disk) releases.................................................7
Version A.3.13 (March 2014)......................................................................................................7
Version A.3.12 (March 2013)......................................................................................................7
Version A.3.11 (September 2012)................................................................................................8
Version A.3.10 (March 2012)......................................................................................................8
Version A.3.9 (September 2011).................................................................................................9
Version A.3.8 (March 2011).....................................................................................................11
Version A.3.6 and A.3.7 (September 2010)...............................................................................12
Version A.3.5 (March 2010).....................................................................................................14
3 System and software requirements..............................................................17
Required patches and software.................................................................................................17
Clone features........................................................................................................................17
Safe command list..................................................................................................................18
Installation and removal of patches and products........................................................................18
Use of SD TUI/GUI.................................................................................................................18
Installation requirements..........................................................................................................18
4 Known problems, issues, limitations, and workarounds..................................19
Out of memory issues..............................................................................................................19
DRD (Dynamic Root Disk) OE update issues...............................................................................19
DRD (Dynamic Root Disk) updates from multiple-DVD media.........................................................20
Rehosting issues.....................................................................................................................20
Limitations due to OS interactions.............................................................................................20
Cloning problems...................................................................................................................22
Whole disk layout limitation.....................................................................................................23
Cloning with VxVM volumes having special characters................................................................24
Cloning support when Enclosure Based Naming (EBN) scheme is enabled with VxFS/VxVM 5.1 SP1
software................................................................................................................................24
5 Documentation feedback...........................................................................25
More on DRD (Dynamic Root Disk) documentation......................................................................25
Support policies for HP-UX.......................................................................................................25
Contents 3
HP secure development lifecycle
Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides
the ability to authenticate HP-UX software. Software delivered through this release has been digitally
signed using HP's private key. You can now verify the authenticity of the software before installing
the products, delivered through this release.
To verify the software signatures in signed depot, the following products must be installed on your
system:
• B.11.31.1303 or later version of SD (Software Distributor).
• A.01.02.00 or later version of HP-UX Whitelisting (WhiteListInf).
To verify the signatures, run: /usr/sbin/swsign -v -s <depot_path>.
For more information, see Software Distributor documentation at http://www.hp.com/go/sd-docs.
NOTE: Ignite-UX software delivered with HP-UX 11i v3 March 2014 release or later supports
verification of the software signatures in signed depot or media, during cold installation. For more
information, see Ignite-UX documentation at http://www.hp.com/go/ignite-ux-docs.
4
1 Overview
DRD, also known as Dynamic Root Disk, is an HP-UX system administration toolset used to clone
an HP-UX system image to an inactive disk for software update, maintenance, recovery, and
rehosting. DRD (Dynamic Root Disk) is available for download from Software Depot. System
administrators use DRD (Dynamic Root Disk) to manage system images on HP PA-RISC and Itanium®
-based systems. DRD (Dynamic Root Disk) complements other parts of your total HP solution by
reducing system downtime while installing and updating patches and other software.
DRD (Dynamic Root Disk) is supported on HP-UX 11i v2 September 2004 and all subsequent
releases of HP-UX 11i v2. It is also supported on all HP-UX 11i v3 releases. DRD (Dynamic Root
Disk) supports LVM or VxVM managed root volumes.
Product features
The following features are supported on the most recent release of DRD (Dynamic Root Disk).
Anything labeled as “new” was added as of the most recent release. New functionality for previous
releases can be seen in the next chapter that details each release.
The most recent release of DRD (Dynamic Root Disk) is supported on HP-UX 11i v2 and HP-UX 11i
v3 with an LVM or a VxVM volume manager. It provides the following functionality:
• Hot maintenance capability. The DRD (Dynamic Root Disk) tools can be used to create a clone
of the running system, apply patches to the clone, and boot the clone as the running system.
On 11i v3, products as well as patches can be installed and managed.
• Hot recovery capability. The DRD (Dynamic Root Disk) tools can be used to create a clone
and boot it if the running system fails.
• SD command support. The DRD (Dynamic Root Disk) tools provide a mechanism for running
SD commands such as swinstall, swremove, swverify, swmodify, swlist, and
swjob on the clone.
• Clone accessibility. The clone can be mounted on the running system so that its files can be
viewed or modified.
• Mirror compatibility. The DRD (Dynamic Root Disk) operation will not affect any mirror already
created on the running system. DRD (Dynamic Root Disk) can be used to create a mirror of
the clone during the cloning operation.
• Command line interface. The DRD (Dynamic Root Disk) tools are run from the command line.
• The drd deactivate command was added. This restores primary boot path to the current
active/running system image.
• A rich set of commands for activating and deactivating the inactive system image. This
determines what volume will be used as the root on the next system boot. This includes options
to set the alternate boot disk and the High Availability alternate boot disk.
• Support for volumes created under root volume group/root disk group with LVM volume group
versions 1.0 and 2.2, 4.1 VxVM, 5.0 VxVM, 5.0.1 VxVM, and 5.1SP1 VxVM. These root
volumes can have any name (not just vg00).
• The drd status command. This allows the user to easily view clone information on the
system. The command specifies the following: which disk the clone resides on; when the clone
was created; the location of the clone's mirror (if one exists); and the original disk that was
copied to create the clone. It also specifies the state of the boot partition on the clone, mirror,
and original disks, as well as which disk is booted and which is activated (the disk that will
be booted from on the next reboot).
• Rehost the clone to another system. This feature allows users to create a clone, which can
optionally be modified, then boot that clone on another system. Rehosting can be used to
Product features 5
quickly and efficiently provision new systems, and to simplify the setup of test systems. Rehosting
is supported on HP-UX 11i v3 and v2 Integrity systems with LVM roots, for rehosting from a
blade to another blade (v3 only) or a VM to another VM (v2 and v3).
• This version of DRD (Dynamic Root Disk) introduces the ability to perform an OE update from
an older version of 11i v3 to HP-UX 11i v3 update 4 or later. You are able now to update
your OE level on the clone while your original system remains up and running. Once the
update on the clone is done, you can boot the clone and keep your original image as backup.
• Improved performance and accuracy of the DRD (Dynamic Root Disk) algorithm which
determines if a disk to be used as a clone is in already in use or not.
• 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 are; changes to password files, log
files, and so on. Enhancements to drd sync to:
◦ Allow users to exclude files and directories, in addition to those described in drd
sync(1M) , from the sync operation.
◦ Support frequently changing files such as logs of automated processes.
◦ Ability to sync file system and volume group information.

• Support in drd runcmd for kcmodule, kconfig, and mk_kernel. This enhancement
introduces limited support for rehosting to a different model system.
• drd clone operation can copies autofile, so that customizations are retained on the clone.
6 Overview
2 Supported DRD (Dynamic Root Disk) releases
The first release of DRD (Dynamic Root Disk), version A.1.0 was posted on 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 (Dynamic Root Disk) are
compatible with previous versions of DRD (Dynamic Root Disk), unless otherwise noted.
Versions of DRD (Dynamic Root Disk) are supported for at least two 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 (Dynamic Root Disk) possible, since there are more
quality improvements in each release, it is even more strongly recommended to use a version of
DRD (Dynamic Root Disk) that is listed as supported in the most recent version of this document.
Version A.3.13 (March 2014)

DRD (Dynamic Root Disk) version A.3.13 contains the following new feature:
Support for root disk group configured with 5.1SP1 VxVM which has DGV (Disk Group Version)
160
DRD (Dynamic Root Disk) is now supports root disk group configured with 5.1SP1 VxVM having
DGV 160. Versions of DRD (Dynamic Root Disk) prior to A.3.13 only support 5.1SP1 VXVM having
DGV 140. Starting with March 2014 release of HP-UX 11i v3, a VxVM root disk group with
5.1SP1 VxVM is configured with DGV 160 by default during cold installation using Ignite-UX.
To check the DGV of the root disk group, run:
/usr/sbin/vxdg list rootdg | grep version
DRD (Dynamic Root Disk) (Dynamic Root Disk) version A.3.13 contains fixes for the following
defects:
Defect ID Description
QXCR1001276997 Title: drd clone fails due to crashing drdconfigure

Severity: Serious
Problem and details: With this fix, drd clone will not core dump, if a CD/DVD
media is loaded in the optical disc drive, or if an iso image is loaded in a virtual
CD/DVD drive in an Integrity VM. This defect is present only in the A.3.12 version of
DRD (Dynamic Root Disk).
Resolution: This issue is fixed in this release.
QXCR1001212797 Title: drd can fail with out of memory errors if too many files in vg00
Severity: Medium
Problem and details: DRD (Dynamic Root Disk) will not fail with "out of memory error",
if too many files are present in the vg00. With this fix, DRD (Dynamic Root Disk)
supports approximately 2.5 million files in vg00. The -x exclude_list option must
be used to prevent syncing of directories that contain large number of files
NOTE: For more information on out of memory issues, see “Out of memory issues”
(page 19).

DRD (Dynamic Root Disk) version A.3.12 contains a new feature, that is, DRD (Dynamic Root Disk)
now supports SoftReboot feature.
Version A.3.13 (March 2014) 7

DRD (Dynamic Root Disk) version A.3.12 contains fixes for the following defects:
QXCR1001164981 Title: Changes to drd clone for fast reboot support

Severity: Medium
Problem and details: 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 Title: drdconfigure gets SIGSEGV and dump core file

Severity: Serious
Problem and details: DRD (Dynamic Root Disk) 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.
Version A.3.11 (September 2012)

DRD (Dynamic Root Disk) version A.3.11 contains only defect fixes and quality improvements.
DRD (Dynamic Root Disk) version A.3.11 contains fix for the following defect:
QXCR1001186489 Title: drd activate selects incorrect (standby) HW path for setboot command
Severity: Serious
Problem and details: 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.
nl

DRD (Dynamic Root Disk) version A.3.10 contains only defect fixes and quality improvements.
QXCR1001080540 Title: DRD (Dynamic Root Disk) clone appears to hang when root group contains
snapshot volumes
Severity: Serious
Problem and details: 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.
QXCR1001120919 Title: “/opt/drd/lbin/drd_scan_hw_host” fails with the return code 1

Severity: Serious
Problem and details: Prior to this fix, drd_scan_hw_host was going into interactive
mode, if the source type was unable to determine. With this fix, we no longer consider
whether the source type can be determined and, thus, never go interactive.

QXCR1001129462 Title: drd clone does not copy disk*_p1:/efi/hpux/vparconfig.efi when cloning
vPars
Severity: Medium
Problem and details: Prior to this fix, DRD (Dynamic Root Disk) was not copying the
EFI/HPUX/vparconfig.efi file during a clone, when the file was present in the EFI/HPUX
directory. With this fix the EFI/HPUX/vparconfig.efi file will be copied during
a clone, when the file is present in the EFI/HPUX directory.
QXCR1001133378 Title: drd_scan_hw_host can attempt to allocate too much memory

Severity: Serious
Problem and details: Prior to this fix, it was possible for a customer configuration to
cause drd_scan_hw_host to allocate large chunks of memory. With this fix, those
configurations can no longer cause this behavior in drd_scan_hw_host.
QXCR1001159424 Title: DRD command fails with environment variable TMPDIR

Severity: Medium
Problem and details: Prior to this fix, setting the environment variable "TMPDIR" causes
the drd clone command fail. With this fix, DRD will ignore "TMPDIR".
QXCR1001167367 Title: drd clone fails with SIGSEGV

Severity: Medium
Problem and details: Prior to this fix, drd clone will core dump when the block DSF
of the booted disk was not present on the system. With this fix, the core dump will no
longer occurs under that condition.
QXCR1001168773 Title: drd clone fails at frecover if /etc/lvmconf is moved & symbolic linked
Severity: Medium
Problem and details: Prior to this fix, drd clone will fail during the copy of file
systems, when /etc/lvmconf was moved and a symbolic link was put in its place.
With this fix, we no longer fail when /etc/lvmconf is moved and a symbolic link
was put in its place.
Version A.3.9 (September 2011)

DRD (Dynamic Root Disk) version A.3.9 contains a new feature, that is, drd clone operation
can now copy autofile, so that customizations are retained on the clone.
QXCR1000988687 Title: EFI content on drd clone is generic rather than a copy of booted EFI
Severity: Serious
Problem and details: Prior to this fix, the EFI AUTO file on the clone was generic rather
than a copy of that which was on the original system. With the fix, the EFI AUTO file
is copied from the original system to the clone and mirror, if applicable.
QXCR1001078844 Title: Some DRD error messages refer to files erased before job completes
Severity: Serious
Version A.3.9 (September 2011) 9

Problem and details: Prior to the fix, DRD (Dynamic Root Disk) was deleting the
temporary configuration files in /var/opt/drd/tmp when the DRD session was
completed. With the fix, in the event of an error, DRD will copy the contents of /var/
opt/drd/tmp to /var/opt/drd/save for use to diagnose the error.
QXCR1001103256 Title: Discrepancy between otherRootDSFsCount and otherRootDSFs in DRD

registry
Severity: Serious
Problem and details: Prior to the fix for this CR, the DRD registry can be missing mirror
dsfs in cases where there are more than 1 mirror dsf for the boot or clone disk. This
inconsistency does not cause any functionality issues.
QXCR1001104751 Title: Delivered script drd_unregister_mirror removes needed registry entries

Severity: Critical
Problem and details: Prior to the fix for this CR, execution of the script /opt/drd/
bin/drd_unregister_mirror removed registry entries which were needed by
“drd mount” on LVM2 systems, and “drd sync”. The entries which were deleted
pertain to volMgrVers, syncDate, and creationDate. On LVM 2 systems, “drd
mount” was producing the following error:
* Mounting Inactive System Image ERROR:

Mounting the file system fails. - Mounting the inactive
system
image fails. - The command "/usr/bin/sh -c
/var/opt/drd/tmp/drdq31CuWfbL/.drdvgimportcmd " fails with
the
return code 1. The error message from the command is
"vgimport:
Error: The major number for the group file "/dev/drd00/group"
corresponds to volume group version 1.0

With the fix, drd_unregister_mirror executes successfully.
QXCR1001105660 Title: runcmd does not forward X11

Severity: Serious
Problem and details: Prior to the fix for this CR, when using ssh -x to a system,
execution of drd runcmd for a GUI application was resulting in an X11 forwarding
failure as follows:
* Executing command: "/usr/sbin/swinstall"
NOTE: The interactive UI was invoked, since no software was
specified. Xlib: connection to "localhost:13.0" refused by
server
Xlib: PuTTY X11 proxy: MIT-MAGIC-COOKIE-1 data did not match.
With this fix, the GUI now runs correctly.
QXCR1001106819 Title: DRD (Dynamic Root Disk) activate and deactivate do not work correctly on cell
based systems (vPars)
Severity: Critical
Problem and details: Prior to this fix, drd activate and drd deactivate was
attempting to set the High Availability bootpath on vPar systems that do not support
the High Availability bootpath. With this fix, drd activate and drd deactivate
do not attempt to set the High Availability bootpath on vPar systems.
QXCR1001113284 Title: drd sync fails due to file with invalid character in the file name

Severity: Serious
Problem and details: Prior to this fix, drd sync was unable to tolerate the file names
that contained unprintable control characters. With this fix, drd sync now handles
unprintable control characters as well as characters in the extended ASCII code set

DRD (Dynamic Root Disk) version A.3.8 contains the following new features:
• Ability to sync file system and volume group information.
• New FAQ entry on using DRD (Dynamic Root Disk) in a vPars environment.
QXCR1000968514 Title: Need to remove registry during rehost

Severity: Serious
Problem and details: Prior to this fix, if a clone disk or original boot disk was removed
from a system, DRD (Dynamic Root Disk) commands was failing with confusing
messages. This change clarifies the messages and makes them consistent for roots
managed by either LVM or VxVM.
QXCR1001024172 Title: drd clone must reject NPIV target

Severity: Serious
Problem and details: Prior to this fix, drd was creating a clone or mirror on an NPIV
disk. After the fix, drd rejects the target with an appropriate message that NPIV disks
are not bootable.
QXCR1001026491 Title: pvmove of root disk causes many DRD (Dynamic Root Disk) problems
Severity: Serious
Problem and details: Prior to this fix, if boot disks were moved by using pvmove or
by creating and breaking mirrors without a reboot, drd clone was failing with the
following errors:
ERROR: Making the file system bootable on clone fails.

- Mounting the file system fails.
- Mounting the inactive system image fails.
- The "mount" command fails with the return code "1". The error
message from the command is
"mount: /dev/drd00/lvol3 is already mounted on
/var/opt/drd/mnts/sysimage_001"
- Use the "bdf(1M)" and "umount(1M)" commands to remove any
conflicting mounts.
* Making New System Image Bootable failed with 1 error.
* Unmounting New System Image Clone
* System image: "sysimage_000" on disk "/dev/disk/disk15"
ERROR: Unmounting the file system fails.
- Unmounting the clone image fails.
- The volume "/dev/drd00/lvol3" is part of the inactive system image,
but is mounted at
"/var/opt/drd/mnts/sysimage_001/" rather than under the directory
"/var/opt/drd/mnts/sysimage_000".
Unmount the volume with umount(1M), then re-run drd.
QXCR1001038220 Title: drd runcmd update-ux -i fails with Terminal user interface failed message
Severity: Serious

Problem and details: The use of the -i (interactive) option with drd runcmd
update-ux was never meant to be supported. We now check for use of this option and
issue an error message. The DRD (Dynamic Root Disk) Manpage reflects this change.
QXCR1001074042 Title: umount at end of drd clone attempt fails if PHCO_40522 installed
Severity: Medium
Problem and details: Prior to this fix, when PHCO_40522 was installed on an HP-UX
11i v2 (11.23) system, the clone operation was failing with an unmount error. Now
clone works as expected.
QXCR1001092279 Title: lvmpvg is not copied correctly during clone operation

Severity: Critical
Problem and details: Prior to this fix, using the path name of the root volume group
for the vg_name in the lvmpvg file was causing the lvmpvg file to be copied
incorrectly during a clone operation. Now it is copied correctly.
Version A.3.6 and A.3.7 (September 2010)

Version A.3.6 is the September 2010 media release and A.3.7 is the August 2010 web release.
DRD (Dynamic Root Disk) version A.3.7 contains a new feature — enhancement to drd sync to
allow users to exclude files and directories, in addition to those described in drd-sync (1M),
from the sync operation.
DRD (Dynamic Root Disk) version A.3.6 and A.3.7 contain the following new features:
• Support for LVM 2.2 root volumes. A clone can be made of an LVM 2.2 root volume, then all
the other drd commands, such as runcmd, activate, sync, and mount can be run on that clone.
• Enhancements to drd sync to support frequently changing files, such as logs of automated
processes.
• Support in drd runcmd for kcmodule, kconfig, and mk_kernel. This enhancement
introduces limited support for rehosting to a different model system.
QXCR1001056449 Title: drd sync is not working for directories and files underneath
Severity: Serious
Problem and details: This fix resolves the issue where drd sync does not copy new
files and directories to the clone even though they are listed in
/var/opt/drd/sync/files_to_be_copied_by_drd_sync.
QXCR1001054745 Title: SYSINFO_HOSTNAME does not support hyphen character

Severity: Medium
Problem and details: The issue where drd rehost will not allow SYSINFO_HOSTNAME
to contain the "-" character is resolved. Symptoms of the issue appear as follows:
======= 06/29/10 16:26:50 MESZZ BEGIN Rehost System Image

(user=root)
(jobid=st-shpu8)
* Checking System Restrictions
* Validating Target to Be Rehosted
* Validating New System Personality
* The messages from validation of the system info file "sethost_shpu8"

are given below.
* To see additional messages, run with higher verbosity.
* WARNING: The invalid value SYSINFO_HOSTNAME=st-shpu8 is ignored.
ERROR: A non-empty value must be specified for SYSINFO_HOSTNAME.
* End of messages from validation of the system info file

QXCR1001051734 Title: DRD (Dynamic Root Disk) needs to differentatie WARNINGS from ERRORs issued
by list_expander
Severity: Critical
Problem and details: Prior to the fix for QXCR1001051734, drd sync treated all
non-zero return codes from list_expander (the utility that creates the initial list of
files to be synchronized) as warnings. In some cases, this resulted in an empty list of
files to be synchronized, but just a warning return code from "drd sync." After this
fix, the return code from list_expander is always respected, and an error return
code will cause "drd sync" to fail.
QXCR1001050440 Title: non-empty /etc/lvmpvg file will cause drd clone to abort
Severity: Serious
Problem and details: Prior to the fix for QXCR1001050440, the existence of
/etc/lvmpvg caused drd clone to fail. After this fix, drd clone succeeds.
QXCR1001041894 Title: files or directories with " char will cause drd sync to fail
Severity: Serious
Problem and details: 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 this fix, files
containing special characters are handled correctly.
DRD version A.3.6 and A.3.7 contain fixes for the following defects:
QXCR1000894322 Title: File system ACLs are not preserved on clone mount points
Severity: Serious
Problem and details: 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 file system.
QXCR1000933863 Title: ^C during DRD (Dynamic Root Disk) causes the daemons and mounts to get left
behind on the active sys
Severity: Serious
Problem and details: Signals (SIGINT, SIGQUIT, SIGHUP, and SIGTERM) to drd
runcmd will no longer have extraneous fsdaemon and swagentd processes running.
QXCR1000985412 Title: Failure to upd /opt/drd/wrappers/common_utils on older clone causes runcmd

err
Severity: Serious
Problem and details: 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, were getting an error similar to the following when running "drd
runcmd": "One or more postcommands for xxx failed."
The fix to QXCR1000985412 resolves this problem.
Version A.3.6 and A.3.7 (September 2010) 13

QXCR1001037278 Title: RUT_1009 drd unmount creates /mapfile on booted disk
Severity: Critical
Problem and details: With this fix, execution of 'drd umount' no longer creates a file
called 'mapfile' in the current directory on LVM root systems.
QXCR1001023408 Title: IC348: incorrect drd runcmd usage

Severity: Medium
Problem and details: The help messages displayed drd runcmd -? are 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 Title: drd clone of VxVM root fails if a root volume ends with name of another
volume
Severity: Critical
Problem and details: 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

DRD (Dynamic Root Disk) version A.3.5 contains a new feature, that is, The sync command, which
is used 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 are; changes to password files, log files, and so
on.
QXCR1000950254 Title: Disks missing device files trigger stack trace in drd clone
Severity: Serious
Problem and details: The drd clone command succeeds when a device file is missing
for a disk other than the clone target.
QXCR1000961233 Title: Cloning fully allocated LVM systems can fail if group parameters are non-default
Severity: Serious
Problem and details: 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
======= 07/02/08 13:16:04 EDT BEGIN Clone System Image (user=root)
(jobid=lccns166)

* Reading Current System Information
* Selecting System Image To Clone
* Selecting Target Disk
* The disk "/dev/dsk/c3t5d0" contains data which will be
overwritten.
* Selecting Volume Manager For New System Image
* Analyzing For System Image Cloning
ERROR: Analysis of file system creation fails.
- Analysis of target fails.
- The analysis step for creation of an inactive system image
failed.
- The following messages, including errors, were obtained
during
analysis:
E:The total volume sizes in disk group: "drdroot" exceed
the
available capacity by 32Mb.
E:The disk capacity available is not sufficient to create
the volume
"/" with the size specified (disk space is short by 32Mb).
Reduce
the size of this volume (or other volumes that share the
same disk
group), or use additional/larger disks.
.
* Analyzing For System Image Cloning failed with 1 error.
======= 07/02/08 13:16:16 EDT END Clone System Image failed
with 1 error.
(user=root) (jobid=lccns166)
QXCR1000964506 Title: LVM panic booting 11.23 disk that was drd mounted on 11.31 system
Severity: Critical
Problem and details: When an 11.23 system is cloned and then updated to 11.31.
The clone can now be mounted from the updated 11.31 system and remain bootable.
QXCR1000976296 Title: drd_safe_command_list: authtmp, fsdaemon for swlist, update-ux

Severity: Serious
Problem and details: The command drd runcmd swlist -l depot fails. DRD
(Dynamic Root Disk) is fixed to enable this, so drd runcmd can list the depots in the
depot registry at the time the drd clone was created. Note, it is preferable to focus
on depots registered on the active system because drd is being improved to use depots
that are on the active system and are not in the drd clone.
QXCR1000983266 Title: Msg from drd runcmd update-ux says "swmoeupdate" must be "swm
oeupdate"
Severity: Serious
Problem and details: During drd runcmd update-ux -s /depot, the following
message needs a space between /opt/swm/bin/swm and oeupdate: * Executing
command: /opt/swm/bin/swmoeupdate -s /depot.
nl
The DRD (Dynamic Root Disk) message is fixed to be: * Executing command:
/opt/swm/bin/swm oeupdate -s /depot.
QXCR1000984246 Title: The tmpauth.save directory is recursively created on multiple drd runcmds
Severity: Serious
Problem and details: Prior to the fix for QXCR1000984246, drd clone may fail if
the booted system was previously in an inactive image, that was modified or listed
repeatedly with drd runcmd. If it is an LVM-managed root, the clone will produce
messages similar to these:
ERROR: Cloning of source system image fails.

- Cloning the system image fails.

- Reading of command output fails.
- Could not read from file
"/var/opt/drd/tmp/drd1UOWhrCb/wUHPy9pu":
Resource temporarily unavailable (errno=11).
* Copying File Systems To New System Image failed with 1
error.
The fix for QXCR1000984246 eliminates this clone failure.
QXCR1000985424 Title: drd B.1123.A.3.4.91: drd clone always fails if we specify mirror_disk
Severity: Serious
Problem and details: The release of A.3.4 introduced a regression that caused creation
of mirrored clones to fail. This regression is fixed in A.3.5.

3 System and software requirements
This chapter discusses the system and software requirements for DRD (Dynamic Root Disk).
Required patches and software

In order to install and run, DRD (Dynamic Root Disk) requires the following:
• Judy-lib (Judy data structure library) version B.11.11.04.13 or greater.
• HP-UX 11i v2 — one of the following releases of SW-DIST (Software Distributor):
◦ PHCO_38149 or superseding patch.
◦ Product version B.11.23.0803.318 or greater.
• HP-UX 11i v3: SW-DIST (Software Distributor) version B.11.31.0709 or greater — when
installing DRD (Dynamic Root Disk) from an OE or AR or from Software Depot, these
dependencies are installed if your system is not having them already, this means that no special
action is required on your part.
DRD (Dynamic Root Disk) has patch requirements in addition to those listed above. For up-to-date
information on which patches are required and how to acquire them along with their dependencies,
see the DRD (Dynamic Root Disk) Downloads & Patches web page.
nl
If your root volume group is VxVM, there is a good chance you will need to install a VXVM patch
in order for DRD (Dynamic Root Disk) to operate correctly.
For more information about HP Dynamic Root Disk, see http://www.hp.com/go/drd-docs.
For more information related to HP-UX technical documentation, see http://www.hp.com/go/
hpux-core-docs.
Clone features
The drd clone command supports the following configurations:
• Clone target must be a single physical disk (with optional second disk for mirroring) or SAN
LUN. If an LVM root volume is spread across multiple disks, it can still be cloned, but the clone
will be on a single physical disk. A VxVM root disk group may reside on several disks, but
each disk must be an exact mirror of every other disk. The clone of a VxVM root disk group
will reside on a single physical disk.
• Root volume must be LVM (DRD [Dynamic Root Disk] versions A.1.0, A.1.1, and A.2.0); root
volume can be LVM or VxVM (DRD (Dynamic Root Disk) versions A.3.0 or later.)
• Prior to DRD [Dynamic Root Disk] version A.3.0, the root volume name must be vg00; the drd
clone command will only clone the contents of vg00, regardless of other volume groups that
exist (DRD (Dynamic Root Disk) versions A.1.0, A.1.1 and A.2.0). The root volume group
may have any name when using DRD (Dynamic Root Disk) version A.3.0 or later.
• Due to system calls DRD (Dynamic Root Disk) (and many other HP-UX applications) depend
on, DRD (Dynamic Root Disk) expects legacy Device Special Files (DSFs) to be present and
the legacy naming model to be enabled. Therefore HP suggests only partial migration to
persistent DSFs be performed as detailed in HP-UX 11i v3 Persistent DSF Migration Guide at
HPSC.
• On VxVM configurations, DRD (Dynamic Root Disk) expects OS Native Naming (osn). Enclosure
Based Naming (ebn) must be turned off.
Required patches and software 17

Safe command list
The drd runcmd command is used to run safe commands on the clone. The safe commands listed
below apply to all DRD (Dynamic Root Disk) releases, unless otherwise noted:
• swinstall
• swremove
• swmodify
• swlist
• swjob*
• view
• kctune (version A.1.1 and later)
• kcmodule
• kconfig
• mk_kernel
*The swjob command can be used to view SD logfiles on the clone. It cannot be used to
schedule jobs for later execution on the clone.
Installation and removal of patches and products

The drd runcmd command can be used in conjunction with swinstall and swremove to install
or remove patches. Use of drd runcmd to install or remove a non-patch product requires that all
its filesets be marked DRD-safe. You can determine whether a fileset has been marked DRD-safe
with the following command:
swlist –l fileset –a is_drd_safe –s depot_name product_name
Each fileset will be displayed with “true”, “false”, or blank. Filesets marked DRD-safe will display
“true”. Filesets marked DRD-unsafe display “false”. Filesets that display neither (blank) are treated
as DRD-unsafe.
Use of SD TUI/GUI
When using the SD TUI/GUI with drd runcmd, you may see messages about building a kernel
or rebooting the system. These messages are not accurate; under no circumstances will using SD
under drd runcmd lead to a reboot, nor will SD under drd runcmd lead to a kernel build on
the running system.
Installation requirements
DRD (Dynamic Root Disk) is dependent on other patches and software.
nl
For more information see, “Required patches and software” (page 17) section.
18 System and software requirements

4 Known problems, issues, limitations, and workarounds
This chapter explains in detail, about various problems, issues, limitations, and their workarounds
for DRD (Dynamic Root Disk) across many releases.
Out of memory issues

Issue
drd clone or drd sync fails with the following error when there are too many files in the root
volume group
ERROR: A fatal error has occurred in file usertasks/UserTask.cc.

Additional information:
Class and method where error happened: UserTask::runTask
Line number: 428
ERROR: Caught an unexpected std::exception.

Additional available information:
- The "SyncDRDSysUserTask" state machine was in the
"InactiveSysImgMountedState" state.
- The exception's what() value is: bad allocation exception thrown
- Please call the response center.
Workaround
The versions of DRD (Dynamic Root Disk) prior to A.3.13 support approximately 1 million files.
DRD (Dynamic Root Disk) version A.3.13 supports approximately 2.5 million files in the root volume
group. The number of files that can be cloned or synchronized can vary depending on each
environment (example, the length of path name). So it might fail even if the number of files is less
than 2.5 million.
If there are more files in the root volume group than supported by DRD (Dynamic Root Disk), the
directories containing large number of files must be excluded using -x exclude_list option (for drd
sync alone). For drd clone and drd sync to work properly, user must move the files from
root volume group to any other volume group so that the number of files in the root volume group
will be within the maximum file limit supported by DRD (Dynamic Root Disk).
DRD (Dynamic Root Disk) OE update issues

Issue
DRD (Dynamic Root Disk) runcmd update-ux fails with local source depots
When executing "drd runcmd update-ux" on the inactive DRD (Dynamic Root Disk) system image
using a directory depot (or mounted media) that resides on the active system image, the command
fails with this error:
ERROR: The expected depot does not exist at "<depot_name>"
Workaround
In order to use a directory depot on the active system image, you will need to install March 2010
or later versions of DRD (Dynamic Root Disk), SWM, and SW-DIST products from an OE depot.
This must be done before the clone is created, so the new DRD (Dynamic Root Disk), SWM, and
SW-DIST are on the active system and on the clone.
The following assumes the OE depot is at /var/depots/1003-DCOE. This must be executed as
root:
Out of memory issues 19

swinstall -x autoselect_dependencies=false -s /var/depots/1003-DCOE \
DRD SWM SW-DIST PHCO_36525
DRD (Dynamic Root Disk) updates from multiple-DVD media

Issue
DRD (Dynamic Root Disk) updates directly from media require the September 2010 OE (or later)
versions of DRD (Dynamic Root Disk), SWM and SW-DIST products
Workaround
In order to use a media depot to do a DRD (Dynamic Root Disk) update, you will need to first install
September 2010 or later versions of DRD (Dynamic Root Disk), SWM, and SW-DIST products from
the media. This must be done before the clone is created, so the new DRD (Dynamic Root Disk),
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 (Dynamic Root Disk) status reports error on rehosted boot disk
After rehosting a clone disk using "drd rehost" and booting that disk, running DRD (Dynamic Root
Disk) 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 (Dynamic Root Disk) 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 (Dynamic Root Disk), a disk specified in a DRD (Dynamic
Root Disk) 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 (Dynamic Root Disk) 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.
If DRD (Dynamic Root Disk) is given the disk as a target or mirror with the –x overwrite=true option,
there is a possibility that DRD (Dynamic Root Disk) will overwrite the LVM 2.x data disk when it is
in use.
Workaround
If the version of LVM 2.x on the system is from September 2008 or newer, and DRD (Dynamic
Root Disk) B.11.31.A.3.4 is also installed, DRD (Dynamic Root Disk) recognizes usage and
formatting by an LVM 2.x volume group on the system. In this case, DRD (Dynamic Root Disk) will
not overwrite a disk in use by LVM 1.0, or LVM 2.x.
If you have DRD (Dynamic Root Disk) B.11.31.A.3.4 installed and a version of LVM 2.x released
prior to September 2008, DRD (Dynamic Root Disk) recognizes when a disk is formatted, but will
overwrite it if the user specifies overwrite=true on the command line—even if the disk is in use.
DRD (Dynamic Root Disk) cannot determine usage in this case.
If the versions of DRD (Dynamic Root Disk) and LVM are not updated on the system—as is the case
for other usages (swap, dump, database, and so on.)—it is the system administrator’s responsibility
in these cases to identify a disk that can be overwritten by DRD (Dynamic Root Disk).
Status: More of a limitation than a problem.
Issue
limitation on nsswitch.conf entries during drd runcmd
The drd runcmd command does not support the following nsswitch.conf file entries on the clone
while managing software through drd runcmd. If the file contains them, the drd runcmd
command will fail.
passwd: compat
group: compat
hosts: nis [NOTFOUND=return] files
You might see the following error message during the execution of drd runcmd if your
nsswitch.conf file contains the "hosts: nis" entry:
ERROR: Could not contact host "myserver". Make sure

the hostname is correct and an absolute pathname
is specified (beginning with "/").
You might see the following error message during the execution of drd runcmd if your
nsswitch.conf file contains the "passwd compat" or "group: compat" entries:
ERROR: Permission is denied for the current operation.

There is no entry for user id 0 in the user
database. Check /etc/passwd and/or the NIS
user database.
Workaround
Because DRD (Dynamic Root Disk) does not need NIS to be running during swinstall, swremove,
or update you can move the nsswitch.conf file on the clone to a temporary location. After you
are done modifying the clone, you can move it back.
# drd mount
Limitations due to OS interactions 21

# bdf
# mv /var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf \
/var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf.orig
# drd runcmd <command_to_run>
# mv /var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf.orig \
/var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf
# drd umount
Alternatively, you can remove the "passwd" and "group" entries that contain compat from the
clone's /var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf file and replace the
"hosts" entry with:
hosts: dns [NOTFOUND=return] nis [NOTFOUND=return] files
Cloning problems
Issue
occasional failure on fully allocated file systems
In some cases where a file system is nearly full, drd clone fails with the following frecover
messages
frecover(1047): I/O error in write of file <path>

frecover(1073): frecover of <path basename>failed
In these cases, frecover appears to need some temporary work space to successfully create the
file.
Workaround
To resolve, free up some space in the nearly full source file system.
Status: Alternative copy mechanisms are being investigated. QXCR1000963803
Issue
failure cloning, sconf* line 7: syntax error
DRD (Dynamic Root Disk) can abort during a clone attempt if instances or disk devices have been
renumbered, and multiple agile device files exist for the same device. The following error can
occur:
# drd clone -pt /dev/disk/disk165 -x overwrite=true
======= 01/07/11 14:09:58 MST BEGIN Clone System Image Preview (user=root)
(jobid=iuxonx1)

ERROR: System information retrieval fails.
- Gathering system configuration information fails with the following error(s):
- Parsing the system configuration information fails with the
following error(s): "E:"/var/opt/drd/tmp/drdD2W270s/sconfVGg09Ev",
line 7: syntax error
E:Problems were encountered while parsing config file:
"/var/opt/drd/tmp/drdD2W270s/sconfVGg09Ev".
"
- Parsing of the configuration file
"/var/opt/drd/tmp/drdD2W270s/sconfVGg09Ev" fails.
* Reading Current System Information failed with 1 error.
======= 01/07/11 14:11:45 MST END Clone System Image Preview failed with 1
error. (user=root) (jobid=iuxonx1)
Workaround
When this issue is encountered during a clone or clone preview, and ioscan shows multiple agile
device files for the same device, remove the stale device files in /dev/disk and /dev/rdisk
using rmsf or rm if they are busy. On LVM systems, you may need to rebuild lvmtab using vgscan
-a if lvlnboot –v reports a stale device.
Issue
Dedicated dump devices not set up correctly on clone
After booting clone, dmesg can show errors if dump devices were set up using crashconf on
the original system:
ERROR: dump device 64:0x2 cannot be used and will be ignored:

device could not be opened
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 1, minor is 0xa27; start = 0, size = 744488960
In addition, on the booted clone, crashconf -v may also show incorrect entries in the persistent
dump device list similar to the following:
...
Persistent dump device list:
64:0x2
...
Workaround
This issue can be worked around by switching modes from config_crashconf_mode to
config_deprecated_mode using crashconf –o on the original system, prior to cloning. Any
dedicated dump devices will also need to be added to fstab prior to cloning.
Status: A fix will be available in a future DRD (Dynamic Root Disk) release. (QXCR1001101295)
Whole disk layout limitation

Issue
drd clone fails when trying to clone a booted system with Whole Disk layout
While Ignite-UX does supports the Whole Disk layout, which has everything configured in the root
(“/”) volume, DRD (Dynamic Root Disk) does not support the cloning of such a configuration. DRD
(Dynamic Root Disk) requires a volume manager to clone the boot disk contents and since Whole
disk layout does not have any volume manager configured drd clone command fails. It is an
expected behavior.
Here is the log seen while cloning such a configuration:
# drd clone -v -t /dev/disk/disk23
======= 10/01/12 12:16:09 IST BEGIN Clone System Image (user=root) (jobid=iuxonx6)
ERROR: System information retrieval fails.
- Gathering system configuration information fails with the following error(s):
- The command "/opt/drd/lbin/drd_save_config" fails with the return code 2. The error message from the command
is
"drd_save_config - running in drd context
drd_save_config: Error - disk not in the volume/disk group"
* Reading Current System Information failed with 1 error.
* DRD operation failed, contents of /var/opt/drd/tmp copied to /var/opt/drd/save.
======= 10/01/12 12:16:15 IST END Clone System Image

failed with 1 error. (user=root) (jobid=iuxonx6)
Workaround
There is no resolution to this case. DRD (Dynamic Root Disk) does not support Whole disk layout.
Whole disk layout limitation 23

Cloning with VxVM volumes having special characters
Issue
drd clone fails when VxVM volume names have special characters
While Ignite-UX does support VxVM volume names with special characters in it, DRD (Dynamic
Root Disk) does not support cloning of such a configuration. It is an expected behavior. Here is
the ERROR message seen while cloning such a configuration:
ERROR: Clone file system creation fails.

- Creating the target file systems fails.
- Start of output from /usr/lib/vxvm/bin/vxrootmir:
- VxVM vxrootmir INFO V-5-2-2501 14:36: Gathering information on the
current VxVM root configuration
VxVM vxrootmir ERROR V-5-2-2522 Getting plex name for volume
abc!j'5k#!pzvol
- VxVM vxprint ERROR V-5-1-625 Error compiling pattern:

unrecognized
variable name
Workaround
There is no resolution to this case. DRD (Dynamic Root Disk) does not support cloning of VxVM
volume with special characters in their names.
Cloning support when Enclosure Based Naming (EBN) scheme is enabled

with VxFS/VxVM 5.1 SP1 software
Issue
drd clone fails when EBN scheme is enabled on the system
VxFS/VxVM 5.1SP1 software, which is used for configuring the disks with VxFS/VxVM volumes
on a system, is supported from March 2014 release of HP-UX 11i v3. Whenever the naming
scheme is set to EBN scheme by the VxFS/VxVM 5.1SP1 software on the system, the drd clone
operation fails.
Workaround
You must change the naming scheme set on the system to OSN (Operating System Naming)
scheme, if it was set to EBN scheme. See the following:
1. Verify if the naming scheme is set to EBN scheme.
/usr/sbin/vxddladm get namingscheme
2. Change the naming scheme to OSN, if it was set to EBN, and run the drd clone operation.
/usr/sbin/vxddladm set namingscheme=osn mode=new

5 Documentation feedback
HP is committed to providing documentation that meets your needs. To help us improve the
documentation, send any errors, suggestions, or comments to Documentation Feedback
(docsfeedback@hp.com). Include the document title and part number, version number, or the URL
when submitting your feedback.
More on DRD (Dynamic Root Disk) documentation

For more information on DRD (Dynamic Root Disk) documents and other manuals, see Manuals
for HP DRD (Dynamic Root Disk) at http://www.hp.com/go/drd-docs.
Support policies for HP-UX

For more information about support policy for HP-UX, see HP-UX support policy.
More on DRD (Dynamic Root Disk) documentation 25

DRD (Dynamic Root Disk) Release Notes (Release March 2014, 766141-001a) (Edition 2, April 2015)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DRD (Dynamic Root Disk) Release Notes (Release March 2014, 766141-001a) (Edition 2, April 2015)

Uploaded by

Copyright:

Available Formats

DRD (Dynamic Root Disk) Release Notes

HP Part Number: 766141-001a

UNIX® is a registered trademark of The Open Group.

DRD (Dynamic Root Disk)

766141-001a A.3.13 HP-UX 11i v2 March 2015

HP-UX 11i v3 (Replaced document)

(Current version of the

(Original edition) HP-UX 11i v3 (Document retired)

◦ Ability to sync file system and volume group information.

Version A.3.13 (March 2014)

QXCR1001276997 Title: drd clone fails due to crashing drdconfigure

Version A.3.12 (March 2013)

Version A.3.13 (March 2014) 7

QXCR1001164981 Title: Changes to drd clone for fast reboot support

QXCR1001242324 Title: drdconfigure gets SIGSEGV and dump core file

Version A.3.11 (September 2012)

Version A.3.10 (March 2012)

QXCR1001120919 Title: “/opt/drd/lbin/drd_scan_hw_host” fails with the return code 1

8 Supported DRD (Dynamic Root Disk) releases

QXCR1001133378 Title: drd_scan_hw_host can attempt to allocate too much memory

QXCR1001159424 Title: DRD command fails with environment variable TMPDIR

QXCR1001167367 Title: drd clone fails with SIGSEGV

Version A.3.9 (September 2011)

Version A.3.9 (September 2011) 9

QXCR1001103256 Title: Discrepancy between otherRootDSFsCount and otherRootDSFs in DRD

QXCR1001104751 Title: Delivered script drd_unregister_mirror removes needed registry entries

* Mounting Inactive System Image ERROR:

corresponds to volume group version 1.0

QXCR1001105660 Title: runcmd does not forward X11

10 Supported DRD (Dynamic Root Disk) releases

Version A.3.8 (March 2011)

QXCR1000968514 Title: Need to remove registry during rehost

QXCR1001024172 Title: drd clone must reject NPIV target

ERROR: Making the file system bootable on clone fails.

Version A.3.8 (March 2011) 11

QXCR1001092279 Title: lvmpvg is not copied correctly during clone operation

Version A.3.6 and A.3.7 (September 2010)

QXCR1001054745 Title: SYSINFO_HOSTNAME does not support hyphen character

======= 06/29/10 16:26:50 MESZZ BEGIN Rehost System Image

12 Supported DRD (Dynamic Root Disk) releases

* End of messages from validation of the system info file

QXCR1000985412 Title: Failure to upd /opt/drd/wrappers/common_utils on older clone causes runcmd

Version A.3.6 and A.3.7 (September 2010) 13

QXCR1001023408 Title: IC348: incorrect drd runcmd usage

Version A.3.5 (March 2010)

======= 07/02/08 13:16:04 EDT BEGIN Clone System Image (user=root)

14 Supported DRD (Dynamic Root Disk) releases

Resolution: This issue is fixed in this release.

QXCR1000976296 Title: drd_safe_command_list: authtmp, fsdaemon for swlist, update-ux

ERROR: Cloning of source system image fails.

Version A.3.5 (March 2010) 15

16 Supported DRD (Dynamic Root Disk) releases

Required patches and software

◦ Product version B.11.23.0803.318 or greater.

Required patches and software 17

Installation and removal of patches and products

18 System and software requirements

Out of memory issues

ERROR: A fatal error has occurred in file usertasks/UserTask.cc.

ERROR: Caught an unexpected std::exception.

DRD (Dynamic Root Disk) OE update issues

ERROR: The expected depot does not exist at "<depot_name>"

Out of memory issues 19

DRD (Dynamic Root Disk) updates from multiple-DVD media