Post reply

when dc is down can we remove database in dr out of always on secondary replica

  • March 18, 2024 at 6:54 am

    #4397251

    HI All,

    primary server is in always on secondary is a replica when primary DC is down due to unexpected power off , can we make the secondary database online by removing them from availability group

    when dc is down can we remove database in dr out of always on secondary replica

    thanks

    naga.rohitkumar

    Thanks
    Naga.Rohitkumar

  • March 18, 2024 at 8:12 am

    #4397302

    You don't need to remove them, if you have setup the cluster and AG right it should allow some form of failover, either automatic or manual to the secondary.

    You need to diagnose what has gone on which is preventing you from failing over.

    Is it that the WSFC itself is offline as for some reason your quorum is lost as you had majority votes in the primary DC?  Well to fix that you need to start the WSFC with force quorum mode, then do a force failover.

    Is the cluster itself online, but the AG is set for manual failover, well then you just need to initiate a manual failover.

    Last thing you want to be doing is removing databases from the AG as you'll just have a nightmare when the primary come back online.

    Start from the OS and work your way up in your diagnosis.

  • April 4, 2024 at 5:03 am

    #4407262

    Yes , you can remove the database out of the Availability Group.

    You will need to do a manual failover to the Secondary if it did not already happen.

    Also, if your secondary replica Availability  Mode was set to 'asynchronous commit' , you will have to run the following query to resume the data synchronization from the secondary replica.

    ALTER DATABASE database_name SET HADR RESUME;

    Thanks,

    William

     

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

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