QuickOPC/EC and SnapOPC+

SnapOPC+ snap sessions can be created on QuickOPC/EC original and clone units, i.e. snap units can be assigned to both the original and the clone unit of a clone pair. The snap unit and the original/clone unit then form a snap pair in the context of a snap session. The original/clone unit is then also the original unit of the snap pair.

A snap unit cannot become an QuickOPC/EC original unit.
/SWAP-CLONE-SESSION (EC only) can also be used together with SnapOPC+.

For replications with EC, access to the snap pair, consisting of a clone unit and a snap unit, via VSN or the pubset ID is usually not possible, as the clone unit cannot be read.

For replications with QuickOPC, access to the snap pair, consisting of a clone unit and a snap, unit via VSN or the pubset ID is possible, as the clone unit can be read (SPLIT status).

Prerequisites for addressing a snap pair with clone unit via the pubset ID or VSN:

• The original unit is attached.

• Additionally, for /START-SNAP-SESSION the following conditions must be met:

  • the clone pair has to be in SPLIT status

  • for replications with EC the clone pair must be synchronized in the event of active replication

SF pubsets can also be implicitly renamed with /START-SNAP-SESSION NEW-PUBSET=<new cat id>. The I/Os to the original unit can be suspended in ongoing operation using the HOLD-IO=*UNTIL-ACTIVATED operand to ensure consistent splitting.