Dynamic Root Disk Frequently Asked Questions HP Part Number: 766143-001 Published: March 2014 Edition: 1.
© Copyright 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 About This Document.....................................................................................5 Intended Audience....................................................................................................................5 Related Documents...................................................................................................................5 Publishing History.......
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.
About This Document This document includes frequently asked questions about Dynamic Root Disk. Intended Audience This document is intended for system and network administrators responsible for installing, configuring, and managing HP-UX servers and workstations. Administrators are assumed to have an in-depth knowledge of HP-UX operating system concepts, commands, and configuration.
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.
This list of frequently asked questions (FAQs) is created by the DRD engineering team. These FAQs are compiled periodically as input dictates. We invite your questions! If you have questions, contact HP Support at 1 (800) 633-3600. Dynamic Root Disk FAQ categories are as follows: » 1. General » 2. Using Dynamic Root Disk Commands » 3. Troubleshooting Dynamic Root Disk Frequently Asked Questions 1- General 1-1. What is DRD? 1-2. What HP-UX releases will DRD run on? 1-3.
1-22. Where can I get more information on how to create a DRD-Safe software package? 1-23 What are the DRD considerations for legacy Device Special Files (DSFs)? 1-24 Does DRD Support SoftReboot feature? 1-1. Q: What is DRD? A: Dynamic Root Disk (DRD) is an HP-UX system administration toolset that lets you create and modify an inactive system image without shutting down the system. To do this, you can clone the active system image and modify the cloned (inactive) system image while the system is running.
drd clone drd deactivate drd mount drd rehost drd runcmd drd status drd sync drd umount drd unrehost In addition, the drd runcmd command allows you to run specific Software Distributor (SD) commands on the inactive system image only. These SD commands are: swinstall swremove swlist swmodify swverify swjob Two other commands can be executed by the drd runcmd command. The view command can be used to view logs produced by commands that were executed by drd runcmd.
1-8. Q: I have many disks I would like to clone in one operation. Is the target a single disk? A: Yes, for this release of DRD, the target disk must be a single disk. top 1-9. Q: What if the DRD contains more than one disk? Does DRD handle this? A: Currently, the target disk must be a single physical disk, or SAN LUN, large enough to hold all of the root volume file systems. This allows a customer to clone the root volume group even if it is spread across multiple disks.
At this point, the bootpath for vpmon on the nPar points to an inactive (original) image even though vpmon is still up and running. The running vpmon maintains the master copy of the vPar database in memory. This data is synchronized with each running vPars local copy of /stand/vpdb. When vpmon is booted, the local /stand/vpdb is loaded into memory and serves as the master copy.
1-14. Q: Does the cloned root disk (VG) contain same VGID as the original root VG? A: The volume group will be vg00 when the clone is booted. It will have a different minor number than the original vg00. top 1-15. Q: How is lvmtab adjusted to reflect the new device name for the disk in vg00? A: The copy of lvmtab on the cloned image is modified by the clone operation to contain information that will reflect the desired volume groups when the clone is booted. top 1-16.
the booted system. For example, if the two disks are on the same SCSI chain, then I/O to the clone will affect performance of I/O on the booted system. DRD's performance is similar to system performance when using Ignite to create recovery images, which many system administrators find acceptable. top 1-21. Q: IgniteUX offers net and tape images.
2-4. If I am running multiple drd runcmd operations, can I avoid mounting and unmounting the inactive system image for each runcmd execution? 2-5. Does the DRD clone operation verify that the target is not in use or part of another VG? Once the root disk is cloned, is there anything in the operating system that prevents the non-active target from being reused? How can inactive targets be identified? 2-6. Can I vgimport the target disk as /dev/vgtmp? 2-7.
drd clone -p -v -t path_to_block_DSF Where path_to_block_DSF is of the form: HP-UX 11i v2: /dev/disk/cXtXdX HP-UX 11i v3: /dev/disk/diskX The preview operation includes the disk space analysis needed to see if the target disk is sufficiently large. top 2-4.
command, see the drd_status(1M) manpage. To determine the validity of all software installed on the inactive system image, execute: drd runcmd swverify \* top 2-8. Q: Some processes in DRD, particularly drd clone and drd runcmd, take a significant amount of time. Can these processes be interrupted? A: All DRD processes, including drd clone and drd runcmd, can be safely interrupted issuing Control/C (SIGINT) from the controlling terminal or by issuing kill HUP (SIGHUP).
with ========. If there is too much data in the log, locate the first sign of trouble and the next several error messages.) Make available information from the swagent.log files stored in depots (for example, /var/spool/sw/swagent.log). The swagent daemon creates these when it reads or writes from a depot containing information written by swagent. Depots at other locations have a similarswagent.log.
A: DRD does utilize fbackup and frecover, however, we have not encountered a problem with busy files. While frecover can fail to overwrite busy files, this is not a problem in DRD because it is cloning a fresh volume group. fbackup can fail if files are changing during the fbackup operation, but this is more common with spool files and log files. If you are concerned, use the drd runcmd swverify \* command to check the integrity of the clone after it is created. top 3-7.
