Home
  •  

Monitor REC_DATABASE_RECOVERY_MODE (434)

NetAppESeries.FailureID_0434_Monitor (UnitMonitor)

The Stable Store Backup database is in recovery mode.

Knowledge Base article:

Storage Array in Recovery Mode

What Caused the Problem?

The storage array is in Recovery Mode. 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

Restoring the Configuration

Clearing Recovery Mode

 

Recovery Steps

If...

Then...

You intentionally or accidentally cleared your storage array configuration

If...

Then...

You want to restore the previous storage array configuration from backup

Go to

Procedure for Configuration Database Restore

.

You do NOT want to restore the previous storage array configuration from backup

Go to

Procedure for Clearing Recovery Mode

.

You did NOT intentionally or accidentally clear your configuration

OR

An internal fault caused an integrity error in the storage array configuration database

Do not continue with the remaining recovery steps and contact your Technical Support Representative.

Procedure for Configuration Database Restore

Important: This procedure is considered an advanced recovery procedure. It is recommended that it is performed under the guidance of a Technical Support Representative.

1

Perform the following steps to choose the OBB database and controller to be used for the restore operation:

a

Using the Recovery Guru Details area, identify the OBB database that has the highest

Generation number

, and whose status is Optimal, Stale, or Frozen. Do not choose an OBB database whose status is Unknown or Invalid.

Note: There will be two OBB databases listed in the Details area even if there is only one controller in the storage array.

b

If...

Then...

There are two usable OBB databases and the generation numbers are the SAME

You will perform the restore operation using Controller A, and will place Controller B offline in the next step.

Go to step 2.

There are two usable OBB databases and the generation numbers are DIFFERENT

You will perform the restore operation using the controller associated with the OBB database that has the

highest

generation number. You will place the opposite controller offline in the next step.

For example, if "Onboard (Controller A)" has the highest generation number, you will place Controller B offline in the next step.

Go to step 2.

There is only one usable OBB database and generation number (the other OBB database is Unknown or Invalid)

You will perform the restore operation using the controller that contains the usable OBB database.

Go to step 3.

2

Place the appropriate controller offline (identified in step 1):

a

On the

Hardware

tab in the Array Management Window (AMW), select the controller you are placing offline.

b

Select the

Hardware > Controller > Advanced > Place > Offline

menu option.

c

Complete the instructions in the dialog, then click the

Yes

button.

3

Open either the Command Line Interface (CLI), or the Script Editor from the Enterprise Management Window (EMW).

Note: The commands in this procedure are formatted as they are used in the CLI. Refer to the EMW online help for assistance with formatting these commands for the Script Editor.

4

Perform the following steps to attempt a full (all) configuration database restore:

a

Execute the following command:

load storageArray dbmDatabase sourceLocation=onboard contentType=all controller[x] 

Where x  is the controller that will be used for the restore operation (identified in step 1)

For example, load storageArray dbmDatabase sourceLocation=onboard contentType=all controller[a]

b

If...

Then...

The previous configuration was restored

Go to step 5.

Execution of the command was NOT successful because of any of the following:

  • Your storage array no longer appears to be responsive in the EMW

  • Your controllers are now in an Offline or Unresponsive state

  • Your controllers are now locked down

Do not continue with the remaining recovery steps and contact your Technical Support Representative.

5

Perform host application validation tests (if available) to ensure the configuration is complete (i.e. is acceptable for your storage array). Examples of validation tests are:

  • Complete a database consistency check

  • Complete a file system check

Note: Any validation tools should be used in read-only mode so that the validation tests do not change the volume data until configuration integrity is validated.

If...

Then...

The restored configuration IS complete (i.e. is acceptable for your storage array)

You can clear the Recovery Mode. Go to

Procedure for Clearing Recovery Mode

.

The restored configuration is NOT complete (i.e. is NOT acceptable for your storage array)

Your configuration may be able to be restored using the OBB from a different controller or from a host file; however, a configuration restored from these backups may not be complete. Therefore, you should contact your Technical Support Representative to help you with any further attempts to restore your configuration.

Procedure for Clearing Recovery Mode

 Caution: Risk of Data Loss. If you clear the Recovery Mode before restoring your configuration database, you will lose your previous configuration and the OBB will be reset to the current storage array configuration. If you want to restore the previous storage array configuration from backup, go to Procedure for Configuration Database Restore.

1

From the Array Management Window, select the

Monitor > Health > Clear Recovery Mode

menu option.

2

Follow the instructions in the dialog, and type "clear recovery mode" to confirm the operation.

3

Click the

OK

button.

4

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_DATABASE_RECOVERY_MODE
The Stable Store Backup database is in recovery mode. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0434_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_DATABASE_RECOVERY_MODE_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.StateId81FC7C82F8A848C38F8EAC8803624B44" MonitorTypeStateID="NoIssue" HealthState="Success"/>

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

  </OperationalStates>

  <Configuration>

    <FailureID>434</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>