Home
  •  

Monitor REC_MIRROR_DUAL_SECONDARY (52)

NetAppSANtricity.FailureID_0052_Monitor (UnitMonitor)

The failure type is Mirror Dual Secondary.

Knowledge Base article:

Dual Secondary Volume Conflict

What Caused the Problem?

The volumes in a mirror relationship are both in the secondary role. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

This problem happens when a role change from primary to secondary was attempted while there was a connection problem between the local and remote storage arrays. The user chose to force the role change which demoted the local primary volume's role to secondary without promoting the remote secondary volume's role to primary. The connection problem was subsequently corrected making the remote volume visible again. This resulted in both volumes being in a secondary role.

Recovery Steps

1

On the Storage and Copy Services tab in the Array Management Window, highlight the local secondary volume and view the mirror status of the volume in the Properties pane.

If...

Then...

The mirror status is synchronized

In its respective Array Management Window, highlight the secondary volume you wish to be primary and select the Copy Services > Mirroring > Synchronous Mirroring > Change > Role to Primary menu option.

Go to step 3.

The mirror status is not synchronized

Go to step 2.

2

Re-create the mirror relationship by performing the following steps:

a

Delete the mirror relationship from either storage array by highlighting either secondary volume in its respective Array Management Window and selecting the Copy Services > Mirroring > Synchronous Mirroring > Remove Mirror Relationship menu option.

Note: The mirror relationship for the remote volume will not be removed if there is a connection problem between the two storage arrays. If the mirror relationship remains on the remote volume after the above action, highlight that volume from its respective Array Management Window and select the Copy Services > Mirroring > Synchronous Mirroring > Remove Mirror Relationship menu option.

b

In its respective Array Management Window, highlight the volume you wish to be the primary volume and select the

Storage > Volume > Create > Synchronous Mirrored Pair

 menu option. Follow the instructions in the Create Remote Volume Mirror wizard to re-create the mirror relationship.

3

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.

Element properties:

TargetNetAppSANtricity.StorageArray
Parent MonitorNetAppSANtricity.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppSANtricity.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_MIRROR_DUAL_SECONDARY
The failure type is Mirror Dual Secondary. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppSANtricity.FailureID_0052_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="NetAppSANtricity.REC_MIRROR_DUAL_SECONDARY_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="NetAppSANtricity.StateId1C7681A1EA8987FFB0C576759DB862E4" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppSANtricity.StateIdD13382BDF9581CFA5D09EA6E22DBDB25" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>52</FailureID>

    <IntervalSeconds>361</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>