<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Duplicity on ads' corner</title><link>https://andreas.scherbaum.la/tags/duplicity/</link><description>Recent content in Duplicity on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 27 Dec 2020 23:47:00 +0100</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/duplicity/index.xml" rel="self" type="application/rss+xml"/><item><title>Restic backup</title><link>https://andreas.scherbaum.la/post/2020-12-27_restic-backup/</link><pubDate>Sun, 27 Dec 2020 23:47:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-12-27_restic-backup/</guid><description>&lt;p&gt;Was asked quite a few times how I do my backups with &lt;em&gt;Restic&lt;/em&gt;.&lt;/p&gt;&#10;&lt;p&gt;For more than 10 years I was using &amp;ldquo;&lt;a href="https://github.com/andreasscherbaum/duplicity-backup"&gt;Duplicity&lt;/a&gt;&amp;rdquo; for backups, but in 2019 I changed to &lt;a href="https://restic.net/"&gt;Restic&lt;/a&gt;. The main reason for the change was that &lt;em&gt;Duplicity&lt;/em&gt; still can&amp;rsquo;t handle &amp;ldquo;Big Data&amp;rdquo;, as in: larger directories. In 2009 someone opened an &lt;a href="https://bugs.launchpad.net/duplicity/+bug/385495"&gt;issue&lt;/a&gt; on the &lt;em&gt;Duplicity&lt;/em&gt; bugtracker, and this problem still exists as of today. For about two years I was shifting around the problem, excluding files, trying to make the sigfile smaller. But at some point I decided that it is enough and I need to change the tool.&lt;/p&gt;</description></item><item><title>Restic upgrade on Debian Buster</title><link>https://andreas.scherbaum.la/post/2020-03-27_restic-upgrade-on-debian-buster/</link><pubDate>Fri, 27 Mar 2020 21:29:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-03-27_restic-upgrade-on-debian-buster/</guid><description>&lt;p&gt;A while ago I switched backups from &lt;a href="https://duplicity.gitlab.io//"&gt;Duplicity&lt;/a&gt; to &lt;a href="https://restic.net/"&gt;Restic&lt;/a&gt;. About time: I was using &lt;em&gt;Duplicity&lt;/em&gt; for many years (I think I started using it around 2010, long before &lt;em&gt;Restic&lt;/em&gt; became available) and it served me well. But recently I ran into more and more issues, especially with archives getting larger and larger. There is an 11 years old open bug in the Duplicity bugtracker, which describes a &lt;a href="https://bugs.launchpad.net/duplicity/+bug/385495"&gt;showstopper for backing up larger archives&lt;/a&gt;. And it doesn&amp;rsquo;t look like this will be solved anytime soon. Therefore it was time for something new.&lt;/p&gt;&#10;&lt;p&gt;Since I&amp;rsquo;m rolling out my backups with &lt;a href="https://andreas.scherbaum.la/categories/ansible"&gt;Ansible&lt;/a&gt;, it was relatively easy to create a set of scripts for &lt;em&gt;Restic&lt;/em&gt; which use almost the same infrastructure as the old Duplicity backups. That works as expected on all our laptops. But the &lt;a href="https://andreas.scherbaum.la/categories/raspberry-pi"&gt;Raspberry Pi&lt;/a&gt;, which does the fileserver backups, seem to had a problem. Backups took way longer than before, jumped from 30-60 minutes (depending on the amount of changes) to constantly around 10 hours.&lt;/p&gt;</description></item></channel></rss>