Mirror Data Unsynchronized

What Caused the Problem?

The data on the secondary virtual disk is no longer synchronized with the primary virtual disk. This occurs when the primary virtual disk is unable to communicate with the secondary virtual disk, or if the Mirror Repository virtual disks have failed. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

All I/Os to the primary virtual disk will continue to be processed.
When the primary virtual disk detects that the secondary virtual disk can be contacted again, it will automatically initiate synchronization if you have selected automatic resynchronization. If you have configured the mirrored pair to resynchronize manually, use the Virtual Disk >> Remote Virtual Disk Mirroring >> Resume menu option to initiate synchronization.
You can increase the synchronization priority to allocate more processing time for the synchronization and less processing time for incoming I/Os or reduce the synchronization priority to allocate more processing time for incoming I/Os and less processing time for the synchronization.
To adjust the synchronization priority or resynchronization settings, highlight the primary virtual disk and select the Virtual Disk >> Remote Virtual Disk Mirroring >> Change >> Synchronization Settings menu option.

Recovery Steps

If there are errors present in the Recovery Guru Summary area, perform those recovery procedures before completing the steps in this procedure.

Verify your resynchronization settings by selecting the primary virtual disk, then selecting the Virtual Disk >> Properties menu option and viewing the Mirroring tab.

If...

Then...

Your resynchronization is set to Automatic

Go to step 3.

Your resynchronization is set to Manual

Try to start resynchronization by selecting the primary virtual disk and then selecting the Virtual Disk >> Remote Virtual Disk Mirroring >> Resume menu option.

If the mirror status changes to Synchronizing, go to step 7.

If the mirror status is still Unsynchronized, go to step 3.

Verify that the cables connecting this storage array to the switch are not loose, disconnected, or damaged.

If...	Then...
A damaged cable is detected	Replace the cable. Go to step 7.
A loose or disconnected cable is detected	Reconnect the cable. Go to step 7.
A loose, disconnected, or damaged cable is not detected	Go to step 4.

Check the switch the storage array is connected to for indications of a switch port, interface transceiver (GBIC or SFP), or other switch failure.

If...	Then...
There is a problem with the switch	Correct the problem. Go to step 7.
There is not a problem with the switch	Go to step 5.

If the fabric consists of multiple switches, verify that the cables connecting the switches are not loose, disconnected, or damaged.

If...	Then...
A damaged cable is detected	Replace the cable. Go to step 7.
A loose or disconnected cable is detected	Reconnect the cable. Go to step 7.
A loose, disconnected, or damaged cable is not detected	Go to step 6.

Verify that the cables connecting the switch to the remote storage array are not loose, disconnected, or damaged.

If...	Then...
A damaged cable is detected	Replace the cable. Go to step 7.
A loose or disconnected cable is detected	Reconnect the cable. Go to step 7.
A loose, disconnected, or damaged cable is not detected	Verify your cabling configuration. If you believe your configuration is valid but the problem still exists, contact your technical support representative.

Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative.