February 17, 2016 at 1:35 am
I have configured the AlwaysOn Availability setup in node1 , node2 and node3 .
always data will sends from node1 to third party server.
Node1 is primary,if primary is healthy no problem,but once primary goes down what about sql server agent jobs like replication ,ssis packages and other jobs?
Case1 : if secondary server will take care means multiple secondaries we have,multiple secondaries sends the same data to third party server ,then data redundancy will occurs.
Case2 : No,we can't send the data using secondary server means what is the alternative,if primary server goes down?
How can we overcome this?
I'm struggling so much regarding this scenario right now.
Early reply is greatfull to me.
I hope you will reply now.
Thanks and Regards
amicusbabu
February 17, 2016 at 8:32 am
amicusbabu (2/17/2016)
I have configured the AlwaysOn Availability setup in node1 , node2 and node3 .always data will sends from node1 to third party server.
Node1 is primary,if primary is healthy no problem,but once primary goes down what about sql server agent jobs like replication ,ssis packages and other jobs?
Case1 : if secondary server will take care means multiple secondaries we have,multiple secondaries sends the same data to third party server ,then data redundancy will occurs.
Case2 : No,we can't send the data using secondary server means what is the alternative,if primary server goes down?
How can we overcome this?
I'm struggling so much regarding this scenario right now.
Early reply is greatfull to me.
I hope you will reply now.
Thanks and Regards
amicusbabu
I can give you a partial answer.
When you use AlwaysOn AG's, Only the databases in the AG are replicated. This excludes things like system databases, logins, and SQL Agent Jobs - all of those need to be created on each server within the AG.
Regarding the piece where you're trying to get data to a third party server, that would need further clarification about what you're trying to do. If the third party server is an SQL server, but not a part of your AG, you could set up log shipping at interval to provide a sort of warm standby. Reference https://blogs.msdn.microsoft.com/saponsqlserver/2013/01/24/alwayson-part-9-alwayson-and-logshipping/
If it's something else, you may have to get creative.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply