DPM Database Update

DPM_Database_Update_1_Rule (Rule)

Knowledge Base article:

Management Pack

Summary
This alert is generated in MOM when the DPM service or DPM Administrator Console on the specified Data Protection Manager (DPM) server encounters a database error in DPM. DPM processes rely on six databases created in Microsoft^® SQL Server™: The DPM database (DPMDB.mdf) stores DPM settings and configuration information. The Report database (ReportServer.mdf) stores reporting information for DPM. In addition, DPM processes rely on the following databases: Tempdb.mdf, Master.mdf, Model.mdf, and Msdb.mdf. Database failures can cause DPM jobs to fail, interfere with the use of DPM Administrator Console, prevent DPM reporting, and cause the DPM service to stop. A backlog of requests due to low memory or high CPU usage also can cause client time-outs (when DPM processes take a long time to establish a connection to SQL Server).

Causes
Possible causes of database failures in DPM include: Too many protection jobs are being processed on the DPM server at one time, and SQL Server is unable to handle the volume of requests in a timely manner. This is the most common cause of client time-outs and general network errors. A database or transaction log that DPM uses has run out of disk space. A database that DPM uses has entered an inconsistent state or has become corrupted. The SQL Server service is not running or is not configured correctly.

Resolutions
Some database failures in DPM are caused by transitory problems that may resolve themselves. Examples include insufficient resources, client time-outs, insufficient disk space for transaction logs, deadlocks in SQL Server, recoverable database errors, and timing issues. Before you run diagnostics for this type of database failure, perform the following steps on the DPM server to ensure that the problem is not a transitory one that will resolve itself. To resolve issues that might cause a transitory database failure Ensure that the SQL Server service is running. In Administrative Tools, open Services, and make sure that the status of the MSSQL$Microsoft$DPM$ service is "Started." If this does not fix the problem, close DPM Administrator Console. If this does not fix the problem, stop and restart the DPM service and the SQL Server service. In Administrative Tools, open Services, and then restart the services by performing the following steps: Stop the DPM service if it is running. (The service stops automatically when not in use.) Stop the SQL Server service (MSSQL$Microsoft$DPM$). Start the SQL Server service (MSSQL$Microsoft$DPM$). The DPM service will start automatically the next time that it is needed. For database failures in DPM that are not transitory in nature, the issues can be complex. You will need to work with your SQL Server administrator to diagnose and resolve the related issues. The following list provides a starting point for resolving database failures in each general area. For detailed information about troubleshooting these database problems, see the " Troubleshooting" chapter in the Microsoft^® System Center Data Protection Manager 2006 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=46369. To get started troubleshooting database failures in DPM: If you are experiencing client time-outs and general network errors related to SQL Server being unable to handle the volume of requests, modify protection schedules for protection groups to stagger protection jobs. Consider offsetting some synchronization jobs from the beginning of the hour. For more information, see "How to modify protection schedules" in DPM Help at http://go.microsoft.com/fwlink/?linkid=46350. For fatal database errors, it is unlikely that the database itself has been damaged. Ensure that the DPM instance of SQL Server (the MSSQL$Microsoft$DPM$ service) is running. Then use Windows Event Viewer to find information about related events. For database connection failures, ensure that the MSSQL$Microsoft$DPM$ service is running on the DPM server. Then use Windows Event Viewer to find information about related events. On a new DPM server, ensure that SQL Server is configured correctly. For information about configuring SQL Server for use with DPM, see the " Installing DPM" chapter in the Microsoft^® System Center Data Protection Manager 2006 Planning and Deployment Guide at http://go.microsoft.com/fwlink/?LinkId=46357. For database failures related to a shortage of disk space for a database or transaction log, SQL Server provides tools for analyzing and mitigating disk space shortages. For more information, see SQL Server Enterprise Manager Help. If the integrity of a database is in question, contact your SQL Server administrator. You might need to repair or restore the database in SQL Server. If DPM finds that a database is in an "inconsistent" state, the problem is unlikely to resolve itself. For help with troubleshooting the problem, contact Microsoft product support. For information, see the Microsoft Product Support Web site at http://go.microsoft.com/fwlink/?linkid=46538.

External Knowledge Sources
For more information about diagnosing and resolving issues related to database failures in DPM, see the " Troubleshooting" chapter in the DPM 2006 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=46369. For information about DPM events, see the " Data Protection Manager 2006 Error Code Catalog" appendix in the DPM 2006 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=46370. For information about configuring SQL Server for use with DPM, see the " Installing DPM" chapter in the DPM 2006 Planning and Deployment Guide at http://go.microsoft.com/fwlink/?LinkId=46357. For information about troubleshooting problems with SQL Server databases, see the documentation for SQL Server.

Related Events
Related DPM events: 940, 941, 942, 943, 944, 945

© 2000-2004 Microsoft Corporation, all rights reserved.

Element properties:

Target	Microsoft.SystemCenter.DPM.Microsoft_System_Center_Data_Protection_Manager_2006_Servers_Installation
Category	EventCollection
Enabled	True
Alert Generate	False
Remotable	True
Comment	Mom2005ID='{536515DD-EBEC-4728-A18D-15F1B82E0F67}';MOM2005ComputerGroupID={49DAC409-542F-4A3A-A540-7E9C08CFF520}

Member Modules:

ID	Module Type	TypeId	RunAs
_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_	DataSource	System.Mom.BackwardCompatibility.FilteredEvent.DataProvider	Default
ScriptResponse1	WriteAction	DPM_Database_Update	Default

Source Code:

<Rule ID="DPM_Database_Update_1_Rule" Target="Microsoft.SystemCenter.DPM.Microsoft_System_Center_Data_Protection_Manager_2006_Servers_Installation" Enabled="true" ConfirmDelivery="false" Comment="Mom2005ID='{536515DD-EBEC-4728-A18D-15F1B82E0F67}';MOM2005ComputerGroupID={49DAC409-542F-4A3A-A540-7E9C08CFF520}">

  <Category>EventCollection</Category>

  <DataSources>

    <DataSource ID="_F320DA51_13BF_11D3_B2CD_00A0C92A28B4_" Comment="{F320DA51-13BF-11D3-B2CD-00A0C92A28B4}" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.FilteredEvent.DataProvider">

      <Expression>

        <RegExExpression>

          <ValueExpression>

            <XPathQuery Type="Integer">EventDisplayNumber</XPathQuery>

          </ValueExpression>

          <Operator>MatchesMOM2005RegularExpression</Operator>

          <Pattern>^(30501|30503)$</Pattern>

        </RegExExpression>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="ScriptResponse1" TypeID="DPM_Database_Update">

      <AlertGeneration>

        <GenerateAlert>false</GenerateAlert>

        <Owner/>

        <Description>

            $Data/EventDescription$

          </Description>

        <AlertLevel>50</AlertLevel>

        <ResolutionState/>

        <Source>

            $Data/PublisherName$

          </Source>

        <Name>DPM Database Update</Name>

      </AlertGeneration>

      <InvokerType>0</InvokerType>

    </WriteAction>

  </WriteActions>

</Rule>