Dynamic Root Disk: Quick Start & Best Practices

# /opt/drd/bin/drd runcmd swinstall -p -x patch_match_target\

-s depot_svr:/var/depots/

mydepot

Each unsafe selection will be rejected with an appropriate message, and the remaining selections will

be listed.

Planning the Installation of DRD-Unsafe Patches

Examine the list of DRD-unsafe patches determined in the section above. For each patch, apply the

following logic:

1. Does the patch apply to a product that is not used and for which no use is planned? If so, no

action is necessary.

2. Has the patch been superseded by a DRD-safe patch? If so, check the superseding patch’s rating

and delivery date in the patch database at the HP IT Resource Center:

http://www.itrc.com. If you

are satisfied with the quality measures for the superseding patch, swcopy it into your patch depot.

When the actual DRD installation is run, use the option

“-x patch_match_target=true”.

3. Does the patch NOT require a kernel build or reboot? If so, one option is to apply it to the booted

system before creating the clone.

4. If the patch is needed on your system, has not been superseded by a DRD-safe patch, and requires

a kernel build or reboot, the patch must be applied to the inactive system image after the image is

booted. Add the patch to a list of patches (or a selection file of patches) that you plan to install as

soon as the inactive system image is booted.

Installing from Serial Depots

HP does not support executing the drd runcmd to install from a serial depot source. Attempts to do

so result in the following error:

ERROR: The source you have chosen is a tape device located on the

booted system. Installing from this source is not supported

under drd runcmd. To install software from this tape device,

first copy the software to a non-tape device using swcopy.

To copy software from a serial depot to a directory depot, use the following command:

# /usr/sbin/swcopy -s /path/to/serial.depot SoftwareSelections @ \

/path/to/non-serial/depot

If the software you are trying to copy does not have its dependencies in the depot, you should add

the –x enforce_dependencies=false option to the swcopy command.

Verifying Operations

Verify scripts have always been required to refrain from making changes either to the file system or to

the process space of the system where a swverify operation is run. For this reason, swverify

operations are always DRD-safe, even for patches and products that are not DRD-safe for sw* and

update-ux operations. The same does

not

apply to swverify operations with the -F option,

which causes “fix” scripts to be run. Use of the -F option on a swverify command is not supported

under drd runcmd.

If you attempt to run the swverify operation with the -F option under drd runcmd, DRD exits

with a failure return code without running any fix scripts.