Repository utilization for a specific Async Mirror Group member has reached the full point (secondary repository).
What Caused the Problem?
All of the available repository capacity of a secondary mirrored volume has been used. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem occurs when synchronization of an asynchronous mirror group causes the repository of a secondary mirrored volume to become full before the synchronization operation completed. As a result, synchronization of the mirror group was suspended in order to preserve the recovery point for the mirrored pair.
If there is a "Synchronization Suspended" problem being reported in the Recovery Guru Summary area on the associated remote storage array (identified in the Details area), fix this problem first. Fixing this problem may resolve the "Synchronization Suspended" problem.
The Remaining unsynchronized data field in the Details area indicates the amount of data that was unsynchronized at the time the repository became full. This value may help you identify whether the repository capacity should be increased.
If the amount of unsynchronized data is high, the repository capacity should be evaluated to ensure that it is adequate for the amount of write activity on the primary mirrored volume.
If the amount of unsynchronized is low, this problem may be the result of a one-time, unusually high amount of write activity on the primary mirrored volume. Unless this problem begins to occur on a regular basis, the repository capacity is likely adequate for the typical amount of write activity.
You can fix this problem in two ways:
Preserve the recovery point by increasing the repository capacity of the secondary mirrored volume, and then resuming synchronization of the asynchronous mirror group. Increasing the repository capacity must be completed on the secondary side (this storage array) of the mirror group; however, resuming the mirror group must be completed on the primary side (remote storage array) of the mirror group.
Discard the recovery point by resuming synchronization of the asynchronous mirror group without expanding the repository of the secondary mirrored volume. Resuming the mirror group must be completed on the primary side (remote storage array) of the mirror group.
Recovery Steps
1 | Refer to the Details area to identify the affected secondary mirrored volume.
| ||||||||||||||
2 | Perform the following steps to increase the repository capacity of the affected secondary mirrored volume:
| ||||||||||||||
3 | Perform the following steps to resume the asynchronous mirror group:
| ||||||||||||||
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. |
| Target | NetAppSANtricity.StorageArray | ||
| Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0432_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_ARVM_SECONDARY_REPOSITORY_FULL_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.StateIdB917A7081D9F0975CD43D09FA07CA57B" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdF5837153F61E863873E8774E424C9268" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>432</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>