Split pair problems
The following table provides a list of split pair problem types.
|
Pair status/type |
Applies to |
Description |
Corrective action |
|---|---|---|---|
|
PSUE (pair suspended-error) / by RCU |
P-VOL |
The primary system detected an error condition at the secondary system, which caused the primary system to split the pair. The S-VOL split type is S-VOL Failure. |
Clear the error condition at the secondary system or S-VOL, and then resynchronize the pair from the primary system. If you need to access the S-VOL to clear the error conditions, release the pair from the secondary system. After you clear the error conditions from S-VOL, restart the pair. |
|
PSUE / S-VOL Failure |
P-VOL |
The primary system detected an error during communication with the secondary system, or detected an I/O error during update copy. In this case, the split type for the S-VOL is usually S-VOL Failure. |
|
|
PSUE (pair suspended-error)/ MCU IMPL |
P-VOL, S-VOL |
The primary system could not find valid control information in its nonvolatile memory during the IMPL procedure. This error occurs only if the system is without power for more than 48 hours (for example, power failure or fully discharged batteries). |
Resynchronize the pair from the primary system. An entire initial copy operation will be performed in response to the pairresync request. |
|
PSUE / Initial Copy Failed |
P-VOL, S-VOL |
The primary system split this pair during the initial copy operation. The data on the S-VOL is not identical to the data on the P-VOL. |
Release the pair from the primary system. Clear all error conditions on the primary system, P-VOL, secondary system, and S-VOL. Recreate the pair. |