PiT purged to free PiT group repository capacity.
What Caused the Problem?
A snapshot image was purged. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
Typically, a snapshot image is purged because the repository for the associated snapshot group is full and the policy for the group is to purge the oldest snapshot images. This allows the repository to free up capacity that can be used for future write operations.
Although deleting the purged snapshot image will fix this problem, it is important that the repository for the snapshot group has enough capacity for the number of snapshot images allowed. If there is also a "Snapshot Group Repository - Full" problem reported in the Recovery Guru Summary area, fix that problem to avoid reoccurrence of this problem.
When a snapshot image is purged, the following occurs:
It is no longer usable and must be deleted
It cannot be used for a rollback operation
It cannot be used to create a snapshot volume
All existing snapshot volumes associated with the snapshot image will be disabled
Enabling the Auto-Delete setting for the snapshot group allows for the automatic deletion of snapshot images from the group 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. This will free up repository capacity to be used for future write operations and will prevent snapshot images from being purged.
Recovery Steps
1 | On the Storage and Copy Services tab in the Array Management Window, highlight the affected snapshot image identified in the Details area. |
2 | Select the Copy Services > Snapshot Image > Delete menu option. |
3 | Follow the instructions in the dialog, and type "yes" to confirm the operation. |
4 | Click the Delete button. |
5 | 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 | 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_0411_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_PIT_PURGED_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.StateIdFAF44A06D983595463D81E54E4AE57BE" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdED84B0FD42E6A26EC7A7D0013F30682" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>411</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>