Write-back caching for one or more volumes has been forcibly disabled by the storage array.
What Caused the Problem?
Write-back caching was disabled on one or more volumes. This problem can occur for the following reasons:
Battery Failure
Below minimum capacity
Discharged upon initial deployment or because of multiple cache backups in a row
The cache size memory of the controllers are different
Cache Reconfiguration
A Cache Data-Restore operation is in progress, which interrupted the normal write-back caching process
The space in the cache backup device is insufficient for storing the cache
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
When write-back caching is enabled when volumes are configured, write-back caching improves I/O performance. When write-back caching is disabled, I/O performance to the volume or group of volumes is seriously degraded.
The error triggers a critical event.
The controller is in the Notified state.
When write-back caching is enabled, the system transitions from Notified to Optimal after all volumes configured to use write-back caching are restored.
When the system transitions from Notified to Optimal, an information MEL event is logged to show that all normal write-back caching capabilities are restored for all volumes in the system.
While in the Notified state, a forced-disable of write-caching on any additional volumes has no effect, and no state transition occurs.
Recovery Steps
IMPORTANT: If the Recovery Guru Summary area reports other problems, fix them first, and then return to this procedure.
1 | Check the Summary area for a Battery Failure problem.
| ||||||||||||
2 | Perform the following steps:
| ||||||||||||
3 | Check the Recovery Guru Summary area for a Cache-Size Mismatch problem.
| ||||||||||||
4 | Perform the following steps:
| ||||||||||||
5 | Check the Recovery Guru Summary area for a Cache Reconfiguration problem.
| ||||||||||||
6 | Perform the following steps:
| ||||||||||||
7 | Check the Recovery Guru Summary area for a Cache Data-Restore in progress problem.
| ||||||||||||
8 | Perform the following steps:
| ||||||||||||
9 | Check the Recovery Guru Summary area for an Insufficient Storage Capacity in Cache Backup Device problem.
| ||||||||||||
10 | Perform the following steps:
|
| Target | NetAppESeries.StorageArray | ||
| Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0329_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_WRITEBACK_CACHING_DISABLED_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.StateId27EF047A91E9E03A37A3AB0E1EF38672" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId80DD46586396E8C17F2BD2008B5D33B9" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>329</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>