Home
  •  

Monitor REC_ARVM_FAILED_MIRROR (413)

NetAppESeries.FailureID_0413_Monitor (UnitMonitor)

An Async Mirror is in failed state.

Knowledge Base article:

Failed Mirror

What Caused the Problem?

A mirrored pair within an asynchronous mirror group has failed. This problem can occur in the following situations:

The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

Recovery Steps

1

Refer to the Details area to identify the affected mirrored pair.

If...

Then...

You want to keep the mirrored pair relationship

Go to step 2.

You do NOT want to keep the mirrored pair relationship

Perform the following steps to remove the mirrored pair from the asynchronous mirror group:

a

On the

Storage and Copy Services

tab in the Array Management Window, highlight the affected mirror group.

b

In the right-hand pane, select the affected mirrored pair.

c

Select the

Copy Services > Mirroring > Asynchronous Mirroring > Mirrored Pair > Remove

menu option.

d

Follow the instructions in the dialog, and then click the

Remove

button.

e

Go to step 5.

2

Fix all error conditions associated with the primary volume or primary volume repository

and then return to this procedure.

If...

Then...

The error conditions WERE resolved

Perform the following steps to resume the asynchronous mirror group:

a

On the

Storage and Copy Services

tab in the Array Management Window, highlight the affected mirror group.

b

Select the

Copy Services > Mirroring > Asynchronous Mirroring > Mirror Group > Resume

menu option.

c

Follow the instructions in the dialog, and then click the

Yes

button.

d

Go to step 5.

The error conditions were NOT resolved

If the underlying primary volume or primary volume repository conditions cannot be resolved, the current mirrored pair relationship cannot be retained and the mirrored pair must be removed from the asynchronous mirror group.

If...

Then...

You want to reestablish the mirrored pair relationship using a new primary volume

Go to step 3.

You do NOT want to reestablish the mirrored pair relationship

Perform the following steps to remove the mirrored pair from the asynchronous mirror group:

a

On the

Storage and Copy Services

tab in the Array Management Window, highlight the affected mirror group.

b

In the right-hand pane, select the affected mirrored pair.

c

Select the

Copy Services > Mirroring > Asynchronous Mirroring > Mirrored Pair > Remove

menu option.

d

Follow the instructions in the dialog, and then click the

Remove

button.

e

Go to step 5.

3

Perform the following steps to remove the mirrored pair from the asynchronous mirror group:

a

On the

Storage and Copy Services

tab in the Array Management Window (AMW), highlight the affected mirror group.

b

In the right-hand pane, select the affected mirrored pair.

c

Select the

Copy Services > Mirroring > Asynchronous Mirroring > Mirrored Pair > Remove

menu option.

d

Follow the instructions in the dialog, and then click the

Remove

button.

4

Perform the following steps to reestablish the mirrored pair relationship using a new primary volume:

a

On the

Storage and Copy Services

tab in the AMW, highlight the affected asynchronous mirror group.

b

Select the

Copy Services > Mirroring > Asynchronous Mirroring > Mirror Group > Create Mirrored Pair

menu option.

c

Select or create a new primary volume for the mirrored pair.

d

Select a repository volume for the new primary volume.

e

After the wizard steps for creating a mirrored pair on this (local) storage array are complete, navigate to the AMW of the remote storage array and complete the mirrored pair using the secondary volume originally associated with the mirrored pair.

5

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:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_ARVM_FAILED_MIRROR
An Async Mirror is in failed state. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

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

  <Category>Custom</Category>

  <AlertSettings AlertMessage="NetAppESeries.REC_ARVM_FAILED_MIRROR_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="NetAppESeries.StateId51171F35424A10164AFB44B1942D392B" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppESeries.StateIdF2A9AAC895A898FCD49DBC80878C6329" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>413</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>