<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Replication on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/replication/</link>
    <description>Recent content in Replication on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 18 Aug 2026 05:00:00 -0500</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/replication/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Asynchronous Replication of Snapshots from an ActiveCluster Pod to a Third Array</title>
      <link>https://www.nocentino.com/posts/2026-08-18-async-replication-activecluster-pod-third-array/</link>
      <pubDate>Tue, 18 Aug 2026 05:00:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-08-18-async-replication-activecluster-pod-third-array/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been rebuilding my three-site SQL Server demo lab, and I ran into something I&amp;rsquo;ve wanted for a long time. If you&amp;rsquo;ve ever designed a SQL Server environment on ActiveCluster, you know the pattern: two FlashArrays running a synchronously replicated pod for zero RPO between sites, and a third array somewhere else for a longer retention, disaster recovery copy. The problem was that you couldn&amp;rsquo;t get the data to that third array directly from the pod. Protection groups inside a stretched pod simply couldn&amp;rsquo;t have an array target.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
