Dynamic Root Disk A.3.13 Release Notes HP-UX 11i v2, HP-UX 11i v3 HP Part Number: 766141-001 Published: March 2014 Edition: 1.
© Copyright 2007, 2010, 2014 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.
Contents HP secure development lifecycle......................................................................4 1 Overview..................................................................................................5 Product features........................................................................................................................5 2 Supported DRD releases..............................................................................
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.
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.
• 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.
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.
Version A.3.11 (September 2012) DRD version A.3.11 contains only defect fixes and quality improvements. DRD version A.3.11 contains fixes for the following defects: • QXCR1001186489: 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. Version A.3.10 (March 2012) DRD version A.3.10 contains only defect fixes and quality improvements.
on LVM2 systems, and “drd sync”. The entries which were deleted pertain to volMgrVers, syncDate, and creationDate. On LVM 2 systems, “drd mount” would produce 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.
"/var/opt/drd/mnts/sysimage_000". Unmount the volume with umount(1M), then re-run drd. • QXCR1001038220: 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 manpage reflects this change. • QXCR1001074042: Prior to this fix, when PHCO_40522 was installed on an HP-UX 11iv2 (11.23) system, the clone operation would fail with an unmount error. Now clone works as expected.
DRD version A.3.6 and A.3.7 contain fixes for the following defects: • QXCR1000894322: 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 filesystem. • QXCR1000933863: Signals (SIGINT, SIGQUIT, SIGHUP and SIGTERM) to drd runcmd will no longer have extraneous fsdaemon and swagentd processes running. • QXCR1000985412: Prior to the fix for QXCR1000985412, customers who had release B.11.xx.3.
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).
3 System and software requirements This chapter discusses the system and software requirements for DRD. 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: ◦ • 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.
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 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.
4 Known problems and workarounds This chapter discusses the known issues and workarounds. 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.
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.
If DRD is given the disk as a target or mirror with the –x overwrite=true option, there is a possibility that DRD 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 B.11.31.A.3.4 is also installed, DRD recognizes usage and formatting by an LVM 2.x volume group on the system. In this case, DRD will not overwrite a disk in use by LVM 1.0, or LVM 2.x. If you have DRD B.11.31.A.3.4 installed and a version of LVM 2.
Alternatively, you can remove the "passwd" and "group" entries that contain compat from the clone's /var/opt/drd/mnts/sysimage_001/etc/nsswitch.
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 ...
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 does not supports cloning of VxVM volume with special characters in their names.
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.
