August 30, 2016 at 10:14 am
We have an availability group spanning 3 nodes with 6 databases and one node in a remote data center. The last couple of times, after a loss of network connectivity to the remote data center, data replication to the remote secondary replica replication falls behind and we've had to restart SQL services on the secondary for it to synchronize.
AlwaysOn AG dashboard shows synchronization state as healthy on all the secondaries and the remote node is reachable from the primary. It also does not affect all the databases belonging to the AG.
Is there a way to force the replication to restart? I've tried suspend\resume data movement on the affected databases. The databases are large, a couple over 1TB in size.
We only have a 100 Mbps MPLS connection to the remote data center, 60-90 ms latency. SQL Server 2012 (build 11.0.6523). Any troubleshooting tips or suggestions would be appreciated.
Thank you in advance for your time.
- an accidental dba
August 31, 2016 at 1:37 am
KGonz (8/30/2016)
data replication to the remote secondary replica replication falls behind and we've had to restart SQL services on the secondary for it to synchronize.
This seems a bit of a brute-force solution. Is the secondary synchronous or asynchronous?
September 1, 2016 at 9:06 am
asynchronous. agreed, restarting sql services is not ideal only resorted to it after the secondary fell 30 min behind. thank you in advance for your time.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply