Hello Readers,
Having recently implemented Microsoft Data Protection Manager 2012 SP1 into my Lab Envirnoment, I have been experiencing issues protecting Microsoft SQL Server 2012 Databases as seen below
Image may be NSFW.
Clik here to view.
It appears this is a known issue with DPM/SQL 2012 as Microsoft have released information within one of its press release. The statement says;
Do the following to protect the Microsoft SQL Server 2012 database:
Connect to the SQL Server 2012 instance through the Management Studio, and then select and expand Security. Select and expand Logins, right-click NT AUTHORITY\SYSTEM, and then click Properties. Click Serverroles, click sysadmin, and then click OK.
So as a test I have set “sysadmin” on my DPM instance as shown below
Image may be NSFW.
Clik here to view.
And “Performed a Consistency Check” on the SQL Tables that failed in Data Protection Manager. SUCESS!! The tables are now showing as “OK” so the above step just needed to be completed on my Default SQL Instance.
Image may be NSFW.
Clik here to view.
The release notes can be found that the following link
Release Notes for System Center 2012 – Data Protection Manager http://technet.microsoft.com/en-us/library/jj860415.aspx
