HP Dynamic Root Disk Getting Started Guide

Dynamic Root Disk

October 2011

http://www.hp.com/go/DRD

The information contained herein is subject to change without notice

Agenda

• DRD overview

• DRD use models

– Recovery

– Maintenance

– Provisioning/Rehosting

– Update

• DRD status & sync

• Real-life examples

• Wrap-up

DRD overview

Mission/benefits

Significantly reduce the downtime needed to perform

HP-UX software maintenance

Reduce the downtime required for recovery from

administrative errors

Perform software update work during normal business

DRD is supported on 11i v2 and v3; the orange lightning bolt on future slides indicates

areas of increased feature

support on 11i v3

hours, or whenever convenient

Provision systems quickly and efficiently

Simplify testing

3

DRD use models

DRD use case

Recovery

1. Original system image is active

2. Create a clone of the original system

image (drd clone)

3. When clone completes, two copies

of system image exist (drd status)

4. If a problem is encountered with

original image, boot clone

(drd activate)

clone

Active

5

DRD use case

Maintenance (slide 1 of 3)

1. Original system image is active

2. Create a clone of the original system image

(drd clone)

3. When complete, two copies of system image

exist (drd status)

clone

Active

6

DRD use case

Maintenance (slide 2 of 3)

1. Original system image is active

2. Create a clone of the original system image

(drd clone)

3. When complete, two copies of system image

exist (drd status)

4. Modify inactive image to reach desired state

– install patches & products (drd runcmd

swinstall)

Apply patches & products

5. When modification completes, have an

unmodified original image and a modified clone

6. Synchronize files from the active image to the

clone – password files, log files, etc. (drd sync)

sync

Active

The orange lightning bolt identifies increased feature support for 11i v3; in this case, product installation on a clone is supported only on 11i v3,

with patch installation supported on 11i v3 and 11i v2

7

Modified clone

DRD use case

Maintenance (slide 3 of 3)

1. Original system image is active

2. Create a clone of the original system image

(drd clone)

3. When complete, two copies of system image

exist (drd status)

4. Modify inactive image to reach desired state

– install patches & products (drd runcmd

swinstall)

Apply patches & products

5. When modification completes, have an

unmodified original image and a modified clone

6. Synchronize files from the active image to the

clone – password files, log files, etc. (drd sync)

7. Boot the clone when ready (drd activate)

8. If original system preferred, boot the

unmodified original image to return to

Modified clone

Active

8

original state (drd activate)

DRD use case

High Availability with DRD and MirrorDisk/UX (slide 1 of 3)

1. Original mirrored system image is active

2. Create mirrored clone of the original system

image (drd clone)

3. When complete, four copies of system image

exist (drd status)

clone

Active

9

DRD use case

High Availability with DRD and MirrorDisk/UX (slide 2 of 3)

1. Original mirrored system image is active

2. Create mirrored clone of the original system

image (drd clone)

3. When complete, four copies of system image

exist (drd status)

4. Patch inactive image (drd runcmd swinstall)

5. When modification completes, have an

unmodified original image and a modified clone

10

Active

sync

Apply patches & products

Modified clone w/patches

6. Synchronize files from the active image to the

clone – password files, log files, etc. (drd sync)

DRD use case

High Availability with DRD and MirrorDisk/UX (slide 3 of 3)

1. Original mirrored system image is active

2. Create mirrored clone of the original system

image (drd clone)

3. When complete, four copies of system image

exist (drd status)

4. Patch inactive image (drd runcmd swinstall)

5. When modification completes, have an

unmodified original image and a modified clone

6. Synchronize files from the active image to the

clone – password files, log files, etc. (drd sync)

11

7. Boot the clone when ready (drd activate)

8. In event of a sw problem, boot the unmodified

original image to return to original state

(drd activate)

9. In the event of a hw problem, run from mirror

Modified clone w/patches

Active

DRD Customer use models

High Availability with DRD and MirrorDisk/UX

Requires 4 LUNs

Requires a MirrorDisk/UX license

Enables fast mirrored recovery

Easy to implement

12

drd clone –t/dev/dsk/c3t15d0 –x

mirror_disk=/dev/dsk/c4t15d0

Provides protection against both

hardware and software failures