<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Borg on Linux Café</title>
    <link>https://mrtomlinux.org/tags/borg/</link>
    <description>Recent content in Borg on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 26 May 2026 08:10:41 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/borg/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Recovering from a Failed Borg Backup Repository: Lessons Learned from a Homelab Mishap</title>
      <link>https://mrtomlinux.org/post/2026-05-26-recovering-from-a-failed-borg-backup-reposito/</link>
      <pubDate>Tue, 26 May 2026 08:10:41 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-05-26-recovering-from-a-failed-borg-backup-reposito/</guid>
      <description>&lt;h2 id=&#34;introduction-to-borg-backup&#34;&gt;Introduction to Borg Backup&lt;/h2&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve learned the hard way that having a reliable backup system is crucial for any homelab setup. Borg Backup has been my go-to tool for deduplicating backups, and it&amp;rsquo;s served me well - until I recently encountered a failed repository. This experience taught me some valuable lessons about recovery and prevention.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-borg-backup-repositories&#34;&gt;Understanding Borg Backup Repositories&lt;/h2&gt;&#xA;&lt;p&gt;Before diving into the recovery process, it&amp;rsquo;s essential to grasp how Borg Backup repositories work. A repository is the central storage location for all your backups, where Borg stores deduplicated data. When you create a repository, Borg initializes it with a unique ID, ensuring data integrity. I&amp;rsquo;ve seen this go wrong when the repository index gets corrupted, so it&amp;rsquo;s crucial to understand how it works.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
