<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>FlashBlade on Anthony Nocentino&#39;s Blog</title>
    <link>https://www.nocentino.com/categories/flashblade/</link>
    <description>Recent content in FlashBlade 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/categories/flashblade/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 00:00:00 +0000</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>
  </channel>
</rss>
