Q: Why am I receiving an error when trying to protect a SQL Server 2012 server using System Center 2012 Data Protection Manager?
A: If you have performed a fresh SQL Server installation and are trying to protect it with System Center 2012 Data Protection Manager (DPM), you might get an error in DPM that the server can't be protected.
If you open Event Viewer and look in the Application log, you might see an error similar to the following:
- Log Name: DPM Alerts
- Source: DPM-EM
- Date: 5/6/2013 3:53:08 PM
- Event ID: 3170
- Task Category: None
- Level: Error
- Keywords: Classic
- User: N/A
- Computer: savdaldpm12.savilltech.net
- DPM could not start a recovery, consistency check, or initial replica creation job for SAVDALSQL01\AppController on savdalsql01.savilltech.net for following reason:
- (ID: 3170)
- The DPM job failed for SAVDALSQL01\AppController on savdalsql01.savilltech.net because the protection agent did not have sysadmin privileges on the SQL Server instance. (ID: 33424)
As the error suggests, the problem is that the built-in NT Authority\SYSTEM doesn't have sysadmin rights. To resolve, perform the following:
- Start Microsoft SQL Server Management Studio.
- Expand Security, Logins.
- Double-click NT AUTHORITY\SYSTEM.
- Select Server Roles and check the sysadmin role and click OK.
In DPM, right-click the protected service and select the Perform consistency check ... action, which will retry the protection and solve the problem.