Dynamic Root Disk A.3.10.* Release Notes HP-UX 11i v2, HP-UX 11i v3 HP Part Number: 5900-2101 Published: January 2012 Edition: 1.
© Copyright 2007, 2010, 2012 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.
HP Dynamic Root Disk (DRD) Release Notes Table of Contents HP Dynamic Root Disk (DRD) Release Notes............................................................................... 1 1. Overview ..................................................................................................................................... 2 1.1 Product Features.................................................................................................................... 2 2. Supported DRD Releases .................
1. Overview Dynamic Root Disk (DRD) 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 is available for download from Software Depot. System administrators use DRD to manage system images on HP PA-RISC and Itanium® -based systems. DRD complements other parts of your total HP solution by reducing system downtime while installing and updating patches and other software.
• • • • • • 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).
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.
2.2 Version A.3.9 (September 2011) DRD version A.3.9 contains the following new features: • DRD clone operation can now copy autofile, so that customizations are retained on the clone. DRD version A.3.9 contains fixes for the following defects: QXCR1000988687. 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.
fix “drd sync” now handles unprintable control characters as well as characters in the extended ASCII code set. 2.3 Version A.3.8 (March 2011) DRD version A.3.8 contains the following new features: • Ability to sync file system and volume group information • New FAQ entry on using DRD in a vPars environment DRD version A.3.8 contains fixes for the following defects: QXCR1000968514.
2.4 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 version A.3.7 contains the following 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 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.
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.
======= * * * * * * ERROR: 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 Analysis of file system creation fails. - Analysis of target fails. - The analysis step for creation of an inactive system image failed.
3. System and Software Requirements 3.1 Required Patches and Software In order to install and run, DRD requires the following: • Judy-lib (Judy data structure library) version B.11.11.04.13 or greater • HP-UX 11i v2: o 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.
• • • • • • • • • • swremove swverify 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. 3.4 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.
4. Known Problems and Workarounds 4.
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 Issue Resolution 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. 4.
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.
======= 01/07/11 14:09:58 MST (jobid=iuxonx1) BEGIN Clone System Image Preview (user=root) * Reading Current System Information 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".
3
*5900-2101* Printed in the US
