Post reply

How to sync Always on AG in primary site with Always on AG in DR ?

  • June 20, 2020 at 4:27 am

    #3764478

    The primary site has 2 database servers connected to a SAN. both nodes running on SQL server 2016. Both the servers are configured to function as an always on availability group as opposed to a Fail over Cluster.

    The DR has an identical setup; 2 nodes, a SAN. both nodes configured as an always on availability group.

    In order to sync primary with DR, both the AGs were configured as a distributed AG, however the documentation, implementation steps, lack of monitoring options around a distributed AG deem us to have a very little confidence over implementing it in production. we've also noticed that the available views and management studio options sometimes show inaccurate status information about the distributed AG. Hence the below questions :

    1. is distributed AG a matured solution suitable to implement on a production environment ? how to properly implement it ?

    2. What are the other alternatives available for synchronizing a primary site AG with a DR AG ?

    3. is AG better than FOC ?.

  • June 21, 2020 at 5:10 am

    #3764577

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

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

  • July 19, 2020 at 12:34 am

    #3771118

    what is the reason for using a Distributed AG?  Have you followed the guidance in this link?  Especially, do you have a listener in place?

    https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/distributed-availability-groups?view=sql-server-ver15#understand-distributed-availability-groups

    "A distributed availability group requires that the underlying availability groups have a listener. Rather than provide the underlying server name for a standalone instance (or in the case of a SQL Server failover cluster instance [FCI], the value associated with the network name resource) as you would with a traditional availability group, you specify the configured listener for the distributed availability group with the parameter ENDPOINT_URL when you create it. Although each underlying availability group of the distributed availability group has a listener, a distributed availability group has no listener."

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

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