HP XP7 Storage User Manual
Page 84
A pair can also be suspended by the primary or secondary system. Suspensions occur for the
following conditions:
•
When the primary system detects that the user has released the volume pair from the secondary
system
•
When the primary system detects an error condition related to the secondary system, S-VOL,
or a journal data operation
•
When the secondary system cannot execute DFW (DASD fast write (DFW)) to the S-VOL (if
DFW is specified)
•
When the primary system is unable to communicate with the secondary system
When a pair is suspended, the primary system stops updating the S-VOL. The primary and secondary
systems keep track of journal data discarded during suspension. Also, the primary system continues
accepting write I/Os for the P-VOL and keeps track of the P-VOL tracks which are updated while
the pair is suspended.
In addition to the Suspended status, an S-VOL also has a consistency status, which indicates its
update sequential consistency with respect to the other S-VOLs in the same group. The consistency
status is available only on the secondary system. See
for descriptions of
suspended S-VOL consistency statuses.
When a pair is suspended, the primary system generates sense information to notify the hosts.
The following provides suspension types and descriptions.
Table 7 Suspension types
Description
Applies to
Suspend type
The user suspended the pair from the primary or secondary
system using the S-VOL option.
P-VOL, S-VOL
Secondary data volume
by operator
The secondary system received a request from the primary
system to suspend the pair. The P-VOL suspend type is Primary
S-VOL
By MCU
data volume by Operator or Secondary data volume by
Operator.
The primary system detected an error condition on the
secondary system which caused the primary system to suspend
the pair. The S-VOL suspend type is By MCU.
P-VOL
By RCU
The primary system detected that S-VOL status changed to
unpaired because the user released the pair from the
P-VOL
Delete Pair to RCU
secondary system. The pair cannot be resynchronized because
the S-VOL is not suspended.
The primary system detected an error during communication
with the secondary system or an I/O error during update copy.
In this case, the S-VOL suspend type is usually By MCU.
P-VOL
Secondary Data Volume
Failure
The primary system could not find valid control information in
its nonvolatile memory during the IMPL procedure. This
P-VOL, S-VOL
MCU IMPL
condition occurs only if the primary system is completely
without power for more than 48 hours (e.g., power failure and
fully discharged backup batteries).
The pair was suspended before the initial copy operation was
complete. The data on the S-VOL is not identical to the data
on the P-VOL.
P-VOL, S-VOL
Initial Copy failed
The pair was suspended because it was highly likely that
journal data will overflow.
P-VOL, S-VOL
JNL Cache Overflow
The table below provides consistency statuses for suspended S-VOLs. These statuses indicate the
S-VOL’s sequential update consistency with respect to the other S-VOLs in the same group.
84
Monitoring the Cnt Ac-J Z system