Home
  •  

Monitor REC_CACHE_DATA_LOSS (389)

NetAppESeries.FailureID_0389_Monitor (UnitMonitor)

Data in cache has been lost after a power cycle or reset. The controller was unable to recover cache data and write it to the affected volume(s).

Knowledge Base article:

Cache Data Loss

What Caused the Problem?

Cache data on the storage array could not be recovered. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Notes

 Caution: Loss of data access. Data on the affected volumes will not be accessible unless you can restore the data from a mirrored volume or another backup medium, or if the applications using those volumes have their own mechanisms for recovering from corrupted data.

Recovery Steps

1

If...

Then...

You want to restore that data from the secondary volume

Go to step 2.

You want to restore your data using another backup tool

Perform the following steps:

a

Restore the data on the affected volumes from a backup medium.

b

Place volumes online by using the

Storage > Volume > Advanced > Place Volumes Online

menu option in the Array Management Window.

c

Go to step 12.

2

Review the Recovery Guru Details area to identify the affected volume.

Note: The affected volume is currently the primary volume in the mirrored relationship.

3

On the

Storage and Copy Services

tab in the Array Management Window (AMW), identify the secondary volume and associated remote storage array that completes the mirrored pair with the primary volume.

4

Since the primary volume is offline, the mirrored pair must be broken from the secondary volume. To do this, open the AMW for the secondary volume.

5

Perform the following steps to break the mirror relationship:

a

On the

Storage and Copy Services

tab in the AMW, highlight the secondary volume.

b

Select the

Copy Services > Mirroring > Synchronous Mirroring > Remove Mirror Relationship

menu option.

c

From the table, select the mirrored volume pair that includes the primary and secondary volumes identified above. 

d

Click the

Remove

button.

e

Follow the instructions in the dialog, then click the

Yes

button.

6

The primary volume can now be placed online. To do this, open the AMW for the primary volume (this storage array) and perform the following steps:

a

On the

Storage and Copy Services

tab in the AMW, highlight the primary volume.

b

Select the

Storage > Volume > Advanced > Place Volumes Online

menu option.

c

Follow the instructions in the dialog, then click the

OK

button.

7

Perform the following steps to break the mirror relationship between from the primary volume:

a

On the

Storage and Copy Services

tab in the AMW, highlight the primary volume.

b

Select the

Copy Services > Mirroring > Synchronous Mirroring > Remove Mirror Relationship

menu option.

c

From the table, select the mirrored volume pair that includes the primary and secondary volumes identified above. 

d

Click the

Remove

button.

e

Follow the instructions in the dialog, then click the

Yes

button.

8

In order to completely synchronize the two volumes and restore the data, the current primary volume (on this storage array) must be reestablished in the mirror as the secondary volume, and the current secondary volume must be reestablished as the primary volume. To do this, open the AMW for the storage array that is the local storage array for the secondary volume identified in step 3.

Note: Ensure that both controllers in the storage array are online before continuing with the remaining steps of the recovery procedure.

9

Perform the following steps to reestablish the mirror relationship between the two volumes:

a

On the

Storage and Copy Services

tab in the AMW, highlight the primary volume. This should be the former secondary volume identified in step 3.

b

Select the

Storage > Volume > Copy Services > Create Synchronous Mirrored Pair

menu option.

c

Select the storage array that contains the secondary volume. This should be the local storage array for the former primary volume identified in step 2.

d

Click the

Next

button.

e

Select the secondary volume. This should be the former primary volume identified in step 2.

f

Click the

Next

button.

g

Select a write mode.

h

Click the

Next

button.

i

Select a synchronization setting.

j

Click the

Next

button.

k

Follow the instructions in the dialog, and type "yes" to confirm the operation.

l

Click

Finish

.

10

After synchronization has completed, highlight the new primary volume on the

Storage and Copy Services

tab in the AMW.

11

Select the

Copy Services > Mirroring > Synchronous Mirroring > Change > Role to Secondary

menu option.

12

After the process has completed, 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_CACHE_DATA_LOSS
Data in cache has been lost after a power cycle or reset. The controller was unable to recover cache data and write it to the affected volume(s). Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0389_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_CACHE_DATA_LOSS_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.StateIdF2A5295327972BBA8F933646312FA80E" MonitorTypeStateID="NoIssue" HealthState="Success"/>

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

  </OperationalStates>

  <Configuration>

    <FailureID>389</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>