SQL Server 2 node availability group - deleting secondary server, to be replaced later



  • I found https://dba.stackexchange.com/questions/266597/questions-regarding-removing-a-secondary-node-from-an-availability-group with Tony Hinkle's answer, but I'd like to get some clarification on 1) removing the databases from the AG, 2) removing the secondary node from the cluster, and 3) removing all quorum votes except for the one node in the cluster.

    Does step 2 mean removing the node from the AG first, then from WSFC?

    How does the file share witness factor into removing all the other quorum votes? Should the one remaining cluster node and the file share witness keep their votes or just the node?

    Thanks!



  • removing the databases from the AG

    Database can be removed from AG but if you want it back you cannot simply add it, you have to first take full and log backup from primary, restore it on the DB and then add it. For VLDB is this a challenge.

    removing the secondary node from the cluster

    Again it would be advisable to break the AG first and then remove the node. It should then be removed from WSFC, If you want to add it back restore all the databases and then add it back with same steps, first in WSFC then in AG.

    removing all quorum votes except for the one node in the cluster.

    If node is removed its vote will be removed. With one node what is point in worrying about Quorum.

    How does the file share witness factor into removing all the other quorum votes?

    With single node, like I said above what is point in FS witness anyway.

    I would say I dont like this idea very much. This will create more work for you. Please note if you have SA purchased and you are NOT running any queries on secondary which means it non readable you do not have to license it, provided it has same no of cores as primary.




Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2