DSM/SCM User's Guide

DSM/SCM User’s Guide — 529846-014
19 - 1
19
Simplified Installation and
Management of Multiple Identical
NonStop Servers (Cloning)
Cloning is the simplified use of DSM/SCM for installation and management of multiple
NonStop systems with identical hardware and software configurations.
In DSM/SCM you can create a clone group, consisting of a master system and one or
more clone systems. Any software configuration applied to the master is also applied
to all the clones in that master’s clone group. You can configure multiple clone groups,
each of which is maintained independent of the other groups.
Topics discussed in this section include:

Cloning Requirements on page 19-1

Creating a Clone Group on page 19-2

Applying a Software Configuration to a Clone Group on page 19-5

Creating a Noncloning Configuration on a Master or Clone on page 19-7

Removing a System From a Clone Group on page 19-8
Cloning Requirements
When deciding whether to manage multiple NonStop systems using cloning, consider:

All systems in a clone group must have the same processor type.

All systems must have the same, identically named volumes (primary and
alternate) for volumes on which DSM/SCM manages TSVs.

All clone system targets must have the same logical target name.

The super ID remote password and sufficient network security access are required
to remotely activate configurations on clone targets simultaneously using the
CLONE utility.
These are limitations to the DSM/SCM cloning feature:

Planner Interface activities for a clone group are indicated only for the master
system. For example, a new software revision created for a clone group appears
created only for the master, not the clones. This applies to most Planner Interface
displays and information, including applied configuration revisions.

Clone targets do not return a snapshot to the host system.