S-VOL consistency refers to whether the data in the S-VOL is identical to the data in the P-VOL. This depends on the fence level setting, which determines whether data is copied to the P-VOL if an error occurs during an update to the S-VOL.
The following table shows S-VOL consistency information based on pair status and the P-VOL fence level setting.
| S-VOL status (CCI) | S-VOL status (BCM) | Split type | Fence level (CCI) | Consistency of S-VOL |
|---|---|---|---|---|
| SMPL | SIMPLEX | - | data, status, never | Not consistent. The S-VOL does not belong to a pair. Even if you have created a pair using this volume, if the pair status is still SMPL, you must regard its data as not consistent with the P-VOL. |
| COPY | PENDING | - | data, status, never | Not consistent. The S-VOL is not synchronized because not all tracks have been copied from the P-VOL yet. This S-VOL must be initialized (or copied from the P-VOL at a later time). |
| PAIR | DUPLEX | - | data, status | Consistent. The S-VOL is synchronized with its P-VOL. |
| never | Needs to be analyzed. The S-VOL requires further analysis to determine its level of consistency. | |||
| PSUE | SUSPER(50) | Initial copy failed | data, status, never | Not consistent. The S-VOL is not synchronized because not all tracks have been copied from the P-VOL yet. The S-VOL must be initialized (or copied from the P-VOL at a later time). |
| PSUS | SUSPOP(04) | Secondary Volume by Operator | data, status, never | Suspect. The S-VOL is not synchronized with its P-VOL if any write I/Os were issued to the P-VOL after the pair was split. Delete the pair, and then run the raidcom add remote_copy_pair command without the -copy_mode none option to re-create the pair. If you are sure that the data on the P-VOL did not change, run the command with the -copy_mode none option to recreate the pair. |
| PSUE | SUSPOP/SUSPER (all other types) | All other types | data | Consistent. The S-VOL is synchronized with its P-VOL. |
| status, never | Suspect. The S-VOL is not synchronized with its P-VOL if any write I/Os were issued to the P-VOL after the pair was suspended. Restore the consistency of the S-VOL and update it,if required. The time of suspension indicated on the Last Update Time field of the Detailed Information dialog box(MCU SVP time) will help to determine the last time the S-VOL was updated. | |||
|
Legend: Data: Data in the secondary volume Status: Status of the secondary volume For pairs whose P-VOL fence level is set to "never" in the raidcom get remote_copy_pair command, further analysis is required to determine the S-VOL consistency. This can be determined by using sense information transferred by host failover, or by comparing the contents of the S-VOL with other files that are confirmed to be consistent (for example, database log files). The S-VOLs should be recovered using the files that are confirmed to be consistent. Note: Actual data recovery must be done using recovery point data in the database operation log. |
||||