The following table lists and describes the statuses for pair volumes and indicates whether the volumes accept read/write operations from the host. You can check the pair status by using the raidcom get remote_copy_pair CCI command or the YKQUERY BCM command.
|
Status displayed by CCI |
Status displayed by BCM |
Description |
P-VOL access |
S-VOL access |
|---|---|---|---|---|
|
SMPL |
SIMPLEX |
The volume is not assigned to a pair. |
Read/Write |
Read/Write |
|
COPY* |
PENDING (1) |
The initial copy operation or differential copy operation (resync) for this pair is in progress. This pair is not yet synchronized. The status will change from PENDING to DUPLEX. |
Read/Write |
No |
|
PAIR |
DUPLEX (2) |
Copying processing from the P-VOL to the SVOL has completed, and the data is synchronized between the P-VOL and the SVOL. |
Read/Write |
Enable the TCMF SVOL Read function (6) mainframe system function. |
|
PSUS |
SUSPOP (03): The user suspended the pair from the P-VOL. SUSPOP (04): The user suspended the pair from the S-VOL. If the P-VOL is updated, it is recorded as differential data. SWAPPING (04): The user suspended the pair in the reverse direction (S-VOL to PVOL). SUSPOP (05): The secondary system received a split request from the primary system and suspended the pair. SUSPER (07): The user deleted the pair from the secondary system. The primary system detected this and suspended the P-VOL. SUSPOP (0A): The pair was suspended because the user issued PPRC's FREEZE command on the primary system. SUSPOP (10): Split MTIR pair was automatically created at the secondary site because the TCz pair was changed to PPRC multi-target configuration on the primary storage system. |
The pair has been split by the user. The pair is not synchronized. When you split the pair in the primary system,that system changes the status of the P-VOL and S-VOL to this status. In this status, updates to the S-VOL stop. The storage system keeps track of updates to the P-VOL in order to update the S-VOL when the pair is resynchronized. When you split the pair in the secondary system, that system changes the status of the S-VOL to this status. The primary system detects this and changes the P-VOL to this status. However, if there is no I/O from the host, the status of the P-VOL might remain Duplex. When you release the pair in the secondary system, that system changes the S-VOL status to Simplex. The primary system detects this and changes the P-VOL to this status. The pair must be released from the primary system in order to change P-VOL status to Simplex. When you build a PPRC multi-target configuration, the status of the primary and secondary volumes of the automatically created MTIR pair is Suspend. |
Read/Write |
Read only if SOM 20 is ON, otherwise No. |
|
PSUE |
SUSPCU (06) SUSPCU (08): The pair was suspended when the primary system detected an error during the communication with the secondary system,or detected an I/O error during update copy. SUSPER (09): The pair was suspended because the primary system detected volatilization of pair control information on memory when power was ON (IMPL). This error occurs when power-off status of the primary system continues beyond the backup time for the nonvolatile memory. SUSPER (50): The pair was suspended because data mismatch between P-VOL and SVOL was detected during the initial copy operation. The cause of the error is invalid track format. |
The primary or secondary system splits the pair due to an error. If the primary system cannot keep the pair synchronized for any reason, it changes the status of the P-VOL and S-VOL (if possible) to this status. The pair is not synchronized. CCI PSUE indicates that although the paired status is retained,updates to the S-VOL is stopped due to an error status. CCI PSUE is PSUS (SSUS) caused by an internal error. |
Read/Write Read only when the P-VOL fence level is Data. |
Read only if SOM 20 is ON, otherwise No. |
|
SSWS |
SWAPPING |
The pair status is retained. The P-VOL and the S-VOL of the pair is switched and then they are resynchronized (horctakeover). |
||
|
* When the pair status is COPY, neither cache nor shared memory can be added to or removed from the storage system. When either of these tasks is to be performed, wait until the pair status changes to PAIR, or split the pair, and then resynchronize when the cache or shared memory operation is completed. |
||||