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

else

{ init _HP_CLONING = "TRUE" }

To:

init _HP_CLONING = "TRUE"

Step 7: Create depots with additional software for the target

The target system may need additional software, particularly if the system differs greatly from the

source. To ensure that all needed kernel modules, as well as any other required software, are

available, consult the Errata document for the target system. The Errata document can be found by

searching the web for the model and the string “Errata”. There may be both an HP-UX Errata site

and a System Errata site for a given model.

Create one or more depots containing all needed software. It is probably most convenient to create

the depots so that any single depot does not contain multiple versions of the same software.

For example, if the target system is a BL860C i2 system, the Errata document available in May, 2010

indicates that HP-UX 11iv3 OE Update Release for March 2010 and additional software listed in the

document are required. For migration to a BL860C i2 system, it is probably most convenient to

create or use an existing depot containing the Operating Environment (Data Center, Virtual Server,

High Availability, or Base) from March 2010 that you intend to install, and create one or more

additional depots with the remaining software documented in the Errata and applicable to your

environment. Often, software that implements firmware changes is packaged so that it excludes itself

during an Ignite-UX recovery. Delay installing firmware changes until after you have deployed the

recovery image and other Errata software.

If desired, you can use the swcopy command to copy software from various source depots to one or

more directory depots. Note that if you are copying a serial (tar format) depot, you need to issue the

swcopy command from the system containing the serial depot. See swcopy(1M) for more

information.

Step 8: Ensure iux_postload scripts from the recovery archive run

correctly

Currently, Ignite-UX determines the list all iux_postload scripts after the recovery archive is installed.

However, the iux_postload scripts are not actually run until after the depots are also loaded. This is

not the correct processing for migration to new hardware. In this case, the scripts need to run before

additional kernel software is installed, which may replace products with newer revisions, thus

changing or removing iux_postload scripts.

To ensure that the iux_postload scripts are run at the right time, and that Ignite-UX executes a

harmless script later – at the “wrong time” - create the following two scripts, with owner bin:bin and

permission 755, named /var/opt/ignite/scripts/run_iux_postloads, as shown in Figure

2 and /var/opt/ignite/scripts/restore_iux_postloads, as shown in Figure 3.