Where Did My Availability Group (AG) Go?

Published Jan 15 2019 02:32 PM 76 Views
Microsoft
First published on MSDN on Jul 16, 2012

I ran into an issue where the AG was no longer present on a specific node of my cluster but I had NOT dropped the AG from another node in the cluster.  ( http://blogs.msdn.com/b/psssql/archive/2012/06/13/how-it-works-drop-availability-group-behavior... )

Note: Use the XEvent files captured in the LOG directory to confirm that a DDL command was not issued.

There are protection mechanisms built into the AlwaysOn Availability groups to protect the data.  In this specific case I had the registry on Node 1 become damaged.  In doing so the cluster registry no longer matched the SQL Server metadata and my AG is removed from the node.

Note:  The database(s) still exist on Node 1 but they are no longer joined to the 'My AG' availability group. This protects the data on Node 1 from unexpected/mis-configured changes.

It is recommended that you keep the following backups for proper restore of the Availability Group configuration.

Bob Dorr -  Principal SQL Server Escalation Engineer

%3CLINGO-SUB%20id%3D%22lingo-sub-317130%22%20slang%3D%22en-US%22%3EWhere%20Did%20My%20Availability%20Group%20(AG)%20Go%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-317130%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Jul%2016%2C%202012%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EI%20ran%20into%20an%20issue%20where%20the%20AG%20was%20no%20longer%20present%20on%20a%20specific%20node%20of%20my%20cluster%20but%20I%20had%20NOT%20dropped%20the%20AG%20from%20another%20node%20in%20the%20cluster.%26nbsp%3B%20(%20%3CA%20href%3D%22http%3A%2F%2Fblogs.msdn.com%2Fb%2Fpsssql%2Farchive%2F2012%2F06%2F13%2Fhow-it-works-drop-availability-group-behaviors.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Fblogs.msdn.com%2Fb%2Fpsssql%2Farchive%2F2012%2F06%2F13%2Fhow-it-works-drop-availability-group-behaviors.aspx%20%3C%2FA%3E%20)%3C%2FP%3E%0A%20%20%3CP%3E%3CSTRONG%3E%20Note%3A%20%3C%2FSTRONG%3E%20%3CEM%3E%20Use%20the%20XEvent%20files%20captured%20in%20the%20LOG%20directory%20to%20confirm%20that%20a%20DDL%20command%20was%20not%20issued.%20%3C%2FEM%3E%3C%2FP%3E%0A%20%20%3CP%3EThere%20are%20protection%20mechanisms%20built%20into%20the%20AlwaysOn%20Availability%20groups%20to%20protect%20the%20data.%26nbsp%3B%20In%20this%20specific%20case%20I%20had%20the%20registry%20on%20Node%201%20become%20damaged.%26nbsp%3B%20In%20doing%20so%20the%20cluster%20registry%20no%20longer%20matched%20the%20SQL%20Server%20metadata%20and%20my%20AG%20is%20removed%20from%20the%20node.%3C%2FP%3E%0A%20%20%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F67174iA79BE20A965F53BD%22%20%2F%3E%3C%2FP%3E%0A%20%20%3CP%3E%3CSTRONG%3E%20Note%3A%26nbsp%3B%20The%20database(s)%20still%20exist%20on%20Node%201%20but%20they%20are%20no%20longer%20joined%20to%20the%20'My%20AG'%20availability%20group.%20%3C%2FSTRONG%3E%20This%20protects%20the%20data%20on%20Node%201%20from%20unexpected%2Fmis-configured%20changes.%3C%2FP%3E%0A%20%20%3CP%3E%3CSTRONG%3E%20It%20is%20recommended%20that%20you%20keep%20the%20following%20backups%20for%20proper%20restore%20of%20the%20Availability%20Group%20configuration.%20%3C%2FSTRONG%3E%3C%2FP%3E%0A%20%20%3CUL%3E%0A%20%20%20%3CLI%3EWindows%20System%20State%20-%20%3CA%20href%3D%22http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc771973.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20http%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fcc771973.aspx%20%3C%2FA%3E%3C%2FLI%3E%0A%20%20%20%3CLI%3ET-SQL%20Scripted%20T-SQL%20Availability%20Group%3C%2FLI%3E%0A%20%20%3C%2FUL%3E%0A%20%20%3CP%3E%3C%2FP%3E%0A%20%20%3CP%3EBob%20Dorr%20-%26nbsp%3B%20Principal%20SQL%20Server%20Escalation%20Engineer%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-317130%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jul%2016%2C%202012%20I%20ran%20into%20an%20issue%20where%20the%20AG%20was%20no%20longer%20present%20on%20a%20specific%20node%20of%20my%20cluster%20but%20I%20had%20NOT%20dropped%20the%20AG%20from%20another%20node%20in%20the%20cluster.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-317130%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHigh%20Availability%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jan 15 2019 02:32 PM
Updated by: