PiT Group repository capacity utilized exceeded warning threshold.
What Caused the Problem?
The used repository capacity has exceeded the warning threshold level for a snapshot group or consistency group member volume. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
If you do not resolve this problem, this is the last warning you will receive before the repository becomes full.
If the repository becomes full, the repository failure policy determines what happens to the associated snapshot images. The failure policy can be set to either automatically purge the oldest snapshot images (recommended) or reject writes to the base volumes (keep snapshot images valid). To determine the failure policy, view the properties for the snapshot group, or the consistency group associated with the consistency group member volume.
You can resolve this problem in three ways (or through a combination of these three):
Increase the capacity of the repository.
Increase the threshold capacity warning level. Note that increasing the warning threshold will reduce the time you have to respond the next time you receive a threshold exceeded notification.
Manually delete the oldest associated snapshot images to free up capacity for the repository.
Enabling the Auto-Delete setting allows for the automatic deletion of snapshot images when the set limit is reached. Lowering the limit may help reduce repository capacity problems because a smaller number of snapshot images are kept in the snapshot group, or consistency group associated with the consistency group member volume. This will free up repository capacity to be used for future write operations.
Recovery Steps
1 | Identify the affected object in the Details area.
| ||||||||||||||||||||||||||||||||||||||||||||
2 |
| ||||||||||||||||||||||||||||||||||||||||||||
3 |
| ||||||||||||||||||||||||||||||||||||||||||||
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 |
<UnitMonitor ID="NetAppSANtricity.FailureID_0405_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_PIT_GROUP_REPOSITORY_OVER_THRESHOLD_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.StateId5BFAE36918599F2A35C42A14917C574" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdC1015F4BF792D5AA952ED4A3E9F9B4C9" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>405</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>