Key Monitoring Scenarios
Applies To: Operations Manager 2007
After you import the management pack, wait at least one hour for the management pack to gather data, monitoring data will begin to appear in the Operations Manager 2007 Operations console. In the Monitoring pane, the System Center Data Protection Manager 2010 (DPM) node and child nodes contain views for DPM.
Computer Attributes
The DPM Management Pack collects the following attribute for computers:
- Microsoft System Center Data Protection Manager
DPM Server Groups
The DPM Management Pack includes the following computer group:
- Microsoft System Center Data Protection Manager 2010 Servers
Alert Rule Group
The rules in the Alert rule group are identical to all the System Center Data Protection Manager (DPM) alerts that might require a user action, so that an administrator can monitor data protection for multiple DPM servers from the Microsoft System Center Operations Manager 2007 Operations console. The Management Pack filters out alerts that do not require user action.
The severity of the alert in DPM determines the severity of the mirrored alert in the Operations Manager Operations console.
Warning alerts in DPM are warning alerts in Operations Manager.
Error alerts in DPM are critical errors in Operations Manager.
Information alerts in DPM are information alerts in Operations Manager.
An inactive alert in DPM, the alert becomes an inactive alert in Operations Manager and is not displayed.
The product knowledge can be found in the Alert Details of the Operations Manager Operations console. This product provides comprehensive information about each alert, including a summary of the problem, possible causes, resolutions, and additional information sources.
Rules in the Alert Rule Group for DPM
| Rule | Enabled | Severity |
|---|---|---|
Protected Computer |
||
DPM Alert 370: Agent operation failed |
Yes |
Critical Error |
DPM Alert 3116: Failed to stop protection |
No |
Critical Error |
DPM Alert 3118: Manual replica creation pending |
No |
Informational |
DPM Alert 3121: Agent incompatible |
Yes |
Critical Error |
DPM Alert 3122: Agent unreachable |
Yes |
Warning |
DPM Alert 3123: End user recovery permission update failed |
Yes |
Warning |
DPM Alert 3311: Backup to tape failed |
Yes |
Critical Error |
DPM Alert 3312: Library catalog build failed |
Yes |
Warning |
DPM Server |
||
DPM Alert: DPM server availability |
Yes |
Critical |
DPM Alert 369: No agent on cluster node |
Yes |
Critical Error |
DPM Alert 24059: Tape encryption certificate expiration |
Yes |
Warning |
DPM Alert 3168: Database size threshold reached |
Yes |
Warning |
DPM Alert: Memory usage |
Yes |
Warning |
DPM Alert: Processor usage |
Yes |
Warning |
Data source |
||
DPM Alert 3178: Consolidation of recovery points of replica failed |
Yes |
Warning |
DPM Alert 3111: Recovery failure |
Yes |
Warning |
DPM Alert 3165: Recovery partial success |
Yes |
Warning |
DPM Alert 1689: Partial Backup Success |
No |
Warning |
DPM Alert 690: Share Path Changed |
No |
Warning |
DPM Alert 3114: Recovery point creation failure |
Yes |
Critical Error |
DPM Alert 3114: Recovery point creation failure without alert |
No |
Warning |
DPM Alert 3114: Recovery point creation failure with threshold |
No |
Warning |
DPM Alert 3163: Replica inconsistent |
Yes |
Critical Error |
DPM Alert 3163: Replica inconsistent without alert |
No |
Warning |
DPM Alert 3163: Replica inconsistent with threshold |
No |
Warning |
DPM Alert 3106: Replica verification in progress |
Yes |
Critical Error |
DPM Alert 3115: Synchronization failed |
Yes |
Warning |
DPM Alert 3115: Synchronization failed without alert |
No |
Normal |
DPM Alert 3115: Synchronization failed with threshold |
No |
Warning |
DPM Alert 3161: Volume missing |
Yes |
Critical Error |
DPM Alert 3170: Job initialization failure |
Yes |
Critical Error |
DPM Alert 3169: Recovery point volume threshold exceeded |
Yes |
Critical Error |
DPM Alert 3100: Replica volume threshold exceeded |
Yes |
Warning |
DPM Alert 3128: Data corruption detected |
Yes |
Warning |
DPM Alert: Data corruption detected during read |
Yes |
Warning |
DPM Alert 1556: Staging Area Restore In Progress |
No |
Warning |
DPM Alert 1557: Staging Area Restore Complete Success |
No |
Warning |
DPM Alert 1558: Staging Area Restore Partial Success |
No |
Warning |
Disk |
||
DPM Alert 3120: Disk missing |
Yes |
Critical Error |
Library |
||
DPM Alert 3310: Data set copy failed |
Yes |
Critical Error |
DPM Alert 3316: Detailed inventory failed |
No |
Critical Error |
DPM Alert 3305: Free media threshold reached |
Yes |
Warning |
DPM Alert 3301: Library not available |
Yes |
Critical Error |
DPM Alert 3302: Library not working efficiently |
Yes |
Warning |
DPM Alert 3308: Media erase failed |
Yes |
Critical Error |
DPM Alert 3309: Media verification failed |
Yes |
Critical Error |
DPM Alert 3317: Tape data integrity issues |
Yes |
Critical Error |
DPM Alert 3315: Job waiting for tape |
Yes |
Critical Error |
Drive |
||
Alert 3303: Drive not functioning |
Yes |
Critical Error |
Server Rule Group
The DPM Server rule performs health checks on the System Center Data Protection Manager (DPM) service and monitors database availability. The following table describes the rule in this rule group.
Rules in the Server Rule Group for DPM
| Rule | Type | Enabled | Severity | Description |
|---|---|---|---|---|
DPM Server Not Available |
Event |
Yes |
N/A |
This rule generates an event in Operations Manager when the DPM database or service is not available. The DPM Server rule uses this information to generate an alert. As a result of the alert, the state of the DPM server is updated to Red. |
Service Discovery Rule Group
This rule group contains a single rule, described in the following table, which collects information about managed computers for the System Center Data Protection Manager (DPM) Management Pack.
Rules in the Service Discovery Rule Group for DPM
| Rule | Type | Enabled | Severity | Description |
|---|---|---|---|---|
DPM Server Discovery |
Event |
Yes |
N/A |
This rule runs a script that pings all the servers on the network and identified the computers running DPM 2010. |
DPM Data Discovery |
Event |
Yes |
N/A |
This rule runs a script to identify all DPM servers and lists the objects on that server. The objects could be protected computers, data sources, drives, disks, and libraries. |