status of database in availibility group

  • I setup a staging environment to test basic always on availability group on SQL servers standard Edition, hence it is  a basic availability group.

    After it setup, I manually failover from serverA (primary) to serverB (secondary). It works OK.

    Then I did another failover from serverB to ServerA.

    Now ServeA is the primary again, and database showing synchronized after I click resume data movement.

    But on the secondary node, I see the database with a status of Synchronizing. and even after I refresh many times, it seems still stuck and show synchronizing next to the database name.

    What the correct status it should show on secondary database?

    I remember when I first set it up, it shows restoring.

    Thanks,

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

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

  • What is the availability mode?  Sync or Async?

    As you mention resume data movement I am going to say your in Async mode so yes the secondary database should be in a synchronising state.

    Only in Sync mode will it return to a synchronised state.

     

    https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/availability-modes-always-on-availability-groups?view=sql-server-ver16

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

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