Our SQL 2008 backups were working just fine with Data Protection Manager 2012 until we upgraded SQL to SQL 2012. Then we started getting the error:
The DPM job failed for SQL Server 2012 database <SQL database> on <our sql server> because the protection agent did not have sysadmin privileges on the SQL Server instance. (ID 33424 Details: )
The suggestion is to add “‘NT Service\DPMRA\ to the sysadmin role on the SQL Server instance.” That’s very specific so that must be the fix. The problem is I don’t have an ‘NT Service\DPMRA’ user in Windows or SQL. Here’s the fix:
- In SQL Management Studio, connect to the SQL 2012 Server and then expand Security.
- Expand Logins and right click on NT AUTHORITY\SYSTEM and select Properties.
- Click Server Roles, check sysadmin and click OK.
I read a post saying you could also add NT Service\DPMA like the Recommended Action in DPM states, but I don’t have that as a SQL Logins and wasn’t able to find it as a Windows account to create one.
Once I added sysadmin to the Server Roles, I was able to right click and “Perform Consistency Check…” and everything took off. You may also go to the jobs themselves and click “Run configuration protection job again”.
Note, for me the Consistency Checks failed on some but this time with a new (more common) error saying “Recovery point creation failed”. The fix was simply to create a new Recovery Point.