HP 3PAR CIM API Programming Reference (OS 3.1.2 MU2) (QL226-97015, June 2013)

Table 110 CopyState/SyncState/ProgressStatus Transitions During Disaster Recovery (continued)
ProgressStatusSyncStateCopyState
Showrcopy Group Info
Role/SyncStatusSequence of Events
setrcopygroup restore
is issued on it
CompletedSynchronizedSynchronizedSecondary/SyncedState of Secondary
3PAR array after
setrcopygroup restore
is done
CompletedSynchronizedSynchronizedPrimary-Rev/SyncedState of Secondary
3PAR array if
setrcopygroup restore
failed
Failing BackSynchronizedSynchronizedSecondary-Rev/SyncedState of Primary 3PAR
array after
setrcopygroup recover
is issued on the
secondary 3PAR array
CompletedSynchronizedSynchronizedPrimary/SyncedState of Primary 3PAR
array if setrcopygroup
restore is done
CompletedSynchronizedSynchronizedSecondary-Rev/SyncedState of Primary 3PAR
array if setrcopygroup
restore failed
Synchronous Long Distance (SLD) Backup Link
For SLD configuration in which a primary 3PAR array copy group has 2 target groups, one to a
synchronous secondary 3PAR array and one to an asynchronous periodic secondary 3PAR array,
there exists also a backup link between the 2 secondary 3PAR array's (showrcopy Group Info
Status field shows “Backup”). Under normal operation this link between the remote replication
groups is not active (they only get activated during disaster recovery). However, the
StorageSynchronized associations will still be discovered between these 2 groups of volumes. In
CLI, they both show up as “Secondary” in the Group Info Role field, but for StorageSynchronized,
the volumes in the synchronous 3PAR array (the one with the FC link to the primary) will be picked
as the SystemElement and those in the asynchronous periodic 3PAR array will be picked as
SyncedElement. The reason for this is that if the primary 3PAR array goes down, by default the
synchronous 3PAR array will assume the primary role.
Under normal operation, this StorageSynchronized will have the following state/status values:
• CopyState – Initialized (2), the link to enable replication is established and source/replica
elements are associated, but the data flow has not started.
• SyncState – Initialized (2), the link to enable replication is established and source/replica
elements are associated, but the Copy engine has not started.
• ProgressStatus – Dormant (3), indicates data flow is inactive.
TPD_ReplicationEntity
Under certain circumstances after the remote replication link goes down, the remote StorageVolume
WWN cannot be calculated. When this happens, the provider will not be able to construct a valid
object path for the remote StorageVolume. Instead, SystemElement or the SyncedElement in question
will contain a reference to a ReplicationEntity, with an InstanceID of 3PAR:<remote volume
name>, and the UndiscoveredElement property will be set to either SystemElement or SyncedElement.
Similiar to remote StorageVolume, this ReplicationEntity cannot be retrieved via
EnumerateInstances/EnumerateInstanceNames.GetInstance.
132 CIM API SMI-S Support