Dual Primary Virtual Disk Conflict

What Caused the Problem?

A role change from secondary to primary was attempted while there was a connection problem between the local and remote storage arrays. The user chose to force the role change which promoted the local secondary virtual disk's role to primary without demoting the remote primary virtual disk's role to secondary. The connection problem was subsequently corrected making the remote virtual disk visible again. This resulted in both virtual disks being in a primary role. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Recovery Steps

1 Recreate the mirror relationship by performing the following steps:
a Delete the mirror relationship from either storage array by highlighting either primary virtual disk in its respective Array Management Window and selecting the Virtual Disk >> Remote Virtual Disk Mirroring >> Remove Mirror Relationship menu option.

Note: The mirror relationship for the remote virtual disk will not be removed if there is a connection problem between the two storage arrays. If the mirror relationship remains on the remote virtual disk after the above action, highlight that virtual disk from its respective Array Management Window and select the Virtual Disk >> Remote Virtual Disk Mirroring >> Remove Mirror Relationship menu option.
b In its respective Array Management Window, highlight the virtual disk you wish to be the primary virtual disk and select the Virtual Disk >> Remote Virtual Disk Mirroring >> Create menu option. Follow the instructions in the Create Remote Virtual Disk Mirror wizard to re-create the mirror relationship.
2 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.