<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Restic on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/restic/</link>
    <description>Recent content in Restic on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 21 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/restic/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Backup Repository Servers: Kopia Server vs Restic Rest-Server vs Borg Backup Server</title>
      <link>https://www.pistack.xyz/posts/2026-05-24-self-hosted-backup-repository-servers-kopia-restic-borg/</link>
      <pubDate>Thu, 21 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-24-self-hosted-backup-repository-servers-kopia-restic-borg/</guid>
      <description>&lt;p&gt;Deduplicating backup tools like Kopia, Restic, and Borg Backup are among the most popular self-hosted data protection solutions. But these clients need somewhere to store their backup data. While they support cloud storage (S3, B2, GCS), running a self-hosted backup repository server gives you complete control over your backup data, eliminates cloud storage fees, and keeps all backups within your network perimeter. In this guide, we compare three self-hosted repository server options: &lt;strong&gt;Kopia Server&lt;/strong&gt;, &lt;strong&gt;Restic Rest-Server&lt;/strong&gt;, and &lt;strong&gt;Borg Backup Server&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
