Reconstructing the unit for Symmetrix/VMAX3

Reconstruction must already be available for TimeFinder/Clone at creation time.

Requirements

• Processing has been terminated on the units and clone units.

• The original pubsets and clone pubset have been exported if all original units of a pubset are to be reconstructed.

• No snap session exists for this original unit.

Initiating reconstruction

Copy the data to the original units:

/RESTORE-FROM-CLONE
   UNIT=*BY-PUBSET(PUBSET=<cat-id>) / *BY-VOLUME(<vsn>) / <unit MN> / 
        *BY-SYMMETRIX(SERIAL-NUMBER=<Symmetrix serialnumber>, 
                      LOGICAL-VOLUME=<logical volume number>)

When multiple clone sessions exist for the same original unit and all TimeFinder/Clone sessions are in the COPIED or SPLIT status, the command can be entered without any further operands.

When any TimeFinder/Clone session of the unit is in the RESTORED status, the command can only be executed for the clone unit of this session. Processing then depends on the RESTORED-SESSION operand:

• In the case of RESTORED-SESSION=*REJECT (default) the command is rejected.

• In the case of RESTORED-SESSION=*ACCEPT the command is executed. The clone session is switched from the SPLIT status to the RESTORED status.

Further sequence of operations

During the reconstruction process the clone pairs are in the REST-IN-PROG status. Console message NDE0060 indicates that reconstruction is complete and that the status is RESTORED. The clone units are accessible.

A TimeFinder/Clone pair in the RESTORED status cannot be used directly and should be canceled. This is particularly true when multiple clone pairs were created for one unit or a new clone pair is to be created with the unit.

A TimeFinder/Clone session in the RESTORED status can, however, also be placed in another status so that the unit and clone unit can continue to be used:

• With /RESTART-CLONE-SESSION ... RESTORED-SESSION=*SPLIT-ONLY the clone session is placed in the SPLIT status. The unit and clone unit can then be processed separately.

• With /RESTART-CLONE-SESSION ... RESTORED-SESSION=*ACCEPT the clone session is placed in the RECREATED or PRECOPY status. The unit and clone unit can then be activated again.

When the clone units of the split pubsets are renamed during activation, integrated renamining can also take place as part of RESTORE processing. Here the original name of the original pubser or any other name can be used. The general conditions described in section "Activating clone pairs" also apply here.

Asynchronous command execution

When the WAIT=*NO operand is specified in /RESTORE-FROM-CLONE, the command does not wait for the reconstruction process to terminate.

Synchronous command execution

When the WAIT=*UNTIL-SYNCHRONIZED operand is specified in /RESTART-CLONE-SESSION, the command waits for the reconstruction process to terminate, i.e. until the clone pair is in the RESTORED status. In interactive mode, this wait status can be aborted by hitting the K2 key.