A distinction is made between unit and clone unit.
The unit is generally in the READY status.
The following replication options are available for the unit:
For ETERNUS DX/AF the unit can be additively mirrored by RAID, SnapOPC+ or REC.
For Symmetrix the unit can be additively mirrored by RAID, TimeFinder or SRDF.
For VMAX3 the unit can be additively mirrored by RAID or SRDF.
The clone unit itself can also be mirrored:
For ETERNUS DX/AF the clone unit can be mirrored by RAID, SnapOPC+ or REC.
For Symmetrix/VMAX3 the clone unit can be mirrored using RAID or SRDF; further TimeFinder replication is also possible with certain constraints, but not for VMAX3.
The relevant status of the clone unit is determined by the status of the clone session.
The lifetime of a clone session extends from the time it is created (/START-CLONE-SESSION) to the time it is terminated (/STOP-CLONE-SESSION). During its lifetime, it can assume one of the following statuses:
CREATE-IN-PROG
TimeFinder only: the clone session is in the process of being created, i.e. the clone unit is being connected to the unit.
The clone unit is in the NOT-READY status.
CREATED
TimeFinder only: the clone session has been created, i.e the clone unit is connected to the unit but has not yet been activated. No data is (yet) copied in the background.
The clone unit is in the NOT-READY status.
COPY-ON-ACCESS
TimeFinder only: the clone session has been activated; the unit and clone unit can be processed separately. Data is copied to the clone unit if and only if this data is accessed in write mode on the unit or in read mode on the clone unit. In other words the clone unit can only be used within the clone session.
The clone unit is in the READY status.
COPY-IN-PROG
TimeFinder only: the clone session has been activated; the unit and clone unit can be processed separately. All the data on the unit is copied to the clone unit in the background.
The clone unit is in the READY status.
COPIED
TimeFinder only: the clone session has been activated; the unit and clone unit are synchronous and can be processed separately. The clone unit is a complete copy of the unit.
The clone unit is in the READY status.
REST-IN-PROG
For QuickOPC: the unit is reconstructed from the clone unit; the modified data is copied in the background from the clone unit to the unit. The unit must not be used.
For TimeFinder: the unit is reconstructed from the clone unit; the modified data is copied in the background from the clone unit to the unit.
The clone unit is in the READY status. The unit is also in the READY status (REST-IN-PROG must be regarded as being the same as COPY-IN-PROG, just in the opposite direction).
RESTORED
TimeFinder only: the unit has been fully restored from the clone unit. This status has the effect of a lock for the restored data on the unit which ensures that the data which has been restored is not destroyed again, i.e. in the normal case the clone session can only be terminated. To enable the clone session still to be used, it must first be placed in the SPLIT status.
The clone unit is in the READY status.
RECREATED
TimeFinder only: the clone session was restarted with a clone pair with which a clone session already exists. The clone unit is therefore still connected to the unit, but has not yet been activated and has not yet been updated with the unit’s data. It can be activated. The copying of modified data from the unit to the clone unit is only started when activating it.
The clone unit is in the NOT-READY status.
SPLIT
For QuickOPC and EC: the clone session is split after the unit and clone unit have been full synchronized. The unit and clone unit operate separately. The clone session can be continued.
For QuickOPC and EC: The /RESTORE-FROM-CLONE command was executed successfully. The clone unit is in the READY status.
For TimeFinder: the unit has been completely restored from the clone unit but not locked to prevent further actions, i.e. the clone session can continue (e.g. a /RESTART-CLONE-SESSION is once more possible).
SYNCHRONIZING
For QuickOPC: the clone session has been newly configured or updated, i.e. the clone unit is connected to the unit and is active. The unit is copied to the clone unit in the background. This status was achieved after configuration (start), or after a restart.
The clone unit is in the READY status.
For EC: the clone session has been configured or newly created, i.e the clone unit is connected to the unit but has not yet been activated. The unit is copied to the clone unit in the background.
The clone unit is in the NOT-READY status.
SYNCHRONIZED
EC only: the clone session has been created but not activated. After the completed copy procedure the clone pair is synchronous. This status was achieved after configuration (start), or after a restart.
The clone unit is in the NOT-READY status.
PRECOPY
TimeFinder only: the clone session has been created or restarted, i.e. the clone unit is connected to the unit, but has not yet been activated. The unit is copied to the clone unit in the background or the unit and clone unit are already synchronous.
The clone unit is in the NOT-READY status.
TERM-IN-PROG
The clone session is in the process of being terminated.
The clone unit is in the READY status.
FAILED
The clone session has become unusable. It can only be terminated using /STOP-CLONE-SESSION.
The clone unit is in the NOT-READY status.