Dynamic Root Disk A.3.12.* Release Notes HP-UX 11i v2, HP-UX 11i v3 HP Part Number: 5900-2101 Published: March 2013 Edition: 1.
© Copyright 2007, 2010, 2013 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.
QXCR1001120919. Prior to this fix drd_scan_hw_host could go into interactive mode if the source type could not be determined. With this fix we no longer consider whether the source type can be determined and, thus, never go interactive. QXCR1001129462. Prior to this fix DRD did not copy 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.
* 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.
- 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.
QXCR1001054745. The issue where drd rehost will not allow SYSINFO_HOSTNAME to contain the "-" character has been 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.
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 • VxVM 5.0 on HP-UX 11i v2 (11.23): PHCO_38570 • VxVM 4.1 on HP-UX 11i v3 (11.31): PHCO_38654 • VxVM 4.1 on HP-UX 11i v2 (11.23): PHCO_38464 2.6 Version A.3.5 (March 2010) DRD version A.3.
QXCR1000976296: The command "drd runcmd swlist -l depot" fails. Drd 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.
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".
4.5 Whole disk layout limitation Issue Description – 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 does not support the cloning of such a configuration. DRD 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’s an expected behavior.
There is no resolution to this case. DRD does not supports cloning of VxVM volume with special characters in their names.
