I would like to say that in my environment I have a 2 node in WSFC with the nodes
SQLServer-01 (Primary Server) SQLServer-02 (Secondary Server)
And for third vote in cluster also One (
File share witness)in quorum & also listener has configured .
I was not a guy who had made the configuration of WSFC , quorum and installation of both SQLServer.
Last Thursday the system administrator guy was updated some widows path and had setup a schedule time to restart the windows server operating systems.
When we came to office as on Sunday. we saw the SQL Server Database engine was stopped in both server as well as quorum was went to in Failed state.
We are able to start the SQL Server engine services in both server. In primary server after connecting with SSMS then find out the
Primary Server is in
Resolving State & Secondary is UP state. And Also AlwaysOn Availability Group node is in
Resolving state. And those databases are participating in AlwaysOn availability group in primary server , which is showing like (
Not synchronizing /Recovery pending). As you can see the below attachment sheet of SSMS screen shot. which has taken in Primary Server.
My Question is that in this situation ,
1)how i shall bring back online to my Quorum node. 2)After that how i shall bring back my Primary server from resolving to normal state.
I know that this is a one of the critical situation of troubleshooting in the life of DBA world. Even i have already went through the MSDN BOL WSFC Disaster Recovery through Forced Quorum and Perform a Forced Manual Failover of an Availability Group Even as per my DBA knowledge it is only solution through manual fail over to bring back online to quorum node.
Regarding in this regards, any suggestion will be appreciated.