{"id":7074,"date":"2016-02-06T16:30:31","date_gmt":"2016-02-06T15:30:31","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/"},"modified":"2016-02-06T16:30:31","modified_gmt":"2016-02-06T15:30:31","slug":"sql-server-alwayson-the-registry-is-also-important-for-availability-groups","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/","title":{"rendered":"SQL Server AlwaysOn : the registry is also important for availability groups"},"content":{"rendered":"<p>A couple of months ago, we experienced with my colleague <a href=\"http:\/\/dbi-services.com\/blog\/author\/nathan-courtine\/\" target=\"_blank\" rel=\"noopener noreferrer\">Nathan Courtine<\/a> a weird issue at one of our customers. This issue concerned an AlwaysOn availability group and more precisely to the WSFC cluster layout. I can\u2019t say strongly enough that the AlwaysOn availability group runs on the top of the WSFC and having a good understanding of the internal stuff can help a lot for troubleshooting.<\/p>\n<p>First of all, let me introduce the issue that began by an SQL Server alert and the error 35262 meaning that we potentially face an availability group failover. So the environment was pretty basic and consisted of several availability groups that run with SQL Server 2012 SP1 and hosted by several replicas. Furthermore, the SQL Server environment runs on the top of a WSFC that consist in two cluster nodes on the same subnet.<\/p>\n<p>The first investigation led us to conclude that a third party backup software was the root cause of availability group instability. In fact, during the backup time frame, the third party tool had frozen the concerned primary replica long enough to trigger a failover of the availability groups to the secondary cluster node. I also faced the same kind of issue which is described <a href=\"http:\/\/dbi-services.com\/blog\/sql-server-alwayson-and-availability-groups-session-timeout-parameter\/\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a>.<\/p>\n<p>However, the most interesting part of the story is not here. So keep reading\u2026 After the availability group\u2019s failover, the normal process would be to bring it online on the new primary replica as well as its respective resources on the WSFC side. However, that didn\u2019t happen in our case: the corresponding cluster resources failed over on the second cluster node but the WSFC service restarted continuously all the night until the customer decided to restart completely the node the morning after. We noticed a lot of related errors in the Windows error log as shown below:<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6972\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service.jpg\" alt=\"blog 76- 1- cluster failover registry - unexpected shutdown cluster service\" width=\"1058\" height=\"250\" \/><\/a><\/p>\n<p>Referring to the above errors, we may think first to an out of memory issue but after checking my colleague told me the problem was not there. In fact, there was enough memory on the concerned server (some gigabytes). Then we decided to take a look at the cluster log and we noticed some interesting information inside. Here one sample among others with the same pattern. Let&#8217;s focus on the records in bold.<\/p>\n<p><strong><em>00000624.00000ee0::2015\/10\/19-21:03:41.107 INFO\u00a0 [RCM] rcm::RcmGum::GroupMoveOperation(AAG_XXXX,2)<\/em><\/strong><\/p>\n<p><strong><em>00000624.000014d4::2015\/10\/19-21:03:56.875 INFO\u00a0 [RCM] Group move for &#8216;AAG_XXXX&#8217; has completed.<\/em><\/strong><\/p>\n<p><em>0000163c.000013a8::2015\/10\/19-21:03:56.721 INFO\u00a0 [RES] SQL Server Availability Group &lt;AAG_XXXX&gt;: [hadrag] Current SQL Instance is not part of Failover clustering<\/em><br \/>\n<em>0000163c.000013a8::2015\/10\/19-21:03:56.721 INFO\u00a0 [RES] SQL Server Availability Group: [hadrag] Starting Health Worker Thread<\/em><br \/>\n<em>0000163c.00001528::2015\/10\/19-21:03:56.730 INFO\u00a0 [RES] SQL Server Availability Group: [hadrag] XEvent session XXXX is created with RolloverCount 10, MaxFileSizeInMBytes 100, and LogPath &#8216;C:\\Program Files\\Microsoft SQL Server\\MSSQL11.XXXX\\MSSQL\\LOG\\&#8217;<\/em><br \/>\n<em>0000163c.00001528::2015\/10\/19-21:03:56.730 INFO\u00a0 [RES] SQL Server Availability Group: [hadrag] Extended Event logging is started<\/em><br \/>\n<em>0000163c.00001528::2015\/10\/19-21:03:56.730 INFO\u00a0 [RES] SQL Server Availability Group: [hadrag] Health worker started for instance XXXX\\XXXX<\/em><\/p>\n<p><em>00000624.000016d4::2015\/10\/19-21:03:56.884 INFO\u00a0 [RCM] rcm::RcmApi::AddPossibleOwner: (AAG_XXXX, 2)<\/em><em><br \/>\n00000624.000016d4::2015\/10\/19-21:03:56.884 INFO\u00a0 [RCM] rcm::RcmGum::AddPossibleOwner(AAG_XXXX,2)<br \/>\n<\/em><strong><em>00000624.000016d4::2015\/10\/19-21:03:56.886 ERR\u00a0\u00a0 [DM] Dm::Hive::PerformReplicatedOperation: STATUS_INSUFFICIENT_RESOURCES(c000009a)&#8217; because of &#8216;::NtRestoreKey( reinterpret_cast&lt;::HANDLE&gt;( hiveHandle.handle ), nullptr, RegistryOptions::RefreshHive)&#8217;<\/em><em><br \/>\n<\/em><em>00000624.000016d4::2015\/10\/19-21:03:56.886 ERR\u00a0\u00a0 Operation failed on a local hive (status = 1450)<\/em><em><br \/>\n<\/em><em>00000624.000016d4::2015\/10\/19-21:03:56.886 ERR\u00a0\u00a0 Operation failed on a local hive (status = 1450), executing OnStop<\/em><\/strong><em><br \/>\n00000624.000016d4::2015\/10\/19-21:03:56.886 INFO\u00a0 [DM]: Shutting down, so unloading the cluster database.<\/em><em><br \/>\n00000624.000016d4::2015\/10\/19-21:03:56.886 INFO\u00a0 [DM] Shutting down, so unloading the cluster database (waitForLock: false).<br \/>\n<\/em><strong><em>00000624.000016d4::2015\/10\/19-21:03:56.887 ERR\u00a0\u00a0 [DM] Error while restoring (refreshing) the hive: STATUS_INSUFFICIENT_RESOURCES(c000009a)<\/em><\/strong><\/p>\n<p>We can notice that the system has detected that the primary node is no more reachable and has performed a failover of the concerned availability group by using the rcm<strong><em>::RcmGum::GroupMoveOperation<\/em><\/strong> API. Moreover, let\u2019s have a look at the STATUS_INSUFFICIENT_RESOURCES message that is related to a cluster registry issue &#8211; <strong><em>NtRestoreKey( reinterpret_cast&lt;::HANDLE&gt;( hiveHandle.handle ), nullptr, RegistryOptions::RefreshHive<\/em><\/strong> .<\/p>\n<p><strong><em>RegistryOptions::RefreshHive<\/em><\/strong> is probably part of the internal registry process handled by the database manager itself. There is also an additional registry WFSC check-pointing process for non-cluster aware applications. Indeed, when a resource comes online, the checkpoint manager is responsible to synchronize the cluster registry hive between nodes and this is also the case with SQL Server FCI and important registry keys. You can get an idea of these registry keys replicated by the checkpoint manager by using the PowerShell cmdlet <strong><em>Get-Clustercheckpoint<\/em><\/strong> as follows:<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-3-cluster-failover-registry-checkpoint.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6973\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-3-cluster-failover-registry-checkpoint.jpg\" alt=\"blog 76- 3- cluster failover registry - checkpoint\" width=\"993\" height=\"230\" \/><\/a><\/p>\n<p>Let\u2019s have a quick idea of this process by adding a registry key named \u201ctest\u201d to my existing SQL Server FCI named SQL16CLUST2\\INST3.<\/p>\n<pre class=\"brush: powershell; gutter: true; first-line: 1\">Add-ClusterCheckpoint - ResourceName \u201cSQL Server (INST3)\u201d -RegistryCheckPoint \u201cSOFTWARE\\Microsoft\\Microsoft SQL Server\\MSSQL13.INST3\\test\u201d<\/pre>\n<p>You can see the new key added to the list of replicated registry keys by the checkpoint manager<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-4-cluster-failover-registry-checkpoint-new-key.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6974\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-4-cluster-failover-registry-checkpoint-new-key.jpg\" alt=\"blog 76- 4- cluster failover registry - checkpoint new key\" width=\"1000\" height=\"243\" \/><\/a><\/p>\n<p>You may test by yourself to verify if the registry is correctly replicated after initiating a failover of your SQL Server FCI or other role. Notice that in my case we used a FSW and the system will use a paxos tag to understand which node has the most up-to-date version of the cluster database.<\/p>\n<p>So let\u2019s go back to the issue. The billion dollar question here is why the\u00a0database manager\u00a0is not able to refresh correctly the cluster registry hive? To answer, we had to move on the registry side. I asked my colleague to get the size of the registry on this cluster node and here what he found:<\/p>\n<p><a href=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-2-cluster-failover-registry-registry-size.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-6976\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-2-cluster-failover-registry-registry-size.jpg\" alt=\"blog 76- 2- cluster failover registry - registry size\" width=\"660\" height=\"132\" \/><\/a><\/p>\n<p>Yes, you\u2019re not dreaming! The registry has roughly reached the total size of 9GB and it was exactly the root cause of our issue. I remembered to face the same issue in the past in other context and have read this very interesting technet <a href=\"http:\/\/blogs.technet.com\/b\/askperf\/archive\/2014\/10\/22\/unable-to-restart-server-due-to-registry-bloat-over-2gb.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">blog post<\/a>. Referring to this blog post, we know that the registry hive is limited to 2GB even on x64 systems. In the context of our customer, the registry was bloated with a lot of records related to the same issue:<\/p>\n<p><strong><em>Description: Detection of product &#8216;{A7037EB2-F953-4B12-B843-195F4D988DA1}&#8217;, feature &#8216;SQL_Tools_Ans&#8217;, Component &#8216;{0CECE655-2A0F-4593-AF4B-EFC31D622982}&#8217; failed. The resource&#8221; does not exist.<\/em><\/strong><\/p>\n<p>After some investigations, we found out a related<a href=\"https:\/\/support.microsoft.com\/en-us\/kb\/2793634\" target=\"_blank\" rel=\"noopener noreferrer\"> KB2793634<\/a> to solve it but unfortunately it was too late in our context. Indeed, we decided finally with the customer that the safest solution would be to perform a new fresh installation and applying the hotfix rather than attempting to clear the registry.<\/p>\n<p>I admit that this issue is the exception but for us it was a good opportunity to learn further about how the cluster registry and the checkpoint manager work. We\u2019ve seen that the registry check-pointing is an important part but often obscured in order to the failover cluster works properly.<\/p>\n<p>Happy clustering!<\/p>\n<p>By David Barbarin<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A couple of months ago, we experienced with my colleague Nathan Courtine a weird issue at one of our customers. This issue concerned an AlwaysOn availability group and more precisely to the WSFC cluster layout. I can\u2019t say strongly enough that the AlwaysOn availability group runs on the top of the WSFC and having a [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":7079,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,198],"tags":[466,464,523,84,738,51],"type_dbi":[],"class_list":["post-7074","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","category-database-management","tag-alwayson","tag-failover-cluster","tag-fci","tag-high-availability","tag-registry","tag-sql-server"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>SQL Server AlwaysOn : the registry is also important for availability groups<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"SQL Server AlwaysOn : the registry is also important for availability groups\" \/>\n<meta property=\"og:description\" content=\"A couple of months ago, we experienced with my colleague Nathan Courtine a weird issue at one of our customers. This issue concerned an AlwaysOn availability group and more precisely to the WSFC cluster layout. I can\u2019t say strongly enough that the AlwaysOn availability group runs on the top of the WSFC and having a [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-02-06T15:30:31+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1058\" \/>\n\t<meta property=\"og:image:height\" content=\"250\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Microsoft Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Microsoft Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\"},\"author\":{\"name\":\"Microsoft Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"headline\":\"SQL Server AlwaysOn : the registry is also important for availability groups\",\"datePublished\":\"2016-02-06T15:30:31+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\"},\"wordCount\":1141,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg\",\"keywords\":[\"AlwaysOn\",\"Failover cluster\",\"FCI\",\"High availability\",\"Registry\",\"SQL Server\"],\"articleSection\":[\"Database Administration &amp; Monitoring\",\"Database management\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\",\"name\":\"SQL Server AlwaysOn : the registry is also important for availability groups\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg\",\"datePublished\":\"2016-02-06T15:30:31+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg\",\"width\":1058,\"height\":250},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"SQL Server AlwaysOn : the registry is also important for availability groups\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4\",\"name\":\"Microsoft Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g\",\"caption\":\"Microsoft Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"SQL Server AlwaysOn : the registry is also important for availability groups","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/","og_locale":"en_US","og_type":"article","og_title":"SQL Server AlwaysOn : the registry is also important for availability groups","og_description":"A couple of months ago, we experienced with my colleague Nathan Courtine a weird issue at one of our customers. This issue concerned an AlwaysOn availability group and more precisely to the WSFC cluster layout. I can\u2019t say strongly enough that the AlwaysOn availability group runs on the top of the WSFC and having a [&hellip;]","og_url":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/","og_site_name":"dbi Blog","article_published_time":"2016-02-06T15:30:31+00:00","og_image":[{"width":1058,"height":250,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg","type":"image\/jpeg"}],"author":"Microsoft Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Team","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/"},"author":{"name":"Microsoft Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"headline":"SQL Server AlwaysOn : the registry is also important for availability groups","datePublished":"2016-02-06T15:30:31+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/"},"wordCount":1141,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg","keywords":["AlwaysOn","Failover cluster","FCI","High availability","Registry","SQL Server"],"articleSection":["Database Administration &amp; Monitoring","Database management"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/","url":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/","name":"SQL Server AlwaysOn : the registry is also important for availability groups","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg","datePublished":"2016-02-06T15:30:31+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/blog-76-1-cluster-failover-registry-unexpected-shutdown-cluster-service-1.jpg","width":1058,"height":250},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/sql-server-alwayson-the-registry-is-also-important-for-availability-groups\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"SQL Server AlwaysOn : the registry is also important for availability groups"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/bfab48333280d616e1170e7369df90a4","name":"Microsoft Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c44a1a792c059f24055763aa77d80a244467f6eef724a8bd13db8d4a350b7a4c?s=96&d=mm&r=g","caption":"Microsoft Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/microsoft-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7074","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=7074"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/7074\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/7079"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=7074"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=7074"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=7074"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=7074"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}