SQL2012 SP2 CU1 Availability Group database not synchronizing after applying February Microsoft patches

Question

Hi,
We are starting our monthly patching and have a situation with SQL2012 SP2 CU1 Availability Groups databases not synchronizing after patching the secondary replica. This seems a little like
http://support2.microsoft.com/kb/3033492/en-us which was for CU3 and CU4 builds. The dashboard on the Primary shows the secondary as not synchronizing. The errorlogs on both nodes show the connection
has recovered but the dashboard shows critical errors. This is running on Windows 2012.
Thanks
Chris

Answer 1

Lydia,
I am referring to MS15-009 to MS15-017 that came out on Tuesday. These are the only patches we have applied. On our two node Availability Group setup we had the patches applied to the secondary node and then it was restarted. It came up fine and SQL is running
as expected.
This is from the primary node errorlog:-
AlwaysOn Availability Groups connection with secondary database terminated for primary database 'XXX_DEVL' on the availability replica with Replica ID: {e6468c4d-9431-4052-88c0-07d3b3eb428c}. This is an informational message only. No user action is required.
A connection for availability group 'YYYYY50_AG' from availability replica 'YYYYY50AV' with id  [0E53235A-0FBB-4E18-8C40-A0D72F30C36A] to 'YYYYY50BV' with id [E6468C4D-9431-4052-88C0-07D3B3EB428C] has been successfully established.  This is an
informational message only. No user action is required.
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXX_DEVL' on the availability replica with Replica ID: {e6468c4d-9431-4052-88c0-07d3b3eb428c}. This is an informational message only. No user action is required.
On the secondary node errorlog:-
Skipping the default startup of database 'XXX_DEVL' because the database belongs to an availability group (Group ID:  65541). The database will be started by the availability group. This is an informational message only. No user action is required.
The state of the local availability replica in availability group 'YYYYY50_AG' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more
information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
AlwaysOn Availability Groups data movement for database 'XXX_DEVL' has been suspended for the following reason: "system" (Source ID 5; Source string: 'SUSPEND_FROM_RESTART'). To resume data movement on the database, you will need to resume the
database manually. For information about how to resume an availability database, see SQL Server Books Online.
Nonqualified transactions are being rolled back in database XXX_DEVL for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
AlwaysOn Availability Groups connection with primary database terminated for secondary database 'XXX_DEVL' on the availability replica with Replica ID: {0e53235a-0fbb-4e18-8c40-a0d72f30c36a}. This is an informational message only. No user action is required.
Now I see the suspend message. Running the select on sys.dm_exec_requests there are NO DB_STARTUP ones on either node or blocking.
Next action is probably to have the patches removed from the secondary node and see if all is well and then try patch one by one to see which one causes the issue.
Chris