Restoring an original unit

Within a snap session, the original unit of a snap pair can be reconstructed by copying the data from the snap unit to the original unit. This reconstruction can be started for all snap pairs of a pubset or for individual snap pairs. Reconstruction results in all modifications which were made on the original unit after the snap unit was activated being discarded.

Requirements

• Processing on the original unit and snap unit has been terminated.

• Original pubsets and the snap pubset have been exported, provided all original units of a pubset are to be reconstructed.

Initiating reconstruction

Copy the data to the original units using the /RESTORE-FROM-SNAP command (see "RESTORE-FROM-SNAP Reconstructs an original from a snap unit"):

/RESTORE-FROM-SNAP 
   UNIT=*BY-PUBSET(PUBSET=<cat-id>) / *BY-VOLUME(<vsn>) / <unit MN> /...

Further sequence of operations

• After reconstruction snap sessions are in the COPY-ON-WRITE status and accessible.

• The snap pairs can still be used. Further reconstructions can also be started.

• For ETERNUS DX/AF, asynchronous reconstruction after command execution or synchronous reconstruction during command execution is possible (WAIT operand). The snap pair is in the REST-IN-PROG status during synchronous reconstruction. Waiting can be aborted in dialog mode by hitting the K2 key.

• The /STOP-SNAP-SESSION and /START-SNAP-SESSION commands are rejected with return code NDE1820 while reconstruction is being performed. They can only be executed successfully after reconstruction has been completed.

• Reconstruction is not possible if the original unit is also a clone unit.