HP Dynamic Root Disk (DRD) manual Updating and managing products with drd runcmd

Page 19

h20392.www2.hp.com/portal/swdepot/ displayInstallInfo.do?productNumber=DynRootDisk#download.

It is helpful during maintenance planning for system administrators to be able to determine which, if any, patches are not DRD-safe, and to make plans regarding these patches. See the DRD-Safe Concepts for HP-UX 11i v2 and Later white paper, located at http://www.hp.com/go/drd-docs, for information about identifying such patches and alternatives on how to manage them without using the drd runcmd operation.

3.2.2 Patches with special installation instructions

Patches may include Special Installation Instructions, or SIIs, which contain specific tasks for the user to perform when they install certain patches. If you install patches with SIIs on an inactive DRD system image, ensure the following:

•You must not stop/kill or restart any processes or daemons. Because the patch is being installed on an inactive DRD system image, these actions are not needed, and in fact could leave the running system in an undesirable state. When the inactive system image is booted, all processes are stopped and restarted.

•Only make kernel changes by executing: drd runcmd kctune

3.3Updating and managing products with drd runcmd

For non-patch products, a new fileset-level packaging attribute, is_drd_safe, has been introduced. The value of the attribute defaults to false, so any package created before the attribute was introduced will be rejected by swinstall, swremove, and update-uxcommands invoked by the drd runcmd operation. Because the DRD product was not available at the initial release of 11i v2, relatively few non-patch products have the is_drd_safe attribute set to true. For HP-UX 11i v3, however, most products will have the is_drd_safe attribute set to true.

To determine if a non-patch product can be installed or removed using drd runcmd, execute the command:

#/usr/sbin/swlist –l fileset –a is_drd_safe _product_name_ and check that all filesets have is_drd_safe set to true.

3.4Special considerations for firmware patches

A firmware patch changes the firmware the next time the patched image is booted. Because the firmware is shared by both the active and inactive system images, there is no ability to have an unchanged copy of the firmware as a fail-safe mechanism. As a result, the benefit of DRD as a Hot Recovery mechanism cannot be provided with firmware patches. Firmware patches set the fileset attribute is_drd_safe to false to supply a checkinstall script that prevents installation in a DRD session.

IMPORTANT: System administrators need to be aware that any firmware change cannot be reversed by booting a different system image.

3.5Restrictions on update-uxand sw* commands invoked by drd runcmd

Options on the Software Distributor commands that can be used with drd runcmd are limited by the need to ensure that operations are DRD-safe. The restrictions include the following:

•The -Fand -x fix=true options are not supported for drd runcmd swverify operations. Use of these options could result in changes to the booted system.

•The use of double quotation marks and wild card symbols (*, ?) in the command line must be escaped with a backslash character (\), as in the following example:

drd runcmd swinstall –s depot_server:/var/opt/patches \*

3.3 Updating and managing products with drd runcmd 19

Page 18 Page 20
Image 19
Page 18 Page 20
Contents Dynamic Root Disk A.3.10.* Administrators Guide Document Part Number DRD Version Supported Operating Systems Table of Contents Glossary Index Troubleshooting DRD Support and other resourcesDRD commands Rehosting and unrehosting systemsList of Figures List of Examples Terminology Commands overviewAbout Dynamic Root Disk Conceptual overviewDownloading and installing Dynamic Root Disk Locating disks on HP-UX 11i v2 systems Cloning the active system imageActive system image Locating disks# /usr/sbin/ioscan -fnkC disk Locating disks on HP-UX 11i v3 Integrity systems# /usr/sbin/ioscan -m dsf Using DRD for limited disk availability checks Using other utilities to determine disk availabilityChoosing a target disk Creating the clone Using drd clone to analyze disk sizeCloning the active system image Success Error Example 2-7 The drd clone command outputAdding or removing a disk Example 2-8 The drd clone command output for SAN diskSwinstall Swremove Swlist Swmodify Swverify Swjob DRD-Safe commands and PackagesUpdating and maintaining software on the clone Updating and managing patches with drd runcmd Kctune Update-ux View Kcmodule Kconfig Mkkernel Swm jobDRD-Safe patches and the drdunsafepatchlist file Updating and managing products with drd runcmd Patches with special installation instructionsSpecial considerations for firmware patches Viewing logs Mounting the inactive system image Accessing the inactive system imagePerforming administrative tasks on the inactive system image Enter the patches into a file such as Unmounting the inactive system image Compare vxconfigbackup with the clone copyUnmounting the inactive system image Page Quick start-basic synchronization OverviewDetermining the list of files in the booted volume group Drd sync commandTrimming the list of files to be synchronized Files that have changed on the clone Copying the files to the inactive clone image Drd sync system shutdown script Page Preparing the inactive system image to activate later Activating the inactive system image# /opt/drd/bin/drd activate Undoing activation of the inactive system image # /usr/bin/more /stand/bootconf l /dev/dsk/c2t0d0s2Activating the inactive system image Undoing activation of the inactive system image Page Rehosting overview Rehosting and unrehosting systemsRehosting examples Example 7-1 Provisioning a new system Rehosting a mirrored image# rm /var/opt/drd/registry/registry.xml Unrehosting overviewPage Troubleshooting DRD Page Contacting HP Support and other resourcesLocating this guide New and changed information in this editionRelated information Typographic conventions Find1 Page DRD command syntax DRD commandsDrd activate command Logverbosity=4 HAalternatebootdisk=blockdevicespecialfileIgnoreunmountedfs=truefalse Logfile=/var/opt/drd/drd.logCopyautofile option Drd clone commandReboot=truefalse Verbosity=3 DefaultCopyautofile=truefalseblockdevicespecialfile TtargetdevicefileEnforcedsa=truefalse Drd deactivate command Drd mount command Example A-1 File system mount points Drd rehost command Devicespecialfile -v-xextended option=value -x-?-Xoptionfile Extended options Drd runcmd command Extended options Drd status command Alternatebootdisk=blockdevicespecialfile Usr/sbin/swlist -l file, or Drd sync commandExcludelist= Drd umount commandAlternatebootdisk=blockdevicespecialfile Drd unrehost command Fsysteminformationfile Mirrordisk=blockdevicespecialfile Page Glossary Booted systemSystem image Index Idisk partition, 10, 11 inactive system file system
Top Page Image Contents