<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Snapshots - vo.rs</title><link>https://vo.rs/tags/snapshots/</link><description>Latest from the Snapshots desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Sun, 22 Oct 2023 15:49:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/snapshots/" rel="self" type="application/rss+xml"/><item><title>Snapshots Are Not Backups: A Cautionary Tale</title><link>https://vo.rs/story/snapshots-are-not-backups-a-cautionary-tale/</link><description>&lt;p&gt;For about two years I told anyone who would listen that I had backups sorted. I ran ZFS, I took hourly snapshots, I kept a fortnight of them, and I had personally watched myself roll back a botched database migration in under a minute by cloning a snapshot from an hour earlier. I felt smug. I had automated point-in-time recovery, it worked, and I stopped thinking about the problem.&lt;/p&gt;
&lt;p&gt;Then the pool died, and it took every last snapshot with it, and I learned the difference between a snapshot and a backup the way most people learn it: at 11pm, with a cold feeling in my stomach, staring at a &lt;code&gt;zpool status&lt;/code&gt; output I did not want to be true. This is that story, and the fix that came out of it, because the mistake I made is the single most common one I see in homelabs that think they are safe.&lt;/p&gt;</description><pubDate>Sun, 22 Oct 2023 15:49:00 +0000</pubDate></item></channel></rss>