Successful System Cloning using Ignite-UX

Am I going to clone a system that has the same hardware model

string?

If you are cloning to another system of the same model, you must use the Ignite-UX Graphical User

Interface (GUI) to manually change the value of Cloning to different HW? to TRUE using the

Additional… button on the Basic tab.

Ignite-UX determines whether you are cloning (installing) to different hardware or not based upon

the setting of the model string for the system. A new kernel is not created when you are cloning to

another system with the same model string. If the system that is being cloned requires different

kernel drivers to support different hardware, these drivers may not be in the kernel because no new

kernel is created.

For example, you could install to a disk for which the kernel in the archive did not contain drivers.

This kernel would panic on boot because it could not activate the root volume group.

Do I have a high enough firmware revision to run the version of HP-UX

that is in the Ignite-UX installation kernel?

When you are planning to use Ignite-UX to clone or recover systems, you must ensure that the

firmware revision you are using is a high enough revision to run the version of HP-UX in the Ignite-

UX kernel (see

HP-UX installation kernel support).

Do I have any HP-UX applications loaded that are known to have

problems after being loaded onto cloned systems?

Some applications do not provide any iux_postload or iux_postconfig scripts to remove

their configuration and/or address any potential issues when you are cloning a system.

Manual configuration may be required to clean up an application that gets confused after cloning.

You may need to disable, remove, or reconfigure the application.

For example, the HP Instant Capacity (iCAP)

# icod_stat

product (prior to version B.06.00) usually does not

function correctly after cloning if the original system was an iCAP system:

ERROR: The software ID of this system does not match the ID stored

in the iCAP processor configuration. Contact your local support

representative to correct the configuration.

If you are running an iCAP version earlier than B.06.00 and you install a golden image or core

operating system SD depot over an existing HP-UX installation, the system is left in a non-iCAP

state. Consider the following issues when you plan for this situation as part of any (re)installation:

• iCAP versions B.06.x and B.07.x only support cell based systems. You should not install a

golden image containing iCAP version B.06.x or B.07.x onto a non-cell based system. V, N, and

L series iCAP systems must continue to run pre-B.06.00 iCAP versions.

• Prior to reinstalling any existing cell-based iCAP system you should ensure that it is running iCAP

version B.06.00 or later before reinstalling. When you upgrade to iCAP version C.06.00 or

This product was formerly known as HP Instant Capacity on Demand (or iCOD) and has been changed to HP Instant Capacity for HP 9000

and HP Integrity Servers, also known as Instant Capacity or iCAP.