Migrating an Integrity HP-UX 11iv3 Instance to New Hardware

If this is your situation Consider usin

this method:

If you are movin

from PA to IPF Install the new system from depots.

Overview of the DRD method

The overall approach used here is to create a DRD clone on an older “source” system, modify it to

support the new “target” system model, and move it to the new target system. The recommended steps

detail the upgrades and changes that must be accomplished on the source system, as well as those

that must be defined for automatic consumption during boot of the target system.

Note:

A system administrator may choose to move the actual boot

disk from the source system to the target. To do this, the

changes that follow should be applied to the boot disk

rather than to the DRD clone. However, this makes it

somewhat more difficult to revert to the original hardware if

issues are encountered. For this reason, the procedure

below is described for a DRD clone.

Assumptions for the DRD method

• DynRootDisk is installed on the source system and on the DRD clone of the source system at

release B.11.31.A.3.6 or above. This release, supplied with the September 2010 media,

includes support for kernel management on the clone using “drd runcmd mk_kernel”, “drd

runcmd kcmodule” and “drd runcmd kconfig” (as well as the previously supported “drd

runcmd kctune”).

• The release of HP-UX on the source system is 11iv3.

• The root group is managed by LVM.

Related Information

Additional information regarding Dynamic Root Disk can be obtained from the DRD documentation

web site located at: http://www.hp.com/go/drd-docs

. The documents located on this site include the

following:

• Dynamic Root Disk Administrator’s Guide

• Dynamic Root disk Quick Start & Best Practices

• Exploring DRD Rehosting in HP-UX 11iv2 and 11iv3

Summary of Steps for the DRD method

In some cases the goal is to move a pre-existing HP-UX instance to new hardware; in other cases, the

goal is to deploy a very similar system (same HP-UX release, same patches, etc.) with a different

network identify (hostname, MAC and IP addresses, etc.). The difference between the steps needed

for these two scenarios is small, so both scenarios are covered here. To distinguish between these

similar scenarios, the first is called the

move

scenario, and the second is called the

clone

scenario.

The following steps are used in both scenarios: