Dynamic Root Disk: Quick Start & Best Practices

2. Use drd status to view the clone: drd status

3. Install the QPK and PHCO_77777: drd runcmd swinstall \

-s depot_svr:/var/depots/1131 -x patch_match_target=true

4. Ensure the patch and QPK is installed: drd runcmd swlist QPKBASE QPKAPPS \

PHCO_77777

5. Create a shutdown script that runs drd sync so that files changed on the original image after

the clone was created will be propagated to the clone (see the “DRD sync” section below for more

details)

6. Activate and boot the clone: drd activate -x reboot=true

BP1: Additional Considerations

DRD-Safe: Overview

Any patch or product that is installed on a DRD clone must be DRD-safe. That is, the patch/product

must not impact the running system.

• For HP-UX 11i v2, only patches are checked prior to release to ensure they are DRD-safe. Almost

all of the HP-UX 11i v2 patches are DRD-safe, and those that are not are listed in the

drd_unsafe_patch_list file; see the next section for details about this file. Most HP-UX 11i v2

products are not safe, and thus cannot be managed with DRD.

• For HP-UX 11i v3, patches and all products in the Operating Environments are checked prior to

release for DRD safety. Any patches that are not DRD-safe either have the is_drd_safe flag set

to false or are listed in the drd_unsafe_patch_list file; see the next section for details about

this file. Any products or patches that are not DRD-safe will not be installed during a DRD session.

• Note that firmware patches are not DRD-safe and will be automatically excluded from any attempt

to install or remove them from an inactive image. One of the values of DRD is that once a DRD

clone is created and booted, the original image (with no changes) acts as a backup and can be

reactivated at any time if the clone does not operate as expected. If a firmware patch was loaded

on the clone once it was booted, this new firmware will be present if the original image is booted.

• For products, the is_drd_safe attribute is used to indicate whether a product is DRD-safe. If this

attribute is not set or is missing, the product is considered to be DRD-unsafe.

• The DRD toolset will not process products or patches that are DRD-unsafe. For products and HP-UX

11i v3 patches, the DRD toolset uses the is_drd_safe attribute to determine safety. For HP-UX

11i v2 patches, any patch that is not safe is placed on the DRD Unsafe Patch List. Please see the

section below, “DRD-safe: Updating the drd_unsafe_patch_list File” for information on how to make

sure this list is current on your system.

Important:

Any patch that has been written for a specific site, or that

has a tag including the UNOF string, has not been through

DRD-safe certification. These types of patches should not be

applied—by executing drd runcmd—without thorough

discussion with the patch provider

DRD-Safe: Updating the drd_unsafe_patch_list file

The /etc/opt/drd/drd_unsafe_patch_list file is delivered as a volatile file containing a list

of DRD-unsafe patches delivered without the attribute is_drd_safe set to false. Most new patches