DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2769094 - Last Review: November 19, 2012 - Revision: 4.0

Symptoms

When attempting to protect a SQL Server AlwaysOn Availability Group (AG) using System Center 2012 Data Protection Manager (DPM), the job fails with the following error:

The DPM job failed for SQL Server 2012 database <DBname> on <serverName> because the SQL Server instance refused a connection to the protection agent. (ID 30172 Details: Internal error code: 0x80990F75)

In SQL, AlwaysOn is configured as follows:

Availability Mode: Synchronous Commit
Failover Mode: Automatic
Connections in Primary Role: Allow all connections
Readable Secondary: No

Backup Preferences:
     Perfer Secondary
     Priority: 50 (for each node)
     Exclude Replica: False (for each node)

In general: Prefer Secondary - Backups should occur on a secondary replica except when the primary replica is the only replica online. If there are multiple secondary replicas available then the node with the highest backup priority will be selected for backup. In the case that only primary replica is available then backup should occur on the primary replica.  

Cause

This occurs due to incorrect SQL AlwaysOn settings for DPM backups where Make Readable Secondary is set to No.

Resolution

Set Make Readable Secondary to Yes on all the nodes.

More Information

If setting Make Readable Secondary to Yes on all the nodes does not resolve the issue, verify on the SQL server that the DPMRA service is running under the Local System account AND that the NT Authority\System has the sysadmin selected for the server role in SQL studio.

Steps
****
a.) On the SQL side the DPMRA service should run under Local system. You can verify this via services in computer management.

b.) Connect to the SQL 2012 instance with the help of SQL2012 Management Studio > select and expand Security > select and expand Logins > right click on the NT AUTHORITY\SYSTEM and select Properties > click on Serverroles > check the sysadmin checkbox > click OK

after this, In certain cases it may also be necessary to reinstall the DPM Agent on the SQL server OR manually run the SetDPMServer command on the SQL server specifying the DPM server.

keywords: sql alwayson sql always on

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Applies to
  • Microsoft System Center 2012 Data Protection Manager
Keywords: 
KB2769094
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support