P-VOL
Status
Pairing Status Primary Secondary
PSUE
(Error)
"PSUS" status due to an internal failure. The
differences of the updated data for the Copy-
on-Write Snapshot volume are not controlled.
R/W enabled
2
R/W disable
Notes:
1. V-VOL unmapped to the S-VOL of a Copy-on-Write Snapshot will reply to a SCSI
Inquiry, but Reading and/or Writing is not allowed.
2. Reading and writing are enabled, as long as no failure occurs in the primary volume.
Pair status relationship to Copy-on-Write Snapshot commands
Table 6-11 Pair status relationship to Copy-on-Write Snapshot commands on
page 6-36 applies to a Copy-on-Write Snapshot context. It explains 1) what
a pair status can be prior to any CCI command execution, 2) what the result
will be after giving a CCI command, and 3) what the pair status can be if the
CCI command is Accepted.
Table 6-11 Pair status relationship to Copy-on-Write Snapshot commands
-
Copy-on-Write Snapshot Command
paircreate pairsplit pairresync
Pair Status No -split -split -E option -C option -S option Resync
1 SMPL Accepted 2 Rejected Rejected Rejected Acceptable Rejected
2 COPY
RCPY
Acceptable Rejected Rejected Accepted* Accepted 1 Acceptable
3 PAIR Acceptable Accepted*4 Rejected Accepted* Accepted 1 Acceptable
4 PSUS
(PFUS)
Rejected Acceptable Rejected Accepted* Accepted 1 Accepted*2
5 PSUE Rejected Rejected Rejected Rejected Accepted 1 Accepted*2
*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 -S of a Copy-on-Write Snapshot volume is returned without
verification of the state transition that waits until SMPL state. In a SMPL
state, note that the volume that was an S-VOL becomes R/W
disabled and data is discarded.
• In the "PSUE" state, Copy-on-Write Snapshot does not manage
differential data between the primary volume and secondary volume.
6-36
Data replication operations with CCI
Command Control Interface User and Reference Guide
To Next Page
Loading...
Need help?
General