HP XP7 Storage - Manual (Page 85)

Table 8 Suspended S-VOL consistency status
Description Consistency status
This Cnt Ac-J Z volume pair was suspended alone. Update sequence consistency
between this S-VOL and other S-VOLs in this mirror is not ensured. Volume
This S-VOL cannot be used for disaster recovery on the secondary system.
This status is indicated when:
This volume pair was suspended by a user-initiated suspend pair operation
with the Cnt Ac-J Z Suspend option set to Volume.
This volume pair was suspended due to a failure that did not affect the entire
mirror, and the Error Level pair option for this pair is set to Volume.
This Cnt Ac-J Z volume pair was suspended along with the other pairs in its
mirror. Update sequence consistency between this S-VOL and other S-VOLs in
this mirror is ensured. Mirror
This S-VOL can be used for disaster recovery on the secondary system (after
releasing the Cnt Ac-J Z volume pair from the secondary system).
This status is indicated when:
This volume pair was suspended by a user-initiated suspend pair operation
with the Cnt Ac-J Z Suspend option set to Mirror.
All volume pairs in this mirror were suspended due to a failure that affected
the entire mirror (not just one pair) (e.g., primary/secondary system
communication failure).
The volume pair was suspended due to a failure that did not affect the entire
mirror.
Suspension conditions on secondary systems
The following table provides conditions reported by the secondary system for suspending Continuous
Access Journal Z pairs.
Table 9 Suspension condition
Pairs to be suspended Detected by Suspension condition
All S-VOLs in the journals, or the affected
S-VOL. Remote system The secondary system could not copy the journal data
successfully due to a hardware failure or logic error.
All S-VOLs in the journal, or the affected
S-VOL, depending on the type of failure. Remote system The secondary system detected a logical error while
selecting the journal data to be restored.
Remote system The secondary system could not restore the journal
data due to a hardware failure, track condition, or
logical error.
See “Troubleshooting by suspension type ” (page 117) for more information.
The primary system stores the differential bitmap for each P-VOL in the system’s shared memory,
and the secondary system stores the differential bitmap for each S-VOL in its shared memory.
The tracks containing the following journal data is marked in the differential bitmap as modified
and will be copied during resynchronization:
•
Journal data created by the primary system but not yet sent to the secondary system. After
marking these P-VOL tracks as modified, the primary system discards these journal data.
•
Journal data sent to the secondary system but not acknowledged by the secondary system.
After marking these P-VOL tracks as modified, the primary system discards these journal data.
This ensures that journal data lost during transmission are identified and marked.
Monitoring pair activity, status, license capacity 85