<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>backups · Alex Moreno</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/tags/backups/</link><description>Alex Moreno writes about developer tools, calm software and the occasional home-lab adventure.</description><generator>Hugo</generator><language>en-US</language><managingEditor>hello@example.org (Alex Moreno)</managingEditor><lastBuildDate>Sat, 18 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/tags/backups/index.xml" rel="self" type="application/rss+xml"/><item><title>Home lab, part 3: backups that actually restore</title><link>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/home-lab-part-3-backups/</link><pubDate>Sat, 18 Apr 2026 00:00:00 +0000</pubDate><guid>https://danielsada.github.io/hugo-breeze-plasma-inspired-theme/blog/home-lab-part-3-backups/</guid><description>&lt;p&gt;The first two parts were about &lt;em&gt;running&lt;/em&gt; things. This one is about getting them back.&lt;/p&gt;&#10;&lt;h2 id="the-rule"&gt;The rule&lt;a class="anchor" href="#the-rule" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Every backup job has a matching restore job, and the restore job runs on a schedule. If the restore fails, I get an email, the same way I would if the backup failed.&lt;/p&gt;&#10;&lt;h2 id="the-setup"&gt;The setup&lt;a class="anchor" href="#the-setup" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;ul&gt;&#10;&lt;li&gt;Nightly snapshots of every service&amp;rsquo;s data directory with &lt;code&gt;restic&lt;/code&gt;.&lt;/li&gt;&#10;&lt;li&gt;A second copy on an external disk that lives in a drawer at a friend&amp;rsquo;s house (rotated monthly).&lt;/li&gt;&#10;&lt;li&gt;A monthly job that restores the latest snapshot into a scratch VM and runs each service&amp;rsquo;s health check against it.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-bash" data-lang="bash"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;restic restore latest --target /srv/restore-test&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;docker compose -f /srv/restore-test/compose.yaml up -d&#10;&lt;/span&gt;&lt;/span&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;curl --fail http://localhost:8080/healthz&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h2 id="what-it-caught"&gt;What it caught&lt;a class="anchor" href="#what-it-caught" aria-label="Link to this section"&gt;#&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;In the first three months the restore test failed twice: once because a database dump was taken mid-write, and once because a config file lived outside the backed-up directory. Neither would have shown up until the day I needed them.&lt;/p&gt;</description></item></channel></rss>