Alwayson Disaster Recovery

mukki mehra 1 Reputation point

I am using three node alwayson Availability Group SQL 2012 Enterprise Edition.

2 Node in DC with File Share Witness quorum also in DC and third node to be setup in DR

I need to perform a DR switchover with all DC down And DR database up for applications.

Can this solution work or I need to use Log Shipping as third node instead of alwayson AG node.

Please help on this.


Not Monitored
Not Monitored
Tag not monitored by Microsoft.
37,556 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. HariHaran Ramalingam 151 Reputation points

    Hi There

    Use Always on Synchronous for 2 nodes in same DC and Use Always on ASynchronous for the DR node.

    This will make sure nodes in SAME DC are up to date (Providing HA) and DIFFERENT DC will be almost up to date (Providing DR)

    So one issue ALL 3 NODES has to be in same WSFC

    Hariharan R

    Mark it as answered if it answered your question.

    0 comments No comments

  2. mukki mehra 1 Reputation point

    But my concern if all DC will be down completely including file share witnesses will application be able to connect with dr db alone in Alwayson configuration

    0 comments No comments

  3. HariHaran Ramalingam 151 Reputation points

    Then you might have 2 options

    1. Upgrade your SQL Server to 2016 to use Distributed AG feature. So you can keep your 3rd node in a different DC. DAG supports different WSFC to get connected
    2. Use Logshipping to move the log files and to establish DR to different DC.

    Hariharan R

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

  4. Navtej Singh Saini 4,221 Reputation points Microsoft Employee

    @mukki mehra

    Please do check the replies above. If you need further help, Please check the SQL Server forum for more insight and traction regarding this case as this forum is more designed to resolve Azure SQL PaaS Service.

    Let me know if any other question.

    Navtej S

    0 comments No comments