<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Borgbackup on Linux Café</title>
    <link>https://mrtomlinux.org/tags/borgbackup/</link>
    <description>Recent content in Borgbackup on Linux Café</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 08:23:50 +0200</lastBuildDate>
    <atom:link href="https://mrtomlinux.org/tags/borgbackup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How a Forgotten SSH Key Stopped My Nightly Off‑Site Borg Backup and the Quick Fix I Implemented</title>
      <link>https://mrtomlinux.org/post/2026-10-01-how-a-forgotten-ssh-key-stopped-my-nightly-of/</link>
      <pubDate>Thu, 01 Oct 2026 08:23:50 +0200</pubDate>
      <guid>https://mrtomlinux.org/post/2026-10-01-how-a-forgotten-ssh-key-stopped-my-nightly-of/</guid>
      <description>&lt;h2 id=&#34;the-night-i-lost-an-offsite-borg-backup&#34;&gt;The night I lost an off‑site Borg backup&lt;/h2&gt;&#xA;&lt;p&gt;I run a 24/7 home‑lab server that backs up my home directories to a remote NAS with Borg. The backup is triggered by a systemd timer that fires every night at 02:00 UTC. For months it worked flawlessly, but one morning the timer ran, the job logged “ssh: connect to host …: Permission denied”, and the backup vanished into the night. The culprit? A forgotten SSH key.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
