Distributed Availability Groups Connectivity post failover

  • Hi all,

    So we are looking at our DR solution and DAG. The question is coming  how the applications connect post DAG failover and the timings around the return to operation. So my question is...Post failover what the best way to get application to go to the correct (now DR) Availability group?

    A few options we are discussing:

    1. Update all connection strings on the web/app servers etc - Laborious as we have so many and time consuming
    2. Doing it from DNS - Is there some recommendations for ensuring that all DC's are updated in a timely manner?
    3. Doing something on the cluster/SQL side; renaming both listeners? Is this more dangerous than its worth?

    If anyone has experience of this or suggestions would be great to hear them.

    Thanks,

    V

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • DNS would be the best solution - that way you don't have to update connection strings when you failover to the DR/alternate site.  Upon failover the aliases would have to be updated - maybe, depends on how DNS is setup in your environment.  You would need to work with that team to determine the best options.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Thanks @Jeffrey Williams

    Working through with the team. This was our original plan just wondered if there was any magic we could do 🙂

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply