<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Everpure Fusion on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/tags/everpure-fusion/</link>
    <description>Recent content in Everpure Fusion on Anthony Nocentino&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 04 Jun 2026 05:00:00 -0500</lastBuildDate>
    <atom:link href="https://www.nocentino.com/tags/everpure-fusion/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Crash-Consistent MongoDB Snapshot and Restore with Everpure Fusion</title>
      <link>https://www.nocentino.com/posts/2026-06-04-mongodb-snapshot-restore-flasharray-fusion/</link>
      <pubDate>Thu, 04 Jun 2026 05:00:00 -0500</pubDate>
      <guid>https://www.nocentino.com/posts/2026-06-04-mongodb-snapshot-restore-flasharray-fusion/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve been working on a project that combines two things I spend a lot of time with: MongoDB sharded clusters and Everpure FlashArrays. The goal is a production-grade backup and restore solution that avoids &lt;code&gt;mongodump&lt;/code&gt;, doesn&amp;rsquo;t require &lt;a href=&#34;https://www.nocentino.com/posts/2025-11-24-app-consistent-mongo-multi-array-snapshots&#34;&gt;&lt;code&gt;fsyncLock&lt;/code&gt;&lt;/a&gt;, and scales across as many arrays as your cluster needs without any code changes. In this post I&amp;rsquo;m walking through the complete workflow (snapshot, disaster simulation, restore, and verification) running against a real 3-node sharded cluster with data spread across 3 independent FlashArrays, all managed through a single &lt;a href=&#34;https://www.everpuredata.com/products/automation-orchestration.html&#34; target=&#34;_blank&#34; rel=&#34;noopener external&#34;&gt;Everpure Fusion&lt;/a&gt; gateway connection.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
