SQL Server always on , one of the nodes down

NeophyteSQL 241 Reputation points
2021-01-29T19:41:55.903+00:00

hi all,

we had high availability always on clustering set up

one of the nodes could not be booted up, so it is down.

ever since the cluster has only one node.

but there are errors in the windows log and informational messages in the sql server logs as seen below.

what can be done to "clean" both the sql server and windows so the node ALa-SQL-01 is not seen anymore

Always On Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,867 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Sean Gallardy - MSFT 1,886 Reputation points Microsoft Employee
    2021-01-29T22:31:23.247+00:00

    what can be done to "clean" both the sql server and windows so the node ALa-SQL-01 is not seen anymore

    SQL Server is pretty simple, remove the replica from the availability group. In fact, if you haven't already completed this then your log is being held and will continue to grow unabated until it hits the specified limit and your database stop functioning.

    The Windows side would be to evict the node from the cluster. You may also have to manually clean up active directory of any computer accounts.

    ever since the cluster has only one node.

    Then you don't have any high availability, which is a problem if you want HA.

    0 comments No comments

  2. CathyJi-MSFT 21,096 Reputation points Microsoft Vendor
    2021-02-01T07:31:45.137+00:00

    Hi @NeophyteSQL ,

    SQL server AG is based on WSFC. Deploying Always On availability groups for HA on Windows requires a Windows Server Failover Cluster(WSFC). Each availability replica of a given availability group must reside on a different node of the same WSFC. You had to fix the windows failover cluster issue firstly, then fix the AG issue.


    If the response is helpful, please click "Accept Answer" and upvote it, thank you.

    0 comments No comments

  3. NeophyteSQL 241 Reputation points
    2021-02-08T15:09:30.67+00:00

    For some reason, the broken cluster node cannot be evicted.

    what happens when cluster is destroyed. (destroy cluster option)

    does the sql cluster name still hold good, or do the applications need to connect to the stand alone instance name.

    0 comments No comments