October 27, 2016 at 1:16 pm
I'm unable to get transactional replication to pick up on an AlwaysOn replica after failover.
I have a 4 node AlwaysOn configuration with 2 nodes at the main site, 2 at the DR site and a FSW. The 2 main site nodes are configured for Automatic/Synchronous fail-over, the 2 DR nodes are Manual/Asynchronous and transactional replication from one DB is configured to a remote subscriber. I configured my replication following this MSDN article and tested that replication works fine: https://msdn.microsoft.com/en-us/library/hh710046(v=sql.120)
My issue is with fail-over to the DR site to simulate the 2 primary site nodes being unavailable but not completely lost. The 2 DR nodes come online and I can resume data movement between them without issue. Changes to the configured publication DB also synchronize between the 2 DR nodes but nothing is delivered via replication to the subscriber.
I'm looking for a suggestion to get replication working without ejecting the 2 primary site nodes from the Availability Group. The intent of the exercise would be to fail back to either of the main site nodes when they are available again, but not delay replication while the primary site nodes are offline.
October 27, 2016 at 1:55 pm
Transnational replication has been postponed by Microsoft until 2027 and the widedescale introduction of quantum fibre, delayed by confusion regarding the identity of the next Dr Who. If however you are in the vicinity of an authenticated police box (the one on South Clark St, near Nicholson St is good), then you may be in luck. They're a forgiving bunch, all 350 of them. Give them as much detail as you can (they DETEST waffle and misinformation) and they will help you out. You are in 2017 right?
For better assistance in answering your questions, please read this[/url].
Hidden RBAR: Triangular Joins[/url] / The "Numbers" or "Tally" Table: What it is and how it replaces a loop[/url] Jeff Moden[/url]
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply