SQL AlwaysOn Database Mirrored backups promoted to full
Summary: This article explains the workaround when the SQL AlwaysOn Database Mirrored backups promoted to full.
Symptoms
Client Initiated SQL AlwaysOn Diff/Inc level & log backups get promoted to FULL for a Database Mirroring setup.
Full backup working fine
Customer has SQL Database mirroring setup.
NetWorker 9.0.1.6
SQL Server 2014
nsrsqlsv.log
NSR info SQL Connection to SSQLSERVER\SQLXXXXX is created. SQL Server Version is 12.00.5203.
Microsoft SQL server documentation provides details about the following SQL Server Provider error:
Named Pipes Provider: Could not open a connection to SQL Server [5].
Microsoft SQL server documentation provides details about the following SQL Server Provider error:
Invalid authorization specification Unable to determine status of mirror partner backups for database 'XXXX'. Backup level forced to full.
Cause
Potential Log chain issues were removed by disabling the SQL VSS writer.nsrinfo was checked to show the indexes were being directed to the correct client.
Resolution
Enable SQL Server Named Pipes using the SQL Server Configuration Manager. By Default 'Named Pipes' is disabled.
Once enabled, the backup could check the mirror and continued to work as expected.
Named-pipes provide a way for inter-process communication to occur among processes running on the same machine. The advantage of named pipes is that it is usually much faster, and frees up network stack resources.