Standard

Posted by

Posted on

September 18, 2017

Posted under

AlwaysON

Comments

Leave a comment

AlwaysON – Working through Crashed Synchronous Secondary Replica

Environment

Blog29_1

-> JBSERVER2 Crashes. The Server is expected to be online after 2 days.

Blog32_2.PNG

-> Checking the SQL Server Management Studio and the Cluster Administrator,

Blog32_3

Blog32_4

-> JBSERVER3 which is an Asynchronous replica, will be changed to a Synchronous replica.

-> Removing the Crashed Replica from Availability group,

Blog32_5.PNG

Blog32_6

Blog32_7.PNG

-> Remove the Node JBSERVER2 from Cluster Administrator,

Blog32_8.PNG

Blog32_9

Blog32_10

-> Server JBSERVER2 comes online after the Rebuild. Lets Add it back to the Availability group.

-> Adding JBSERVER2 to the Failover Cluster,

Blog32_11.PNG

Blog32_12.PNG

Blog32_13.PNG

-> Adding JBSERVER2 as a Replica,

Blog32_14.PNG

Blog32_15.PNG

Blog32_16.PNG

Blog32_17.PNG

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided “AS IS” with no warranties, and confers no rights.

Leave a Reply