Pair status definitions

The following table lists and describes the Universal Replicator pair status names. The Storage Navigator pair status name and the RAID Manager pair status name are both displayed in the Storage Navigator Status column. When the names are the same, the RAID Manager pair status name is not displayed.

When checking the status of a pair, click File/Refresh to make sure the most recent information is displayed.

SN status

RAID Manager status

Description

P-VOL access

S-VOL access

(Unpaired- no SN status)

SMPL

The volume is not assigned to a pair and is not in a journal.

Read/Write

Read/Write

COPY

COPY

The initial copy operation is in progress.

Read/Write

Read Only

PAIR

PAIR

The pair is synchronized. Updates to the P-VOL are duplicated on the S-VOL.

Read/Write

Read Only

SN displays this status as PAIR

PFUL

If data in the journal volume exceeds the threshold (80 %), pair status changes to PFUL. The pair is not suspended; the copy operation continues.

If the Inflow Control journal option is set to Yes when status changes to PFUL, host I/O is delayed because update I/O to the journal volume is delayed.

Read/Write

Read Only

PSUS

PSUS SSUS

The pair has been split by the user and the P-VOL and S-VOL are no longer synchronized.

  • The primary and secondary systems keep track of journal data discarded during the split operation.

  • When the operation is performed on the primary system, the status of both the P-VOL and S-VOL changes to PSUS.

  • When the operation is performed on the secondary system, the status of the S-VOL changes to PSUS; the primary system detects this and changes P-VOL status to PSUS.

SSUS is the S-VOL’s split status name.

See also PSUS types and behaviors.

Read/Write

Read Only, but if you select Enable for Secondary Volume Write option then split pair from primary site, it is Read/Write (default is Disable).

PSUE

PSUE

The pair is suspended by the system due to an error; it is not synchronized.

  • The primary and secondary systems keep track of journal data discarded during the suspension operation.

  • The primary system keeps track of P-VOL tracks that are updated while the pair is suspended.

  • When a Universal Replicator suspension condition is detected, the primary system changes P-VOL and S-VOL status to PSUE. If the secondary system detects the condition, it changes the S-VOL status to PSUE; the primary system detects this and changes P-VOL status to PSUE.

See also PSUS types and behaviors.

SN: Read/Write RAID Manager: Read/Write if no error in P-VOL

Read Only

Suspending

(No equivalent RAID Manager status)

The pair is not synchronized and in transition from the PAIR or COPY status to PSUS or PSUE status.

Read/Write

Read Only

Deleting (releasing)

(No equivalent RAID Manager status)

The pair relationship is being deleted. When the operation completes, the status changes to unpaired.

Read/Write

Read Only

HOLD

(No equivalent RAID Manager status)

Displayed for a UR delta resync pair in the 3DC multi-target configuration using delta resync. This status indicates that all of the conditions for delta resync are met and the pairs are waiting for delta resync. When used with GAD, this status indicates that delta resync can be executed. If the UR P-VOL status is HOLD, the updated TC or GAD S-VOL data is stored in the master journal volume.

Operations allowed on pairs in HOLD status:

  • Delta resync

  • Delete pair

  • Change pair options

Read/Write1

Read/Write2

HOLDING3

(No equivalent RAID Manager status)

Displayed for a UR delta resync pair in the 3DC multi-target configuration using delta resync. This status indicates that the pair status is changing to HOLD so that the delta resync pair can be created. When a pair status is HOLDING, no differential data for the delta resync operation exists in the storage system, and it depends on the user whether to perform the delta resync operation.

Operations allowed on pairs in HOLDING status:

  • Delta resync

  • Delete pair

  • Change pair options

If the delta resync operation is run on a pair in HOLDING status, the operation might fail. If delta resync fails and you specified Entire Copy for the Delta Resync Failure option (Edit Mirror Options window), all of the differential data is copied to the S-VOL.

When used with GAD, delta resync is being prepared for execution. Delta resync fails if the status is HOLDING. When used with GAD, specifying Entire Copy for the Delta Resync Failure option (Edit Mirror Options window) is invalid. If delta resync fails, resynchronize the UR pair.

Read/Write1

N/A

HLDE

(No equivalent RAID Manager status)

Displayed for a UR delta resync pair in the delta resync configuration.

  • An error occurred on a pair in the HOLD status.

  • When the P-VOL status is HLDE, the updated S-VOL data of TC or GAD pairs is not stored in the master journal volume.

Operations allowed on pairs in HLDE status:

  • Recover pair status to HOLD

  • Delete pair

  • Change pair options

Read/Write1

N/A

(No equivalent SN status)

PFUS

This status results when the journal volume becomes full and suspends. Pair status changes from COPY, PAIR or PFUL to PFUS. The UR pair is suspended and the copy operation stops. Make sure to review configuration of the remote path and journal volume.

  • If a Dynamic Provisioning virtual volume (DP-VOL) is used as the UR S-VOL, and the capacity of a pool-VOL is nearly full, the UR status becomes PFUS and the pair is suspended.

  • If the journal option Inflow Control is set to Yes when status changes to PFUS, the pair is not suspended for the time set in the Data Overflow Watch field, even when the journal volume becomes full. During the time it takes for the journal data area to clear, the response to host I/O is delayed.

See Changing options used by journals for more information on Data Overflow Watch.

Read/Write

Read Only, but if you select Enable for Secondary Volume Write option then split pair from primary site, it is Read/Write (default is Disable).

(No equivalent SN status)

SSWS

After the horctakeover or pairsplit -RS command, SSWS is the status of the S-VOL. With this status, data can be written to the S-VOL. The host can write data to an S-VOL whose status is SSWS on the intermediate site or secondary site during the failure recovery.

Read Only

Read/Write

  1. The access conditions to the UR P-VOL depend on the status of the TC or GAD pair that shares volumes with UR.

  1. In the 3DC multi-target configuration using delta resync, two mirrors are used. The access conditions to this S-VOL depend on the status of the mirror whose status is not HOLD.

  1. HOLDING indicates either that differential data used for a delta resync operation does not exist or that the system cannot judge whether the delta resync can be performed without the differential data.

When differential data does not exist in the secondary TC or GAD site, even after the S-VOL is updated, the differential data might be discarded due to the one of the following reasons:

- The cache or shared memory was added to or removed from the system during maintenance work.

- The system was powered off during maintenance work.

- The UR, TC, or GAD pair was suspended and then resynchronized.

- A disaster or failure occurred in a TC or GAD secondary site, and volumes cannot be accessed.

After the system is back to normal, differential data is stored again in the TC S-VOL if you update the data in the primary site.

The delta resync operation can be executed without differential data if the primary site has not received a data update or if the data in the TC or GAD S-VOL and the UR S-VOL is the same.

Even if the delta resync operation without differential data is executable, the pair status changes to HOLD even when the differential data exists if the conditions for discarding the differential data are satisfied. To change the status of the pair to HOLD, update the data in the primary storage system after the recovery from the condition of the differential data discarding.

If you cannot connect to the secondary site of TC or GAD due to failures or disasters, the transition from HOLDING to HOLD is not performed correctly. When used with GAD, keep updating I/O from the server to GAD P-VOL or S-VOL for about two minutes.