HP XP P9500 Storage User Manual
Page 81
S-VOL access
P-VOL
access
Description
BCM status
RWC status
No
Read/Write
The pair is synchronized. Updates to the P-VOL are
duplicated on the S-VOL.
DUPLEX (02)
Duplex
SWAPPING
(04):
Read/Write
The pair has been suspended by the user and the P-VOL
and S-VOL are no longer synchronized.
SUSPOP (03),
SUSPOP (04),
SWAPPING (04),
SUSPER (07)
Suspend
Read/Write.
All others:
•
The primary and secondary systems keep track of journal
data discarded during the suspend operation.
Read Only if
•
In RWC, when the operation is performed on the primary
system, the status of both the P-VOL and S-VOL changes
to Suspend.
Mode=20 is
ON, otherwise
No.
•
In RWC, when the operation is performed on the
secondary system, the status of the S-VOL changes to
Suspend; the primary system detects this and changes
P-VOL status to Suspend.
BCM suspend statuses initiated by the user:
•
SUSPOP (03): The user performed a split operation on
the P-VOL. The update information is not reflected in
S-VOL.
•
SUSPOP (04): The user performed a split operation on
the S-VOL. The P-VOL can be updated, and the update
information is recorded as differential data.
•
SWAPPING (04): The pair was split in the REVERSE
direction (S-VOL to P-VOL).
•
SUSPER (07): The P-VOL was split by the system because
the user deleted the pair from the S-VOL side.
See also
Read Only if
Mode=20 is
Read/Write
The pair is suspended by the system due to an error; it is
not synchronized.
SUSPOP (05),
SUSPCU (06),
SUSPCU (08),
Suspend
ON, otherwise
No.
•
The primary and secondary systems keep track of journal
data discarded during the suspension operation.
SUSPER (09), SUSPER
(50)
•
The primary system keeps track of P-VOL tracks that are
updated while the pair is suspended.
•
In RWC, when a Cnt Ac-J Z suspension condition is
detected, the primary system changes P-VOL and S-VOL
status to Suspend. If the secondary system detects the
condition, it changes the S-VOL status to Suspend; the
primary system detects this and changes P-VOL status to
Suspend.
BCM suspend statuses initiated by the primary or secondary
system:
•
SUSPOP (05): The secondary system received a split
request from the primary system and split the pair.
•
SUSPCU (06): The primary system split the pair because
it detected an error in the secondary system.
•
SUSPCU (08): The pair was split because the primary
system detected an error during communication with the
secondary system or detected an I/O error during update
copy.
•
SUSPER (09): The pair was split 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
Monitoring pair activity and status
81