Quantcast
Channel: SQL Server Replication forum
Viewing all articles
Browse latest Browse all 4054

SQL 2012 Transactional Replication Publisher is also AG Primary, AG fine, but Replication status continuously 'waiting for next Log backup'

$
0
0

Hi,

I have a SQL 2012 instance that hosts 3 databases that are publishers in (push) transactional replication to subscribers in other domains and are also primary in an Availability Group to other instances in the same domain.  The AG is healty (synchronized), and replication is ok for 2 databases, but the third continuously shows the Publisher to Distributor history status as 'Replicated transactions are waiting for next Log backup or for mirroring to catch up.'

I have weekly full, nightly differential, and hourly log.  Those are running and I've tested restoring the publisher db from them into a test instance.  The option for sync_with_backup is 0.  I generated a new snapshot, no change (haven't reinitialized, that will be last possible option as this is production).  When the log backups run, status will briefly change to 'Approximately (x) log records have been scanned in pass # ..., 0 of which were marked for replication' and some data does replicate, but then status immediately changes back to the message about waiting for log backup.   We are only replicating tables (no views, sp's, etc).  All subscribers and AG secondaries are SQL 2012.  My db is less than 200 GB data. 

The jobs are continuously running and data updates are occurring on the primary.  The distribution database is on the same instance as the publishers.  Anyone have any ideas what could be happening? 

Thanks greatly!


Viewing all articles
Browse latest Browse all 4054

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>