unable to perform. In this case, you need to wait until the S-VOL state
becomes SVOL_SSUS.
Table 6-6 Pair status versus Copy-on-Write Snapshot commands
Pair Status
Copy-on-Write Snapshot Command
paircreate pairsplit pairresync
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 Rejected Rejected Acceptable
3 PAIR Acceptable Accepted* 4 Rejected Accepted 4 Accepted 1 Acceptable
4 PSUS
(PFUS)
Rejected Acceptable Rejected Acceptable Accepted 1 Accepted* 2
5 PSUE Rejected Rejected Acceptable Rejected Accepted 1 Accepted* 2
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 Copy-on-Write 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, Copy-on-Write Snapshot does not manage for
differential data between the primary volume and secondary volume.
TrueCopy Async, TrueCopy, Universal Replicator, and global-active
device volumes
TrueCopy Async, Universal Replicator, and global-active device provide 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 6-9 TrueCopy Async
consistency groups on page 6-25).
6-24
Data replication operations with CCI
Command Control Interface User and Reference Guide
To Next Page
Loading...
