Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In case of async commit setup and the backup preference set to secondary replica. I have observed, in case of high unsent log size, log backup on secondary replica starts failing for that database with error:

Connection With Primary Replica Not Active

The unsent log size was ~4GB. There was no connectivity issues.

What factors impact log backups in multiple secondaries and async commit mode?

share|improve this question
Which DBMS and/or tool(s) are you using that give you this error? This question is pretty meaningless without that information. – Colin 't Hart Feb 27 '14 at 9:22
This is the error we get in SSMS, with the normal backup command. BAckup log <dbname> to disk = '<path>' – user34707 Feb 27 '14 at 10:45
What is SSMS? Please update your question to include name of DBMS and tool and tag for them too. – Colin 't Hart Feb 27 '14 at 10:49
You need to first verify that your secondary replica is in a SYNCHRONIZING state. – Thomas Stringer Mar 7 '14 at 19:07

You can backup on any secondary replica if they are connected to the primary replica AND the state is either SYNCHRONIZED or SYNCHRONIZING.

It seems that you should check the connection to the primary replica. Please take a look in the sql server's error log.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.