ads

Style3[OneLeft]

Style3[OneRight]

Style5[ImagesOnly]

Style2

 By Steven Jordan on March 26th, 2013. 

Takeaway:   DPM 2010 can backup SQL 2012 with this simple permission change.

Problem:  DPM 2010 cannot backup SQL 2012 databases.

  • DPM 2010 Recovery Point Errors:  Recovery point creation jobs for SQL Server 2012 database SERVER\NAME have been failing.  The number of failed recovery point creation jobs = x.
  •  DPM 2010 Replica is inconstant Alerts:  The replica of SQL Server 2012 database SERVER\NAME is inconsistent with the protected data source. 

Solution:  NT AUTHORITY\System must be granted Sysadmin permissions on the SQL 2012 database instance.


Background:    By default, SQL 2010 includes the Sysadmin permissions for the NT Authority\System account.  However, SQL 2012 does not include the Sysadmin permissions for the NT Authority\System account by default.   

Fix DPM 2010 consistency errors for SQL 2012 databases by adding the Sysadmin server role to the SQL 2012 NT AUTHORITY\System:


1.   Modify the NT Authority\System login:














2.  Add Sysadmin server role









O #DPM #Consistency #SQL O


Reference:  http://theessentialexchange.com/blogs/michael/default.aspx

About Steven Jordan

Steven Jordan is an infrastructure and process management specialist. Steven holds a Master of Science degree in ICT from the University of Wisconsin Stout. Steven is also a Cisco Certified Network Professional (CCNP) and Master Gardener.
«
Next
Newer Post
»
Previous
Older Post

1 comments: