<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Replica Set on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/replica-set/</link>
    <description>Recent content in Replica Set 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/replica-set/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Snapshot Recovery of a MongoDB Replica Set on a Single FlashArray</title>
      <link>https://www.nocentino.com/posts/2026-11-17-mongodb-snapshot-recovery-single-flasharray/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.nocentino.com/posts/2026-11-17-mongodb-snapshot-recovery-single-flasharray/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been running MongoDB on Everpure FlashArray in my lab, and the first thing I wanted to prove is the simplest one. Can I snapshot an entire replica set while it&amp;rsquo;s taking writes, drop a database, and get everything back just by overwriting volumes?&lt;/p&gt;&#xA;&lt;p&gt;In this post, I&amp;rsquo;m going to show you exactly that: a three-member replica set, one &lt;code&gt;mongod&lt;/code&gt; per node, every member on volumes from the same FlashArray, four writers and an updater hammering away during the snapshot, and no &lt;code&gt;fsyncLock&lt;/code&gt;. If you&amp;rsquo;ve read my &lt;a href=&#34;https://www.nocentino.com/posts/2026-11-17-mongodb-on-everpure-why-it-matters&#34;&gt;intro to this series&lt;/a&gt;, this is the first hands-on post. If protection groups, the oplog, or crash consistency are new to you, the &lt;a href=&#34;https://www.nocentino.com/posts/2026-11-17-mongodb-on-everpure-why-it-matters#terms-in-this-series&#34;&gt;terms list&lt;/a&gt; in the intro defines them in plain words. Let&amp;rsquo;s go.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
