<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Deduplication - vo.rs</title><link>https://vo.rs/tags/deduplication/</link><description>Latest from the Deduplication desk at vo.rs.</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 21 May 2024 10:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/deduplication/" rel="self" type="application/rss+xml"/><item><title>Kopia: The Backup Tool That Deduplicates Everything</title><link>https://vo.rs/story/kopia-the-backup-tool-that-deduplicates-everything/</link><description>&lt;p&gt;I ran Restic for two years before I looked seriously at Kopia, and the thing that finally moved me was not a benchmark, it was a support ticket I never had to write. A snapshot policy had quietly evolved over months — different retention on different machines, different exclude lists nobody remembered setting — and when I went looking for what was actually configured, Restic had no answer beyond &amp;ldquo;whatever flags you happened to type last time.&amp;rdquo; Kopia keeps that configuration as a first-class, inspectable object. That single difference changed how I think about backup tooling: the policy is the product, not the command line.&lt;/p&gt;</description><pubDate>Tue, 21 May 2024 10:00:00 +0000</pubDate></item></channel></rss>