<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Failover on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/failover/</link>
    <description>Recent content in Failover on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 19 Apr 2026 00:00:00 -0500</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/failover/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Walking Through a Planned Failover: SQL Server Availability Groups on Kubernetes</title>
      <link>https://www.nocentino.com/posts/2026-04-19-planned-failover-walkthrough-sql-server-kubernetes-operator/</link>
      <pubDate>Sun, 19 Apr 2026 00:00:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-04-19-planned-failover-walkthrough-sql-server-kubernetes-operator/</guid>
      <description>&lt;p&gt;When building the &lt;a href=&#34;https://github.com/nocentino/sql-on-k8s-operator&#34; target=&#34;_blank&#34; rel=&#34;noopener external&#34;&gt;sql-on-k8s-operator&lt;/a&gt;, I wanted to make sure it could handle both planned and unplanned failovers. The easy case is a planned failover, where you deliberately move the primary role to another replica. The harder case is an unplanned failover, where the primary pod just disappears. The operator needs to handle both.&lt;/p&gt;&#xA;&lt;p&gt;I recently ran a full planned failover rotation on a three-replica SQL Server Availability Group managed by &lt;a href=&#34;https://github.com/nocentino/sql-on-k8s-operator&#34; target=&#34;_blank&#34; rel=&#34;noopener external&#34;&gt;sql-on-k8s-operator&lt;/a&gt;, and I want to show you exactly what happens inside SQL Server and the operator during each hop. If you&amp;rsquo;ve been following my &lt;a href=&#34;https://www.nocentino.com/posts/2026-04-12-introducing-sql-on-k8s-operator/&#34;&gt;Introducing the SQL Server on Kubernetes Operator&lt;/a&gt; post, this is the logical next step: what does the error log actually look like during a planned failover, what does the operator do in response, and how long does the whole thing take?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
