HP XP P9000 Business Continuity Manager User Guide (T5253-96086, November 2013)

Using CLI commands to obtain status
Business Continuity Manager obtains the types of copy pair statuses by using the commands
described in Table 17 (page 78).
Table 17 Types of copy pair statuses obtained by Business Continuity Manager
DescriptionPanel used to obtain the statusCommand used to obtain
status
No.
Obtains the copy pair status of a specific volume.Volume Query Information panelYKQRYDEV command1
Obtains the copy pair status for each copy pair based
on the copy pair status of the P-VOL and S-VOL.
Copy Group Pair Status panelYKQUERY command
YKEWAIT command
2
Meaning of copy pair status
Table 18 (page 78) explains the meanings of the copy pair statuses obtained by Business Continuity
Manager and their relationship with copy types. For the correspondence with copy pairs in storage
systems, see “Using the YKQRYDEV command to obtain the copy pair status of specified volumes”
(page 80).
Table 18 Meanings of the copy pair statuses obtained by Business Continuity Manager
Cnt Ac-J ZTCACnt Ac-S ZBC ZMeaningCopy pair
status
YesYesYesYesInitial status.SIMPLEX
This status exists before the copy
pair is placed in the DUPLEX
status or after the copy pair is
dissolved.
YesYesYesYesCopying processing from the
P-VOL to the S-VOL has
DUPLEX
completed, and the data is
synchronized between the P-VOL
and the S-VOL.
YesYesYesYesFull copy (initial copy) or
differential copy
PENDING
(resynchronization) is performed
from the P-VOL to the S-VOL in
order to reach the DUPLEX
status. This status occurs after
copy pair creation is requested
from the SIMPLEX or suspend
status. The DUPLEX status occurs
after the copy is completed.
YesYesYesYesData sychronization on the
P-VOL and S-VOl is temporarily
SUSPOP
stopped by the YKSUSPND
command.
YesYesYesN/AData synchronization on the
P-VOL and S-VOL is temporarily
SUSPCU
stopped due to an automatic
transition performed by the
control unit.
YesYesYesYesData synchronization on the
P-VOL and S-VOL is temporarily
SUSPER
stopped due to a hardware
failure or a similar cause.
78 Business Continuity Manager with replication products