Split pair problems

PSUE/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 in the Resync Pairs window of HDvM - SN, or by the pairresync command of CCI.

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, re-create the pair.

PSUE/Secondary Volume 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.

Check the path status in the Remote Connections window of HDvM - SN, or by the raidcom get rcu command of CCI. If errors occurred on the path, clear the error conditions.

• Clear any error conditions 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, recreate the pair.

PSUE/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. Resume the initial copy operation.