Continuous Copy

The “Continuous Copy” function ensures the parallel availability of the additional local clone replication in both storage systems of a Storage Cluster.

For an automatic or manual switch between both storage systems the additional local clone replication is adopted. This means that local clones are available anytime. They can be managed anytime, independent of the currently active storage system. This makes the clone replication fully transparent for the user.

Continuous Copy is based on QuickOPC and is automatically activated if a replication on a clone unit in the same Storage Cluster is created with QuickOPC.

The automatic deployment of additional replications in the Storage Cluster can only be ensured with Continuous Copy. It is therefore recommended to realize local clone replication in Storage Clusters with QuickOPC.

The user has to ensure that no QuickOPC  clone pair actions are performed during a manual failover or failback.
They might be rejected during the failover/failback due to internal processes.

When using the “Continuous Copy” function with CLONE-TYPE=*COPY, some general conditions must be observed for the storage cluster status and phase:

• Existing clone replications can be transparently managed, even after failure of a storage system, with /RESTART-CLONE-SESSION and /RESTORE-FROM-CLONE.

• Creating new clone replications with /START-CLONE-SESSION and terminating existing clone replications with /STOP-CLONE-SESSION is only possible within a storage cluster in PHASE = NORMAL, FAILBACK-READY and COPYING, i.e. only if both the primary and secondary storage system are available. Actions during failure of the primary or secondary storage system would lead to inconsistencies in the Continuous Copy configuration of the ETERNUS DX/AF and are therefore rejected.