HP XP P9000 External Storage Access Manager User Guide (AV400-96607, January 2014)

Pair status values
When checking pair status in RWC, click File/Refresh to verify that the data is current.
In RWC, the pair status is shown in the [pair status in Remote Web Console/pair
status in RAID Manager] format. If the pair status name in RWC and the pair status name
in RAID Manager are the same, the pair status name in RAID Manager is not shown.
The following table lists ESAM pair status and whether the volumes can be accessed. The
accessibility to P-VOL or S-VOL depends on the pair status and VOL Access. You can see VOL
Access in the Pair Operation window or the Detailed Information dialog box.
Access
to
DescriptionVOL AccessPair Status
S-VOLP-VOLS-VOLP-VOLS-VOL-PVOL
Read/writeRead/writeThe volume is not assigned to an
ESAM pair.
BlankBlank
SMPLSMPL
Not accessibleRead/writeThe initial copy operation for this pair
is in progress. This pair is not yet
synchronized.
BlankAccess
(No Lock)
COPYCOPY
Read/write*Read/writeThe pair is synchronized. The system
reads and writes updates from the
BlankBlank
PAIRPAIR
host to the P-VOL and duplicates them
in the S-VOL.
Read/writeNot
Accessible
The I/O operation to S-VOL or the
swapping and suspending operation
Access (Lock)Blank
SSUS
was successful. If the pair status of the
S-VOL is SSWS, the S-VOL is
accessible. The most recent data is on
the S-VOL.
Read/writeNot
accessible
Pair failed to get the lock at swapping
and suspended command
BlankBlank
(pairsplit -RS command). Status
of the SSUS was forcibly changed. If
the pair status of the S-VOL is SSWS,
the S-VOL is accessible. Data on the
S-VOL might be old.
Not accessibleNot
accessible
After the status of the S-VOL was
changed to SSWS, you ran
Access (Lock)Blank
PSUS
pairsplit-RB command to
rollback. Suspend the pair and
resynchronize. After a rollback, do
not access the P-VOL or S-VOL until
resynchronization is finished. Data on
P-VOL might be old.
Not accessibleNot
accessible
After the status of the S-VOL was
forcibly changed to SSWS, you ran
BlankBlank
the pairsplit-RB command to
rollback. Suspend the pair and
resynchronize. After a rollback, do
not access the P-VOL or S-VOL until
resynchronization is finished. Data on
P-VOL might be old.
Not accessible.Read/write.
Read-only can
This ESAM pair is not synchronized
because the user has split the pair
BlankAccess
(Lock)
PSUSPSUS
(see
be set with(pairsplit-r command). The
P-VOL data is up-to-date.
“Suspend
types (PSUE
the option
pairsplit-r)
30 Working with volume pairs