At the start of a clone session, the /START-CLONE-SESSION command creates a clone pair. Before the command is executed, the clone units must be free units, i.e. they may not belong to another clone pair.
Clone pairs that were created with EC or TimeFinder/Clone are in NOT-READY status after the command execution and have to be activated.
Clone pairs created with QuickOPC will be activated automatically after their creation. The clone units are in the READY status. Considerations on a synchronization point and renaming should therefore be taken into account already at the creation of the clone pairs (see the respective descriptions in section "Activating clone pairs").
The clone pairs can be created during normal processing. The current VSN and the formatting of the units are irrelevant.
A distinction must be made according to whether clone units are created for the entire pubset or only for one unit or several specific units.
Entire pubset
A unit which can also be used as a clone unit must also exist for each unit of the pubset.
Create clone pairs for all units of a pubset:
/START-CLONE-SESSION UNIT=*BY-PUBSET(PUBSET=<cat-id>),CLONE-UNIT=<clone units MN list>
The sequence of the clone units is determined by the VSN of the pubset’s volumes. If, for example, the pubset ID or volume set ID is CLN, the first clone unit is assigned to the VSN CLN.00, the second to the VSN CLN.01, and so forth.
Individual units
Create a clone pair with one unit and one clone unit:
/START-CLONE-SESSION UNIT=<unit MN>,CLONE-UNIT=<clone unit MN>
Further sequence of operations
The copy process is initiated.
For TimeFinder/Clone, console message NDE0060 indicates that the clone pair has been created and, if required, when the copy process was terminated that the CREATED status was assumed.
The clone session process can always be restarted.
A clone session can be terminated without the clone unit ever being activated. In this case the clone unit may possibly not contain any consistent data. In the case of EC the session can be terminated only if the clone unit is in the SYNCHRONIZED or SPLIT status.
Repeated entry of the /START-CLONE-SESSION command enables multiple clone sessions (multiple clone pairs) to be generated for a unit. For Symmetrix/VMAX3 this is possible only provided no earlier snap or clone session in the RESTORED status exists. If a snap or clone session in the RESTORED status does exist, it must be terminated before a new clone session is generated (/STOP-SNAP-SESSION or /STOP-CLONE-SESSION).