Post reply

Distributed Availability Group Issue / Misunderstanding.

  • November 6, 2025 at 11:48 am

    #4681645

    Not sure if this is a tech mistake I've made or a lack of understanding:

    • Architecture = 2 x 2 node clusters, with 1 x AG each & 1 x testDB in AG1.
    • Aim = to use distributed availability group to port testDB from clusterA to clusterB.

    Steps:

    • Create DAG on clusterA listener to listener.
    • Join to DAG on clusterB.  Grant create any database.
    • Looks good.  testDB appears on clusterB / node 1.  Failover is fine - happy with it all.

    My problem is that stepping back to pre-failover, the database is never seeded to clusterB node2.  The database is not created there through AG2.  It does appear in the AG under availability databases but the join fails as the database is not created.  There are no errors to suggest an issue, which makes me think this is probably how it is supposed to work.

    Thanks.

     

  • November 7, 2025 at 12:10 pm

    #4682096

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

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

  • November 10, 2025 at 8:47 am

    #4683093

    Sounds like a pretty common Distributed AG configuration mix-up. Make sure both local AGs are set up correctly before joining them into the distributed one, and double-check that the endpoints, listener, and failover modes match on both sides. Also, take a look at the replica roles and sync state — they can look healthy even when something’s slightly off. Most of these issues end up being small setup mismatches between the local and distributed layers.

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

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