Troubleshoot database issues
Applies To: System Center 2012 SP1 - Data Protection Manager, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager
System Center 2012 – Data Protection Manager (DPM) processes rely on a database created in an instance of SQL Server 2008 SP1.
The DPM database stores all DPM settings, configuration, and reporting information for DPM.
A database failure can cause DPM jobs to fail, interfere with the use of DPM Administrator Console, prevent DPM reporting, and stop the DPM service. A backlog of requests caused by low memory or high CPU usage also can cause client timeouts (when DPM processes take a long time to establish a connection to SQL Server or run a SQL query).
Possible causes of DPM database failures include the following:
An unusually high number of protection jobs 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 timeouts and general network errors.
A database or transaction log that DPM uses has run out of disk space.
The DPM database enters an inconsistent state or becomes corrupted.
The SQL Server service is not running or is not configured correctly.
Some database failures in DPM are caused by transitory problems that may resolve themselves. Examples include insufficient resources, client timeouts, 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 transitory.
To resolve issues that might cause a transitory database failure
Verify that the SQL Server service is running. In Administrative Tools, open Services, and verify that the status of the SQL Server (MSDPM2010) service is Started. If it is not, right-click the service, and then click Start or Resume, as appropriate.
If this does not fix the problem, close and reopen DPM Administrator Console.
If this does not fix the problem, stop and restart both the DPM service and the SQL Server (MSDPM2010) service. (In most cases, restarting the DPM service will resolve the issue.) For instructions, see General troubleshooting steps.
If you experience 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 Database Errors table provides a starting point for resolving specific database errors. The Database Exceptions table later in this topic provides information about how to troubleshoot database exceptions.
To troubleshoot this error
Error 940: Unable to connect to the database because of a fatal database error. It is unlikely that the database itself has been damaged.
Ensure that the DPM instance of SQL Server (MSDPM2010) service is running. Then use Windows Event Viewer to find information about related events.
Error 941: Unable to connect to the DPM database.
To resolve issues related to database connection failures
Error 942: Database integrity is in question because of a hardware or software problem.
If the integrity of the DPM database is in question, contact your SQL Server administrator. You might need to repair or restore the database in SQL Server from backup media.
Inform the administrator every time this error is encountered. Look at Windows Event Log for SQL Server/media failures. It is possible that the problem is in the cache only and not on the disk itself. If so, restarting SQL Server corrects the problem. In some cases, it may be necessary to restore the database.
To resolve issues related to a database that may be corrupt
Error 943: Unable to connect to the DPM database because the database is in an inconsistent state.
If DPM finds that the database is in an inconsistent state, the problem is unlikely to resolve itself.
Error 944: Database operation failed.
Error 945: Unable to connect to the DPM database because of a general database failure.
For general database failures, ensure that the 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.
To resolve issues related to general database failures
To troubleshoot this exception
Exception 5168: Login failed for user <user name>.
DpmSync fails when trying to restore the DPM database because it cannot open the DPM database requested by the login.
Verify that the DPM installation contains a new DPM database and that it is online before trying to restore an older database. If a new database does not exist on the DPM installation, uninstall and then reinstall DPM. After the installation is complete, run DpmSync again.