HP XP P9500 Storage - Manual (Page 133)

P-VOL_PSUS from/to S-VOL_SSUS(WE) T2: P-VOL_PSUS from/to S-VOL_SSUS(WE)
•
If you attempt the pairevtwait -s psus in P-VOL_PSUS & S-VOL_COPY state, then pairevtwait
will return immediately even if the S-VOL is still in S-VOL_COPY state because P-VOL is already
in P-VOL_PSUS state. If you want to wait the “S-VOL_SSUS” state, and then you must check
the status of the S-VOL becomes “S-VOL_PSUS” via the return code using pairvolchk -ss
command on S-VOL side or pairvolchk -ss -c command on P-VOL side. Or you can use
pairevtwait -ss ssus on both P-VOL and S-VOL, pairevtwait -ss ssus -l on S-VOL locally.
•
If you attempt the pairresync -restore or pairsplit -S in P-VOL_PSUS & S-VOL_COPY state, then
Business Copy will reject this command due to unable to perform. In this case, you need to
wait until the S-VO state becomes S-VOL_SSUS.
Table 26 Pair status versus Snapshot commands
Snapshot Command Pair Status
pairresync pairsplit paircreate
Resync -S option -C option -E option -split No -split
Rejected Acceptable Rejected Rejected Rejected Accepted 2 SMPL 1
Acceptable Rejected Rejected Rejected Rejected Acceptable COPY
RCPY 2
Acceptable Accepted 1 Accepted 4 Rejected Accepted*4 Acceptable PAIR 3
Accepted* 2 Accepted 1 Acceptable Rejected Acceptable Rejected PSUS
(PFUS) 4
Accepted* 2 Accepted 1 Rejected Acceptable Rejected Rejected PSUE 5
Accepted*: A command is accepted and issued; whether this command is executed or not depends
on the microcode version of the RAID storage system.
NOTE:
•
pairsplit (“simplex -S”) of Snapshot volume is returned without verification of state transition
that waits until SMPL state. In SMPL state, the volume that was S-VOL becomes R/W disable
and data is discarded.
•
In the “PSUE” state, Snapshot does not manage for differential data between the primary
volume and secondary volume.
Continuous Access Asynchronous, Continuous Access Synchronous, and Continuous
Access Journal volumes
Continuous Access Asynchronous/Continuous Access Journal provides paired volumes that use
asynchronous transfer to ensure the sequence of writing data between the primary volume and
secondary volume. The sequence of writing data between the primary and secondary volumes is
guaranteed within each consistency (CT) group (see
Figure 54 (page 134) ).
Continuous Access Synchronous, Business Copy, and Continuous Access Journal operations 133