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

• 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
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 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 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 would be changes
to password files, log files, etc. Enhancements to drd sync to:
o allow users to exclude files and directories, in addition to those described in drd
sync (1M), from the sync operation
o support frequently changing files such as logs of automated processes.
o 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.