<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Oplog on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/oplog/</link>
    <description>Recent content in Oplog on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/oplog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Replacing the MongoDB Replica Set Initial Sync with FlashArray Snapshots</title>
      <link>https://www.nocentino.com/posts/2026-11-17-mongodb-reseed-replica-between-flasharrays/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.nocentino.com/posts/2026-11-17-mongodb-reseed-replica-between-flasharrays/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://www.nocentino.com/posts/2026-11-17-mongodb-snapshot-recovery-single-flasharray&#34;&gt;last post&lt;/a&gt;, I restored every member of a replica set from one snapshot on the same array. In real life, you usually lose one member: a host dies, someone rebuilds the wrong VM, a member&amp;rsquo;s data gets damaged. And each member of a replica set is most likely on a different array. MongoDB rebuilds a member from nothing with an initial sync, the job every DBA dreads, and I wanted to see how much of that job I could hand off to the storage tier.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
