my personal blog about systemcenter

Data Protection Manager , Detect SQL Backup Jobs not triggered from DPM

 

One reoccurring task for many Data Protection Manger Administrators is to find out who broke their SQL Backup chain.

image

Data Protection Manager does a excellent job out of box notifying us when and why a job would fail

image

And the Management Pack for Operations Manager provided by Microsoft also picks up that alert and tells us what to do.

image

If we want additional information or perhaps want to catch errors before next synchronization we can make a simple Operations Manager Rule triggering on the SQL server logging

image

In Operations Manager Create a Event Based Alerting Rule

image

Target the Rule at SQL Database Engine and leave it disabled if you don’t want monitoring of all SQL instances

image

Select Application Log

image

And 18264 for Full Backup and 18265 for Log backup (still need to find failed backup event id’s) , and MSSQL server as source

image

and a eventdescription that does not contain DPM_SQL , for performance reasons its recommended that we don’t use description but find the event parameter the text is in, but since this is a low volume event performance shouldn’t suffer

 

image

And if the rule isn’t enabled for all SQL servers we need to create a override

image

And enable the rule for the SQL servers we want to monitor

 

image

And when we create a manual backup we will get a alert right away , the DPM alert triggers at next synchronization job

 
Comments