my personal blog about systemcenter

Archive for February, 2011

 

repost from : scug.dk

With the release of DPM 2010 Microsoft also released a management pack to tie the two products better together enabling single point of monitoring.

 

Download link  http://www.microsoft.com/downloads/en/details.aspx?FamilyID=32077d99-618f-43d0-843d-4ba4f8019f84&displaylang=en or download and install is possible from within SCOM

 

This will be a short introduction to the management pack a more detailed intro will follow when time permits.

The management tells us what we can see from the DPM interface but it operations a easier way to verify that everything is as it should be without having to open yet another console.

image

Go to Administration – > Management Packs –> Import Management Pack

image

Select the DPM 2010 Management Pack and import it.

 

image

And after a few seconds it should be imported

image

The management pack adds discoveries to find and add the DPM servers to SCOM as well as all resource types for DPM.

image

The Discovery runs once a day if you need to look for new DPM servers more frequently you can override the DPM 2010 Server Discovery , remember to create a Override management pack for DPM, the script targets Windows Servers.

 

image

The script to discovery clients being protected is targeted at the DPM server so SCOM will query DPM with powershell to get all needed information about the DPM installation , default discovery internal is 12 hours , again this can be adjusted if needed.

 

image

a easy way to get a overview if protection is missing for some agent is to go to the Protect Computer and Resource Group State , there will be a “Number of Data Sources” if this is 0 there are no Protection Groups setup against this resource and it wont be protected , the management pack wont detect clients that only is installed and not bound to a DPM server.

 

image

each view will give a overview of the datasource states and the health of the datasources in them

image

and a view of all resources across types

 

image

 

after a while DPM reported failure to protect a SQL database (after I stopped the SQL server service)

 

image

DPM utilizes the DPM Alerts Event log on the DPM servers to monitor for problems within the DPM installation (Rules can also be used included but disabled pr default)

image

But still no errors due to the Sync Error

 

image

Recovery Point Failed (3114) is disabled pr default

image

Select Overrides and create a override

image

and enable the monitor

Link to TechNet article showing what is enabled pr default http://technet.microsoft.com/en-us/library/gg299575.aspx but the documentation is a 27 pages must read to get a overview of what the management pack can do and especially if you use a ticketing system.

 

image

 

And we can see our alert

 

image

Creation of recovery points for DEMOSMDB01DWDataMart on DEMOSMDB01.demo.local have failed. The last recovery point creation failed for the following reason: (ID: 3114) The DPM job failed for DEMOSMDB01DWDataMart on DEMOSMDB01.demo.local because the SQL Server instance refused a connection to the protection agent. (ID: 30172)

 

and we can drill down from DPM Server state level to the error message that triggered the alert.

 

The management pack have a SLA feature that will be covered later that will only trigger alerts pr default if a backup have failed for 24 hours that can be configured , in most cases a single failed backup shouldn’t trigger a critical error as this can happen to do server restarts and should not  be critical for the backup operation due to DPM will run past again soon to create a new recovery point