HP Integrity NonStop H-Series - Manual (Page 354)

Simplified Installation and Management of Multiple
Identical NonStop Servers (Cloning)
DSM/SCM User’s Guide — 529846-014
19 - 5
Applying a Software Configuration to a Clone Group
Applying a Software Configuration to a Clone
Group
Most of the process for applying a new software configuration to a clone group is
similar to the normal DSM/SCM process.
Creating a Clone Group Software Configuration
To create a new software configuration for a clone group, create a new software
configuration for the master target.

SUTs copied to the clone group configuration choose licensed products based on
the master target CUSTFILE.

In Planner Interface displays, only the master indicates that the configuration
exists. The clones do not indicate it.
When you finish creating the new software configuration, click Build/Apply....
Building and Applying a Clone Group Configuration Revision
To avoid manually starting each clone apply in the Target Interface, make sure these
options are selected:

Build, apply & process snapshot

In the Output... dialog, Disk (under Activation package/snapshot location)
Other Build notes:

SYSGEN and system load indications are accurate for the master target, but they
might not be for clone targets unless their software and SYSnn are exactly
identical to the master.

All applies to all clones start at the specified apply time.

Target profile values for the master target, such as the Manage OSS Files
checkbox, also apply to clone targets.
After you click OK, the build starts for the clone group at the selected time.
All indicators in the Planner Interface reflect the Build/Apply request for only the
master. The master Build/Apply request does not indicate completion until every clone
apply is complete.
If a Clone Group apply fails to start, you can manually start it in the Target Interface.
When one Group apply fails, the others continue independently.
Caution. Any software configuration installed for a clone group is indicated in the Planner
Interface only on the master target. The Planner Interface does not indicate that the clones
have the newly installed configuration. Therefore, Planner Interface information for clones
might not appear current.