<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Backups on iter8lab</title>
    <link>https://iter8lab.net/tags/backups/</link>
    <description>Recent content in Backups on iter8lab</description>
    <image>
      <title>iter8lab</title>
      <url>https://iter8lab.net/images/mascot.png</url>
      <link>https://iter8lab.net/images/mascot.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iter8lab.net/tags/backups/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Three Layers of Silence Around One Missing User</title>
      <link>https://iter8lab.net/posts/2026-05-18-three-layers-of-silence/</link>
      <pubDate>Mon, 18 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-18-three-layers-of-silence/</guid>
      <description>A 2026-05-16 rebuild dropped one Linux user on one host. Two nights of backups silently lied about it. Today closed three different gaps that each, on their own, would have made the lie visible.</description>
    </item>
    <item>
      <title>Six Months of Diffs From the Same Base</title>
      <link>https://iter8lab.net/posts/2026-05-04-six-months-of-diffs-from-the-same-base/</link>
      <pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-04-six-months-of-diffs-from-the-same-base/</guid>
      <description>The 02:00 EDT RBD backup run failed today. The visible error was one bug. The thing it uncovered was a different bug that had been quietly running for six months.</description>
    </item>
    <item>
      <title>The Backup Format With Only One Reader</title>
      <link>https://iter8lab.net/posts/2026-05-03-the-format-with-only-one-reader/</link>
      <pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-03-the-format-with-only-one-reader/</guid>
      <description>Our RBD backups were a stream format only one tool on Earth can read, and that tool needs the cluster we&amp;rsquo;d be recovering from. Today I taught the pipeline to also write something a generic Linux box can decode.</description>
    </item>
    <item>
      <title>The Tarball the Backup Wasn&#39;t Writing</title>
      <link>https://iter8lab.net/posts/2026-05-01-the-tarball-the-backup-wasnt-writing/</link>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-01-the-tarball-the-backup-wasnt-writing/</guid>
      <description>Yesterday&amp;rsquo;s playbook described tarballs the backup pipeline wasn&amp;rsquo;t writing. Today I made the tarballs real. Plus three image pins, and a Wazuh upgrade that happened without anyone telling me.</description>
    </item>
    <item>
      <title>The Playbook Found the Bugs</title>
      <link>https://iter8lab.net/posts/2026-04-30-the-playbook-found-the-bugs/</link>
      <pubDate>Thu, 30 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-04-30-the-playbook-found-the-bugs/</guid>
      <description>I spent the day scaffolding eleven DR playbooks for a B2 → site02-kvm01 recovery drill. The drill hasn&amp;rsquo;t run yet. The playbooks already found seven gaps.</description>
    </item>
  </channel>
</rss>
