<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MongoDB on Everpure on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/mongodb-on-everpure/</link>
    <description>Recent content in MongoDB on Everpure on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2026 08:05:00 -0500</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/mongodb-on-everpure/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Where FlashBlade Fits When MongoDB Lives on FlashArray</title>
      <link>https://www.nocentino.com/posts/2026-11-17-mongodb-flashblade-logical-backups/</link>
      <pubDate>Tue, 17 Nov 2026 08:05:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-11-17-mongodb-flashblade-logical-backups/</guid>
      <description>&lt;p&gt;Every copy of MongoDB data I&amp;rsquo;ve made so far in this series lives on a FlashArray. The snapshots sit on the same array as the volumes they protect, and even the replicated ones land on another FlashArray as the same kind of block copy. That&amp;rsquo;s exactly what you want for fast recovery. It&amp;rsquo;s also the thing that nags at me. If every copy you have lives on the same kind of system as the live data, a bad day for that system is a bad day for your backups too. So I wanted a copy somewhere else, in a format that doesn&amp;rsquo;t care what storage produced it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Expanding a MongoDB Replica Set with Everpure Fusion</title>
      <link>https://www.nocentino.com/posts/2026-11-17-mongodb-expand-replica-set-everpure-fusion/</link>
      <pubDate>Tue, 17 Nov 2026 08:04:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-11-17-mongodb-expand-replica-set-everpure-fusion/</guid>
      <description>&lt;p&gt;So far in this series I&amp;rsquo;ve been rebuilding members on arrays I already had. In my &lt;a href=&#34;https://www.nocentino.com/posts/2026-11-17-mongodb-reseed-replica-between-flasharrays&#34;&gt;reseed post&lt;/a&gt;, I rebuilt &lt;code&gt;aen-mongo-06&lt;/code&gt; from a replicated snapshot of the primary. This time I wanted to grow the replica set onto a fourth array. That&amp;rsquo;s usually where you open a storage ticket, wait for someone to pick an array and carve some volumes, and then start an initial sync that copies every document over the network. Two waits, and the second one gets longer every time your database grows.&lt;/p&gt;</description>
    </item>
    <item>
      <title>When You Need fsyncLock: Restoring a MongoDB Replica Set from Local Snapshots on Every FlashArray</title>
      <link>https://www.nocentino.com/posts/2026-11-17-mongodb-app-consistent-replica-set-snapshots-flasharrays/</link>
      <pubDate>Tue, 17 Nov 2026 08:03:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-11-17-mongodb-app-consistent-replica-set-snapshots-flasharrays/</guid>
      <description>&lt;p&gt;In my &lt;a href=&#34;https://www.nocentino.com/posts/2026-11-17-mongodb-reseed-replica-between-flasharrays&#34;&gt;reseed post&lt;/a&gt;, I spent a lot of time convincing you that you &lt;strong&gt;don&amp;rsquo;t&lt;/strong&gt; need &lt;code&gt;fsyncLock&lt;/code&gt;. One crash-consistent snapshot of the primary, replicated to every array, rebuilt every secondary in the set, under load, with no pause in writes. That&amp;rsquo;s still what I reach for when I&amp;rsquo;m rebuilding members.&lt;/p&gt;&#xA;&lt;p&gt;Then I asked myself the obvious follow-up: what if I want to put &lt;strong&gt;every&lt;/strong&gt; member back to the same known moment, each one from &lt;strong&gt;its own array&amp;rsquo;s local snapshot&lt;/strong&gt;? That&amp;rsquo;s the one case in this series where I do reach for the lock. It&amp;rsquo;s also the Python version of my 2025 post on &lt;a href=&#34;https://www.nocentino.com/posts/2025-11-24-app-consistent-mongo-multi-array-snapshots&#34;&gt;app-consistent snapshots across multiple FlashArrays&lt;/a&gt;, this time for a replica set instead of a sharded cluster.&lt;/p&gt;</description>
    </item>
    <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 08:02:00 -0500</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>
    <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 08:01:00 -0500</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>
    <item>
      <title>Why Run MongoDB on Everpure FlashArray?</title>
      <link>https://www.nocentino.com/posts/2026-11-17-mongodb-on-everpure-why-it-matters/</link>
      <pubDate>Tue, 17 Nov 2026 08:00:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-11-17-mongodb-on-everpure-why-it-matters/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve spent a lot of years around SQL Server on shared storage, and lately I&amp;rsquo;ve been spending that time with MongoDB. The database engine couldn&amp;rsquo;t be more different, but the storage conversation sounds very familiar. How do I protect it? How do I grow it? How do I get another copy of it somewhere else, and how long is all of that going to take?&lt;/p&gt;&#xA;&lt;p&gt;This is the first post in a series where I run MongoDB replica sets on Everpure FlashArray in my lab, with the commands and the real output in every post. In this post, I&amp;rsquo;m going to show you why you&amp;rsquo;d run MongoDB this way at all: what MongoDB asks of storage, where disks inside every node start to hurt, what changes when the volumes come from a FlashArray, and a map of the rest of the series. There&amp;rsquo;s no lab output in this one, just the reasoning. Let&amp;rsquo;s go.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
