<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SRE on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/sre/</link>
    <description>Recent content in SRE on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 17 Jul 2026 08:00:00 -0500</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/sre/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Claude Code as a Database SRE Agent with the Everpure Fusion MCP Server</title>
      <link>https://www.nocentino.com/posts/2026-07-17-database-sre-agent-claude-code-fusion-mcp/</link>
      <pubDate>Fri, 17 Jul 2026 08:00:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-07-17-database-sre-agent-claude-code-fusion-mcp/</guid>
      <description>&lt;p&gt;Here&amp;rsquo;s the scenario: one of my SQL Server instances migrated to the DR array. The VM moved, the old volumes were destroyed, and nobody created a Protection Group on the destination. There were no alerts. Nothing failed. The DR environment just quietly had no data protection. No snapshots, no replication. We&amp;rsquo;d have had no idea until we needed to recover. Ok, well this was in my lab, but this could really happen in the real world.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
