<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Backups done right! on restic</title>
    <link>https://restic.net/</link>
    <description>Recent content in Backups done right! on restic</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Sep 2025 20:36:00 +0200</lastBuildDate>
    <atom:link href="https://restic.net/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Restic 0.18.1 Released</title>
      <link>https://restic.net/blog/2025-09-21/restic-0.18.1-released/</link>
      <pubDate>Sun, 21 Sep 2025 20:36:00 +0200</pubDate>
      <guid>https://restic.net/blog/2025-09-21/restic-0.18.1-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.18.1&#34;&gt;restic 0.18.1&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This is a bug fix release. Most notably, it resolves a crash when using &lt;code&gt;backup --stdin-filename&lt;/code&gt; with directory paths and another crash that could occur when directories are removed during backup operations. Support for local repositories stored on a filesystem that does not support &lt;code&gt;chmod&lt;/code&gt; (such as CIFS or WebDAV mounted via FUSE) has been restored.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.18.1&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>REST-server 0.14.0 released</title>
      <link>https://restic.net/blog/2025-05-31/rest-server-0.14.0-released/</link>
      <pubDate>Sat, 31 May 2025 22:35:00 +0200</pubDate>
      <guid>https://restic.net/blog/2025-05-31/rest-server-0.14.0-released/</guid>
      <description>&lt;p&gt;We have just released &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.14.0&#34;&gt;REST-server 0.14.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release corrects permissions of the &lt;code&gt;.htpasswd&lt;/code&gt; file created by the Docker container when one does not already exist. The permissions of existing &lt;code&gt;.htpasswd&lt;/code&gt; files, which were previously created world-readable, must be manually changed if relevant in your setup.&lt;/p&gt;&#xA;&lt;p&gt;In addition, REST-server adds support for proxy-based authentication and uses hardened TLS settings. Due to dependency updates, REST-server now requires Go 1.23 to build.&lt;/p&gt;&#xA;&lt;p&gt;Please see the &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.14.0&#34;&gt;changelog&lt;/a&gt; for more specific information!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.18.0 Released</title>
      <link>https://restic.net/blog/2025-03-27/restic-0.18.0-released/</link>
      <pubDate>Thu, 27 Mar 2025 20:41:00 +0100</pubDate>
      <guid>https://restic.net/blog/2025-03-27/restic-0.18.0-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.18.0&#34;&gt;restic 0.18.0&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release brings a large number of improvements, many of which have been contributed by our community. Thank you to everyone who contributed to this release, whether through providing input, testing, contributing code changes, or helping with support in the forum!&lt;/p&gt;&#xA;&lt;p&gt;The most important changes are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Mitigation for a potential attack on the content-defined chunking algorithm used by restic. The attack does not let an attacker decrypt data, but could in very specific circumstances allow an attacker to determine whether a large file, fully known to the attacker, is present in the repository. We consider the chance of a practical attack to be very low, but nonetheless implement protection against it. See this &lt;a href=&#34;https://github.com/restic/restic/issues/5291#issuecomment-2746146193&#34;&gt;post&lt;/a&gt; for details on the attack and mitigation.&lt;/li&gt;&#xA;&lt;li&gt;On Windows and macOS, restic now requires at least Windows 10, Windows Server 2016 or macOS 11 Big Sur. In addition, restic no longer supports TLS versions before TLS 1.2. This is due to dependencies needing Go 1.23 which is now used to build restic.&lt;/li&gt;&#xA;&lt;li&gt;JSON support for the &lt;code&gt;check&lt;/code&gt; and &lt;code&gt;tag&lt;/code&gt; commands. Exit codes are now also included in JSON output. See the &lt;a href=&#34;https://restic.readthedocs.io/en/stable/075_scripting.html#json-output&#34;&gt;JSON output&lt;/a&gt; documentation for more information.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Other notable changes include:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.17.3 Released</title>
      <link>https://restic.net/blog/2024-11-08/restic-0.17.3-released/</link>
      <pubDate>Fri, 08 Nov 2024 00:00:00 +0100</pubDate>
      <guid>https://restic.net/blog/2024-11-08/restic-0.17.3-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.17.3&#34;&gt;restic 0.17.3&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This patch release fixes a couple of bugs on Windows related to backing up metadata on removable disks and extended attributes with VSS. It also fixes handling of broken SFTP connections, enables &lt;code&gt;--no-lock&lt;/code&gt; for &lt;code&gt;prune --dry-run&lt;/code&gt; and works around a problem when browsing FUSE-T mounted repositories.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.17.3&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.17.2 Released</title>
      <link>https://restic.net/blog/2024-10-27/restic-0.17.2-released/</link>
      <pubDate>Sun, 27 Oct 2024 16:55:00 +0100</pubDate>
      <guid>https://restic.net/blog/2024-10-27/restic-0.17.2-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.17.2&#34;&gt;restic 0.17.2&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This patch release is mainly to fix a problem on Windows where files with the type &lt;code&gt;irregular&lt;/code&gt; could mistakenly be included in snapshots, causing error messages. Once having upgraded to restic 0.17.2, this can be fixed for existing snapshots by running &lt;code&gt;restic repair snapshots --forget&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.17.2&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.17.1 Released</title>
      <link>https://restic.net/blog/2024-09-05/restic-0.17.1-released/</link>
      <pubDate>Thu, 05 Sep 2024 21:40:00 +0200</pubDate>
      <guid>https://restic.net/blog/2024-09-05/restic-0.17.1-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.17.1&#34;&gt;restic 0.17.1&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release contains various bug fixes and small enhancements. The most important ones are the following:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The backup command now also stores files and directories for which some metadata could not be retrieved.&lt;/li&gt;&#xA;&lt;li&gt;On Windows several backup errors have been fixed. In particular volumes and network shares that do not support extended attributes can be backed up again.&lt;/li&gt;&#xA;&lt;li&gt;The JSON output of the backup and restore command now properly include the error message.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.17.1&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.17.0 Released</title>
      <link>https://restic.net/blog/2024-07-26/restic-0.17.0-released/</link>
      <pubDate>Fri, 26 Jul 2024 15:08:00 +0200</pubDate>
      <guid>https://restic.net/blog/2024-07-26/restic-0.17.0-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.17.0&#34;&gt;restic 0.17.0&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;After almost a year of hard work, this release brings a lot of improvements, of which the main highlights are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Highly improved &lt;a href=&#34;https://restic.readthedocs.io/en/stable/050_restore.html&#34;&gt;&lt;code&gt;restore&lt;/code&gt;&lt;/a&gt; command, now supporting &lt;a href=&#34;https://restic.readthedocs.io/en/stable/050_restore.html#dry-run&#34;&gt;dry-run&lt;/a&gt;, &lt;a href=&#34;https://restic.readthedocs.io/en/stable/050_restore.html#restoring-in-place&#34;&gt;in-place restore&lt;/a&gt; with different overwrite modes and a &lt;a href=&#34;https://restic.readthedocs.io/en/stable/050_restore.html#delete-files-not-in-snapshot&#34;&gt;delete&lt;/a&gt; option.&lt;/li&gt;&#xA;&lt;li&gt;Resumable and optimized &lt;a href=&#34;https://restic.readthedocs.io/en/stable/060_forget.html&#34;&gt;&lt;code&gt;prune&lt;/code&gt;&lt;/a&gt; command, now using up to 60% less memory and being less write-intensive.&lt;/li&gt;&#xA;&lt;li&gt;Ability to &lt;a href=&#34;https://restic.readthedocs.io/en/stable/040_backup.html#skip-creating-snapshots-if-unchanged&#34;&gt;skip snapshot creation if nothing changed&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Support for &lt;a href=&#34;https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#repositories-with-empty-password&#34;&gt;repositories with empty password&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Support for &lt;a href=&#34;https://restic.readthedocs.io/en/stable/050_restore.html#restore-using-mount&#34;&gt;FUSE-T on macOS&lt;/a&gt;.&lt;/li&gt;&#xA;&lt;li&gt;Support for &lt;a href=&#34;https://restic.readthedocs.io/en/stable/045_working_with_repos.html#listing-all-snapshots&#34;&gt;size&lt;/a&gt; and &lt;a href=&#34;https://restic.readthedocs.io/en/stable/075_scripting.html#summary&#34;&gt;summary&lt;/a&gt; statistics in snapshots.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Other notable mentions are:&lt;/p&gt;</description>
    </item>
    <item>
      <title>REST-server 0.13.0 released</title>
      <link>https://restic.net/blog/2024-07-26/rest-server-0.13.0-released/</link>
      <pubDate>Fri, 26 Jul 2024 11:30:00 +0200</pubDate>
      <guid>https://restic.net/blog/2024-07-26/rest-server-0.13.0-released/</guid>
      <description>&lt;p&gt;We have just released &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.13.0&#34;&gt;REST-server 0.13.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release of REST-server supports listening on unix sockets and also handles signals better than previous releases. Due to dependency updates REST-server now requires Go 1.18 to build.&lt;/p&gt;&#xA;&lt;p&gt;Please see the &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.13.0&#34;&gt;changelog&lt;/a&gt; for more specific information!&lt;/p&gt;&#xA;&lt;p&gt;Please let us know what you think in the forum post linked below!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.16.5 Released</title>
      <link>https://restic.net/blog/2024-07-01/restic-0.16.5-released/</link>
      <pubDate>Mon, 01 Jul 2024 21:00:00 +0200</pubDate>
      <guid>https://restic.net/blog/2024-07-01/restic-0.16.5-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.5&#34;&gt;restic 0.16.5&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release updates a few potentially vulnerable dependencies.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.5&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! To get help or provide feedback, please write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.16.4 Released</title>
      <link>https://restic.net/blog/2024-02-04/restic-0.16.4-released/</link>
      <pubDate>Sun, 04 Feb 2024 00:00:00 +0100</pubDate>
      <guid>https://restic.net/blog/2024-02-04/restic-0.16.4-released/</guid>
      <description>&lt;p&gt;A new patch release of restic 0.16 has now been released, &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.4&#34;&gt;restic 0.16.4&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release works around and improves detection of a bug in the compression library used by restic. The resulting issue only happens when using restic 0.16.3 and the &lt;code&gt;max&lt;/code&gt; compression level (the default &lt;code&gt;auto&lt;/code&gt; and &lt;code&gt;off&lt;/code&gt; compression levels are not affected), and when the source files being backed up have specific data in them to trigger the bug.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.16.3 Released</title>
      <link>https://restic.net/blog/2024-01-14/restic-0.16.3-released/</link>
      <pubDate>Sun, 14 Jan 2024 00:00:00 +0100</pubDate>
      <guid>https://restic.net/blog/2024-01-14/restic-0.16.3-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.3&#34;&gt;restic 0.16.3&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release fixes a couple of bugs on Windows and in the &lt;code&gt;restore&lt;/code&gt; command. It also works around an unlikely yet possible situation with &lt;code&gt;rclone&lt;/code&gt; which could potentially result in data loss. Please upgrade to this new restic version to make sure you are not affected.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.3&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.16.2 Released</title>
      <link>https://restic.net/blog/2023-10-29/restic-0.16.2-released/</link>
      <pubDate>Sun, 29 Oct 2023 00:00:00 +0200</pubDate>
      <guid>https://restic.net/blog/2023-10-29/restic-0.16.2-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.2&#34;&gt;restic 0.16.2&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release restores support for ARMv5 which was accidentally not included in the previous one, and also fixes missing documentation on &lt;a href=&#34;https://restic.readthedocs.io/&#34;&gt;Read the Docs&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.2&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.16.1 Released</title>
      <link>https://restic.net/blog/2023-10-24/restic-0.16.1-released/</link>
      <pubDate>Tue, 24 Oct 2023 00:00:00 +0200</pubDate>
      <guid>https://restic.net/blog/2023-10-24/restic-0.16.1-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.1&#34;&gt;restic 0.16.1&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release contains a few usage and cosmetic improvements, but also one bugfix for a very unlikely but still possible data corruption issue when using the &lt;code&gt;max&lt;/code&gt; compression level. Please read the changelog for more details and information on how to verify your repository if you used &lt;code&gt;max&lt;/code&gt; compression. Please also note that the &lt;code&gt;auto&lt;/code&gt; compression level (which is the default) was never affected.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.16.0 Released</title>
      <link>https://restic.net/blog/2023-07-31/restic-0.16.0-released/</link>
      <pubDate>Mon, 31 Jul 2023 20:42:23 +0200</pubDate>
      <guid>https://restic.net/blog/2023-07-31/restic-0.16.0-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.16.0&#34;&gt;restic 0.16.0&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This version of restic brings up to 25% less memory usage and a lot of usability improvements, including &lt;code&gt;&amp;lt;snapshot&amp;gt;:&amp;lt;subfolder&amp;gt;&lt;/code&gt; syntax for the &lt;code&gt;diff&lt;/code&gt;, &lt;code&gt;ls&lt;/code&gt; and &lt;code&gt;restore&lt;/code&gt; commands, as well as a progress bar and &lt;a href=&#34;https://restic.readthedocs.io/en/stable/075_scripting.html#restore&#34;&gt;JSON support&lt;/a&gt; for the &lt;code&gt;restore&lt;/code&gt; command. Please see the documentation of each command for details.&lt;/p&gt;&#xA;&lt;p&gt;Restic now also includes a &lt;a href=&#34;https://restic.readthedocs.io/en/stable/077_troubleshooting.html&#34;&gt;&lt;code&gt;repair snapshots&lt;/code&gt;&lt;/a&gt; command, which can be used to salvage certain types of damaged repositories. For consistency, the &lt;code&gt;rebuild-index&lt;/code&gt; command has been renamed to &lt;code&gt;repair index&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>REST-server 0.12.1 released</title>
      <link>https://restic.net/blog/2023-07-09/rest-server-0.12.1-released/</link>
      <pubDate>Sun, 09 Jul 2023 18:00:00 +0200</pubDate>
      <guid>https://restic.net/blog/2023-07-09/rest-server-0.12.1-released/</guid>
      <description>&lt;p&gt;We have just released &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.12.1&#34;&gt;rest-server 0.12.1&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release includes a bugfix for fsync related warnings and allows logging to stdout using the &lt;code&gt;--log -&lt;/code&gt; option. Please see the &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.12.1&#34;&gt;changelog&lt;/a&gt; for more specific information!&lt;/p&gt;&#xA;&lt;p&gt;Please let us know what you think in the forum post linked below!&lt;/p&gt;</description>
    </item>
    <item>
      <title>REST-server 0.12.0 released</title>
      <link>https://restic.net/blog/2023-04-24/rest-server-0.12.0-released/</link>
      <pubDate>Mon, 24 Apr 2023 13:00:00 +0200</pubDate>
      <guid>https://restic.net/blog/2023-04-24/rest-server-0.12.0-released/</guid>
      <description>&lt;p&gt;We have just released &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.12.0&#34;&gt;rest-server 0.12.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release includes performance optimizations, allowing additional characters in usernames, ability to specify &lt;code&gt;.htpasswd&lt;/code&gt; file location, as well as some macOS specific fixes and other general compatibility fixes. Please see the &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.12.0&#34;&gt;changelog&lt;/a&gt; for more specific information!&lt;/p&gt;&#xA;&lt;p&gt;Please let us know what you think in the forum post linked below!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.15.2 released</title>
      <link>https://restic.net/blog/2023-04-24/restic-0.15.2-released/</link>
      <pubDate>Mon, 24 Apr 2023 12:00:00 +0200</pubDate>
      <guid>https://restic.net/blog/2023-04-24/restic-0.15.2-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re very pleased to announce &lt;a href=&#34;https://github.com/restic/restic/releases/v0.15.2&#34;&gt;restic 0.15.2&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This release is primarily intended to address some minor bugs and cosmetic issues, but worth mentioning is that it is now possible to use the &lt;code&gt;ap-southeast-4&lt;/code&gt; region (Melbourne) with S3. Also, official restic builds for the &lt;code&gt;riscv64&lt;/code&gt; architecture on Linux are now available.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.15.2&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.15.1 Released</title>
      <link>https://restic.net/blog/2023-01-30/restic-0.15.1-released/</link>
      <pubDate>Mon, 30 Jan 2023 00:00:00 +0100</pubDate>
      <guid>https://restic.net/blog/2023-01-30/restic-0.15.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re very pleased to announce &lt;a href=&#34;https://github.com/restic/restic/releases/v0.15.1&#34;&gt;restic 0.15.1&lt;/a&gt;! This is just a small bugfix release, fixing some issues and cosmetic inconveniences.&lt;/p&gt;&#xA;&lt;p&gt;To download the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.15.1&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! To get help or provide feedback, please write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.15.0 Released</title>
      <link>https://restic.net/blog/2023-01-12/restic-0.15.0-released/</link>
      <pubDate>Thu, 12 Jan 2023 21:14:23 +0100</pubDate>
      <guid>https://restic.net/blog/2023-01-12/restic-0.15.0-released/</guid>
      <description>&lt;p&gt;We are happy to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.15.0&#34;&gt;restic 0.15.0&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;In this version, a new &lt;a href=&#34;https://restic.readthedocs.io/en/stable/045_working_with_repos.html#removing-files-from-snapshots&#34;&gt;&lt;code&gt;rewrite&lt;/code&gt;&lt;/a&gt; command has been implemented. This allows for removing unwanted data from existing snapshots, for example if you discover that some files were unintentionally backed up, such as files with sensitive content or files that take up a lot of space and don&amp;rsquo;t need to be backed up. Please see the &lt;a href=&#34;https://restic.readthedocs.io/en/stable/045_working_with_repos.html#removing-files-from-snapshots&#34;&gt;corresponding documentation&lt;/a&gt; for more information and usage examples.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.14.0 Released</title>
      <link>https://restic.net/blog/2022-08-25/restic-0.14.0-released/</link>
      <pubDate>Thu, 25 Aug 2022 20:16:02 +0200</pubDate>
      <guid>https://restic.net/blog/2022-08-25/restic-0.14.0-released/</guid>
      <description>&lt;p&gt;We today happily announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/v0.14.0&#34;&gt;restic 0.14.0&lt;/a&gt;! \o/&lt;/p&gt;&#xA;&lt;p&gt;This release contains a highly anticipated feature in restic - compression! To start using it, either &lt;a href=&#34;https://restic.readthedocs.io/en/stable/030_preparing_a_new_repo.html#preparing-a-new-repository&#34;&gt;initialize a new repository&lt;/a&gt; (which defaults to repository version 2 and therefore supports compression) or &lt;a href=&#34;https://restic.readthedocs.io/en/stable/045_working_with_repos.html#upgrading-the-repository-format-version&#34;&gt;upgrade your current repository&lt;/a&gt;. The &lt;a href=&#34;https://restic.readthedocs.io/en/stable/047_tuning_backup_parameters.html#compression&#34;&gt;compression level&lt;/a&gt; can be changed from the default &lt;code&gt;auto&lt;/code&gt; (fast and efficient) to &lt;code&gt;max&lt;/code&gt; or &lt;code&gt;off&lt;/code&gt; using the &lt;code&gt;--compression&lt;/code&gt; option (or the corresponding &lt;a href=&#34;https://restic.readthedocs.io/en/stable/040_backup.html#environment-variables&#34;&gt;environment variable&lt;/a&gt;). Please note that the new/upgraded repository can only be accessed by restic version 0.14 or higher.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.13.1 Released</title>
      <link>https://restic.net/blog/2022-04-10/restic-0.13.1-released/</link>
      <pubDate>Sun, 10 Apr 2022 11:16:23 +0200</pubDate>
      <guid>https://restic.net/blog/2022-04-10/restic-0.13.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re proud to announce that &lt;a href=&#34;https://github.com/restic/restic/releases/v0.13.1&#34;&gt;restic 0.13.1&lt;/a&gt; has been released today!&lt;/p&gt;&#xA;&lt;p&gt;This release contains two smaller bug fixes which came up after the last release. For downloading the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.13.1&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.13.0 Released</title>
      <link>https://restic.net/blog/2022-03-26/restic-0.13.0-released/</link>
      <pubDate>Sat, 26 Mar 2022 19:47:44 +0100</pubDate>
      <guid>https://restic.net/blog/2022-03-26/restic-0.13.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re proud to announce that &lt;a href=&#34;https://github.com/restic/restic/releases/v0.13.0&#34;&gt;restic 0.13.0&lt;/a&gt; has been released today!&lt;/p&gt;&#xA;&lt;p&gt;This release contains several bug fixes and improvements worth mentioning:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;It is now possible to add negative patterns to cancel previous exclusions (e.g. &lt;code&gt;--exclude &#39;/home/user/*&#39; --exclude &#39;!/home/user/.config&#39;&lt;/code&gt;).&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;backup&lt;/code&gt; command now has a &lt;code&gt;--dry-run&lt;/code&gt; switch which (together with &lt;code&gt;--verbose&lt;/code&gt;) prints the files that would be included in a backup.&lt;/li&gt;&#xA;&lt;li&gt;We have added checksums for various backends so data uploaded to a backend can be checked there.&lt;/li&gt;&#xA;&lt;li&gt;The &lt;code&gt;restore&lt;/code&gt; command was optimized and is now twice as fast, the &lt;code&gt;copy&lt;/code&gt; command was improved as well.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;For downloading the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.13.0&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rest Server 0.11.0 released</title>
      <link>https://restic.net/blog/2022-02-10/rest-server-0.11.0-released/</link>
      <pubDate>Thu, 10 Feb 2022 20:23:36 +0100</pubDate>
      <guid>https://restic.net/blog/2022-02-10/rest-server-0.11.0-released/</guid>
      <description>&lt;p&gt;We have just released &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.11.0&#34;&gt;rest-server 0.11.0&lt;/a&gt;. It includes a fix for an issue where during transfer, a file could have been corrupted. The details are described in &lt;a href=&#34;https://github.com/restic/rest-server/pull/142&#34;&gt;PR #142&lt;/a&gt;. The full changelog is included in the &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.11.0&#34;&gt;release&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Please let us know what you think in the forum post linked below!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.12.1 released</title>
      <link>https://restic.net/blog/2021-08-03/restic-0.12.1-released/</link>
      <pubDate>Tue, 03 Aug 2021 12:04:36 +0200</pubDate>
      <guid>https://restic.net/blog/2021-08-03/restic-0.12.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re proud to announce that &lt;a href=&#34;https://github.com/restic/restic/releases/v0.12.1&#34;&gt;restic 0.12.1&lt;/a&gt; has been released today! This release contains several small fixes for bugs and a few smaller enhancements.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.12.1&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;. If you have the time, please let us know if the &lt;code&gt;CHANGELOG.md&lt;/code&gt; file (also included in the release on GitHub) is helpful for you. We try hard to make it readable for users, so you do not have to follow the development in detail. Is it worth the effort? What do you think? Please answer in the forum below.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.12.0 released</title>
      <link>https://restic.net/blog/2021-02-14/restic-0.12.0-released/</link>
      <pubDate>Sun, 14 Feb 2021 11:02:36 +0100</pubDate>
      <guid>https://restic.net/blog/2021-02-14/restic-0.12.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re proud to announce that &lt;a href=&#34;https://github.com/restic/restic/releases/v0.12.0&#34;&gt;restic 0.12.0&lt;/a&gt; has been released today! This release packs &lt;strong&gt;many&lt;/strong&gt; speed improvements in several restic commands. For example, we expect that the garbage collection process (&lt;code&gt;restic prune&lt;/code&gt;) will be an order of magnitude faster for almost all users. In addition, you can now configure how much data should be optimized (via &lt;code&gt;--max-repack-size&lt;/code&gt;) and how much unused data is allowed to remain in the repo (via &lt;code&gt;--max-unused&lt;/code&gt;). These flags gives you more control over how long &lt;code&gt;restic prune&lt;/code&gt; will take overall, and also allow you to have several shorter runs of &lt;code&gt;restic prune&lt;/code&gt; instead of a single long one. A special thanks goes out to &lt;a href=&#34;https://github.com/aawsome&#34;&gt;Alexander Weiss&lt;/a&gt; for these indeed awesome improvements in particular, but also to all the other contributors who work on restic!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Restic 0.11.0 released</title>
      <link>https://restic.net/blog/2020-11-05/restic-0.11.0-released/</link>
      <pubDate>Thu, 05 Nov 2020 10:00:51 +0100</pubDate>
      <guid>https://restic.net/blog/2020-11-05/restic-0.11.0-released/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://github.com/restic/restic/releases/v0.11.0&#34;&gt;Restic 0.11.0&lt;/a&gt; was released today! For downloading the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.11.0&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;This new release contains a highly anticipated feature on Windows: being able to automatically create a Volume Shadow Copy (VSS) using &lt;code&gt;restic backup --use-fs-snapshot&lt;/code&gt;. We thought that this feature warrants a new release, just a few weeks after restic 0.10.0 was released. The code was contributed by user &lt;a href=&#34;https://github.com/fgma&#34;&gt;fgma&lt;/a&gt;, thank you very much!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.10.0 released</title>
      <link>https://restic.net/blog/2020-09-19/restic-0.10.0-released/</link>
      <pubDate>Sat, 19 Sep 2020 17:44:59 +0200</pubDate>
      <guid>https://restic.net/blog/2020-09-19/restic-0.10.0-released/</guid>
      <description>&lt;p&gt;After ten months of work we&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.10.0&#34;&gt;restic 0.10.0&lt;/a&gt;! For downloading the new release and to see a more detailed list of important changes, please head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.10.0&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;This release contains a lot of improvements, both smaller and bigger ones, and the restic project wishes to send a big thank you to everyone who contributed to make this happen. Every contribution, be it a small documentation change or deeply technical code changes and optimizations, are always welcome. An extra huge thanks goes out to &lt;a href=&#34;https://github.com/MichaelEischer&#34;&gt;MichaelEischer&lt;/a&gt; for tying it all together with countless hours of tireless reviewing and carefully considered decisions as part of this delicate process.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rest Server 0.10.0 Released</title>
      <link>https://restic.net/blog/2020-09-13/rest-server-0.10.0-released/</link>
      <pubDate>Sun, 13 Sep 2020 11:47:00 +0200</pubDate>
      <guid>https://restic.net/blog/2020-09-13/rest-server-0.10.0-released/</guid>
      <description>&lt;p&gt;We have just released &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.10.0&#34;&gt;rest-server 0.10.0&lt;/a&gt; which includes a few potentially breaking changes. For details, please see the changes described &lt;a href=&#34;https://github.com/restic/rest-server/releases/tag/v0.10.0&#34;&gt;in the release&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release corrects a security issue. User &lt;a href=&#34;https://github.com/wojas&#34;&gt;wojas&lt;/a&gt; discovered that it was possible to access repositories belonging to other users. It was not possible to access directories outside of the path the repositories were stored in.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;code&gt;rest-server&lt;/code&gt; has an option to allow users (identify by HTTP Basic authentication) to only access their own repository by specifying the &lt;code&gt;--private-repos&lt;/code&gt; option. For example, the user &lt;code&gt;foo&lt;/code&gt; can then only access the repository at &lt;code&gt;https://localhost:8000/foo&lt;/code&gt;, but not the repo of the user &lt;code&gt;bar&lt;/code&gt; at &lt;code&gt;http://localhost:8000/bar&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.6 released</title>
      <link>https://restic.net/blog/2019-11-22/restic-0.9.6-released/</link>
      <pubDate>Fri, 22 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2019-11-22/restic-0.9.6-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.6&#34;&gt;restic 0.9.6&lt;/a&gt;. For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.6&#34;&gt;GitHub&lt;/a&gt;. If you already have restic (0.9.4 or later), you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.5 released</title>
      <link>https://restic.net/blog/2019-04-23/restic-0.9.5-released/</link>
      <pubDate>Tue, 23 Apr 2019 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2019-04-23/restic-0.9.5-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.5&#34;&gt;restic 0.9.5&lt;/a&gt;. For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.5&#34;&gt;GitHub&lt;/a&gt;. If you already have restic 0.9.4, you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.4 released</title>
      <link>https://restic.net/blog/2019-01-06/restic-0.9.4-released/</link>
      <pubDate>Sun, 06 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2019-01-06/restic-0.9.4-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.4&#34;&gt;restic 0.9.4&lt;/a&gt;. Besides several fixes for bugs it contains a new restorer implementation which downloads data concurrently, so it is much faster than the old one.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.4&#34;&gt;GitHub&lt;/a&gt;. If you already have restic 0.9.3, you can use the &lt;code&gt;self-update&lt;/code&gt; command to automatically download and verify the new release. Due to a &lt;a href=&#34;https://github.com/restic/restic/issues/2041&#34;&gt;bug&lt;/a&gt; you need to specify where restic should write the new file, e.g. like this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Year, New Infrastructure!</title>
      <link>https://restic.net/blog/2019-01-01/new-infrastructure/</link>
      <pubDate>Tue, 01 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2019-01-01/new-infrastructure/</guid>
      <description>&lt;p&gt;We wish you a happy new year 2019!&lt;/p&gt;&#xA;&lt;p&gt;Our friends at &lt;a href=&#34;https://www.hosting.de&#34;&gt;hosting.de&lt;/a&gt; recently provided us with a dedicated server to host this website, the forum, and the &lt;a href=&#34;https://beta.restic.net&#34;&gt;beta builder&lt;/a&gt; for restic, and we&amp;rsquo;ve just moved everything over. Thank you very much for your support!&lt;/p&gt;&#xA;&lt;p&gt;Please leave a comment in the forum in the thread for this announcement if there&amp;rsquo;s anything broken for you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.3 released</title>
      <link>https://restic.net/blog/2018-10-13/restic-0.9.3-released/</link>
      <pubDate>Sat, 13 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-10-13/restic-0.9.3-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.3&#34;&gt;restic 0.9.3&lt;/a&gt;. It is mostly a maintenance release, but several smaller enhancements have been added.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.3&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new/choose&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configuring GitHub Issue Templates</title>
      <link>https://restic.net/blog/2018-09-09/GitHub-issue-templates/</link>
      <pubDate>Sun, 09 Sep 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-09-09/GitHub-issue-templates/</guid>
      <description>&lt;p&gt;Like many other Open Source projects, restic uses GitHub for hosting the source&#xA;code and managing issues. Over time, we discovered that oftentimes users open&#xA;an issue on GitHub which just consists of a question, for example on how to use&#xA;restic in a certain situation. While such issues can be answered quickly,&#xA;sometimes there&amp;rsquo;s no consent on when the issue can be seen as resolved and&#xA;therefore closed (the issue is not actionable). The GitHub issue tracker is&#xA;then cluttered with issues for which there is no clear next action and no&#xA;clear &amp;ldquo;resolved&amp;rdquo; state. This blog post describes how we set up the issue&#xA;templates on GitHub to resolve this situation nicely.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enabling the Go Build Cache on Travis/AppVeyor</title>
      <link>https://restic.net/blog/2018-09-02/travis-build-cache/</link>
      <pubDate>Sun, 02 Sep 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-09-02/travis-build-cache/</guid>
      <description>&lt;p&gt;The restic project runs the unit and integration tests for each pushed commit&#xA;and each pull request. We&amp;rsquo;re using &lt;a href=&#34;https://travis-ci.com&#34;&gt;Travis CI&lt;/a&gt; for Linux&#xA;and OS X, and &lt;a href=&#34;https://www.appveyor.com/&#34;&gt;AppVeyor&lt;/a&gt; for Windows. We&amp;rsquo;re very&#xA;grateful that they provide their services free of charge for Open Source&#xA;projects!&lt;/p&gt;&#xA;&lt;p&gt;Our project not only runs the tests on Travis, but also compiles restic for&#xA;each supported architecture, operating system, and version of Go. Go is known&#xA;for its fast compilation times, but still, compilation takes its time. Roughly,&#xA;for each version of Go, running all the tests takes between 13 and 25 minutes:&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.2 released</title>
      <link>https://restic.net/blog/2018-08-06/restic-0.9.2-released/</link>
      <pubDate>Mon, 06 Aug 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-08-06/restic-0.9.2-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.2&#34;&gt;restic 0.9.2&lt;/a&gt;. Among several fixes it includes support for &amp;ldquo;Application Keys&amp;rdquo; for BackBlaze B2, which can be restricted to a specific bucket and/or path (so you don&amp;rsquo;t have to give restic access to all your files stored at B2).&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.2&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.1 released</title>
      <link>https://restic.net/blog/2018-06-10/restic-0.9.1-released/</link>
      <pubDate>Sun, 10 Jun 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-06-10/restic-0.9.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.1&#34;&gt;restic 0.9.1&lt;/a&gt;, a minor bugfix release.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/v0.9.1&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.9.0 released</title>
      <link>https://restic.net/blog/2018-05-21/restic-0.9.0-released/</link>
      <pubDate>Mon, 21 May 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-05-21/restic-0.9.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.9.0&#34;&gt;restic 0.9.0&lt;/a&gt;. This is the next bigger release since 0.8.0, it mainly brings a completely rewritten archiver core, improves the speed for &lt;code&gt;restic check&lt;/code&gt;, and many bug fixes.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.9.0&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The restic project turns four!</title>
      <link>https://restic.net/blog/2018-04-06/restic-turns-four/</link>
      <pubDate>Fri, 06 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-04-06/restic-turns-four/</guid>
      <description>&lt;p&gt;Four years ago on 2014-04-06 &lt;a href=&#34;https://github.com/fd0&#34;&gt;fd0&lt;/a&gt; added the &lt;a href=&#34;https://github.com/restic/restic/commit/c54facf66be1c4e137121f36b300543f6673ea7c&#34;&gt;first commit&lt;/a&gt; to what would later become the restic repository. At the time it was code-named &lt;code&gt;khepri&lt;/code&gt;, but unfortunately the name wasn&amp;rsquo;t available on GitHub any more, so we had to find a different one.&lt;/p&gt;&#xA;&lt;p&gt;At the moment, restic&amp;rsquo;s repository was starred on GitHub almost four thousand times. And we&amp;rsquo;ve &lt;a href=&#34;https://github.com/restic/others&#34;&gt;collected&lt;/a&gt; 56 other backup tools along the way, helping countless people to discover backup programs (not necessarily restic alone). These two facts alone prove that it was worth it: More people were able to setup easy, effortless backups which they can depend upon.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using rclone as a restic Backend</title>
      <link>https://restic.net/blog/2018-04-01/rclone-backend/</link>
      <pubDate>Sun, 01 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-04-01/rclone-backend/</guid>
      <description>&lt;p&gt;Originally, restic started with just two backends: &lt;code&gt;local&lt;/code&gt; and &lt;code&gt;sftp&lt;/code&gt;. Over time, many new backends were added so that restic is now able to store a repository on a variety of different cloud-based services. However, it became clear that each new backend we add for a new cloud service works slightly different and requires almost constant maintenance.&lt;/p&gt;&#xA;&lt;p&gt;A while ago, &lt;a href=&#34;https://github.com/fd0&#34;&gt;Alex&lt;/a&gt; was contacted by &lt;a href=&#34;https://github.com/ncw&#34;&gt;Nick&lt;/a&gt;, who found restic by listening to the episode &lt;a href=&#34;https://changelog.com/gotime/48&#34;&gt;#48&lt;/a&gt; of the &lt;a href=&#34;https://changelog.com/gotime&#34;&gt;GoTime podcast&lt;/a&gt;. He&amp;rsquo;s the primary author of &lt;a href=&#34;https://github.com/ncw/rclone&#34;&gt;rclone&lt;/a&gt;, a program which is &amp;ldquo;rsync for cloud storage&amp;rdquo;. At the moment, it supports almost 20 different backends/services! They quickly agreed that it would be awesome if restic could just use rclone as a backend, thereby supporting all the backends that rclone can talk to!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.8.3 released</title>
      <link>https://restic.net/blog/2018-02-26/restic-0.8.3-released/</link>
      <pubDate>Mon, 26 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-02-26/restic-0.8.3-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.3&#34;&gt;restic 0.8.3&lt;/a&gt;. This is again a bugfix release, but also several improvements for cloud-based backends.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.3&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.8.2 released</title>
      <link>https://restic.net/blog/2018-02-17/restic-0.8.2-released/</link>
      <pubDate>Sat, 17 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-02-17/restic-0.8.2-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.2&#34;&gt;restic 0.8.2&lt;/a&gt;. This is mostly a bugfix release, with some smaller enhancements.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.2&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>moving to restic.net</title>
      <link>https://restic.net/blog/2018-01-01/moving-domain/</link>
      <pubDate>Mon, 01 Jan 2018 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2018-01-01/moving-domain/</guid>
      <description>&lt;p&gt;A while back we&amp;rsquo;ve registered the domain &lt;code&gt;restic.net&lt;/code&gt; and we&amp;rsquo;re moving the&#xA;website from GitHub Pages to a dedicated hosting machine at&#xA;&lt;a href=&#34;https://restic.net&#34;&gt;https://restic.net&lt;/a&gt;. Please update any links to the old website,&#xA;thanks!&lt;/p&gt;&#xA;&lt;p&gt;&lt;del&gt;If you&amp;rsquo;re subscribed to the RSS/Atom XML feed, you need to update the feed url&#xA;to &lt;a href=&#34;https://restic.net/feed.xml&#34;&gt;https://restic.net/feed.xml&lt;/a&gt;.&lt;/del&gt;&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt; When we migrated the website to &lt;a href=&#34;https://gohugo.io&#34;&gt;Hugo&lt;/a&gt; in 2020, the&#xA;feed changed from Atom at the above mentioned URL to RSS 2.0 at individual section&#xA;URLs, e.g. &lt;a href=&#34;https://restic.net/blog/index.xml&#34;&gt;https://restic.net/blog/index.xml&lt;/a&gt;&#xA;for the blog posts. Please update or verify the feed configuration in your reader&#xA;so you don&amp;rsquo;t miss out on any new posts! :)&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.8.1 released</title>
      <link>https://restic.net/blog/2017-12-27/restic-0.8.1-released/</link>
      <pubDate>Wed, 27 Dec 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-12-27/restic-0.8.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.1&#34;&gt;restic 0.8.1&lt;/a&gt;. Among others, support for DigitalOcean Spaces (and other backends which use HTTP) is improved.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.1&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.8.0 released</title>
      <link>https://restic.net/blog/2017-11-26/restic-0.8.0-released/</link>
      <pubDate>Sun, 26 Nov 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-11-26/restic-0.8.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.0&#34;&gt;restic 0.8.0&lt;/a&gt;. It brings the new awesome metadata cache which will speed up many operations, you may need to run &lt;code&gt;restic prune&lt;/code&gt; once to fully see it in action.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the new release and see a more detailed list of important changes, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.8.0&#34;&gt;GitHub&lt;/a&gt;. As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter! Or just write a post in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release also corrects a (low risk) vulnerability. When attackers are able to create files with arbitrary names on a Linux/Unix system in a directory that is saved with restic, it may happen that when the directory is restored on a Windows system to write files outside the target directory for the restore.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Upcoming changes for the S3 backend</title>
      <link>https://restic.net/blog/2017-11-25/upcoming-changes-to-s3/</link>
      <pubDate>Sat, 25 Nov 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-11-25/upcoming-changes-to-s3/</guid>
      <description>&lt;p&gt;TL;DR: If you&amp;rsquo;re using the &lt;code&gt;s3&lt;/code&gt; backend and cannot access your repo any more, append the path &lt;code&gt;/restic&lt;/code&gt; to the repository location.&lt;/p&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve just merged &lt;a href=&#34;https://github.com/restic/restic/pull/1437&#34;&gt;Pull Request #1437&lt;/a&gt; which resolves an issue with the S3 backend reported in &lt;a href=&#34;https://github.com/restic/restic/issues/1292&#34;&gt;#1292&lt;/a&gt;. When the next restic version is released (or you&amp;rsquo;re using the master branch directly), this may require modifying the repository location you&amp;rsquo;re passing to restic.&lt;/p&gt;&#xA;&lt;p&gt;In order to access a repository stored on S3, restic requires the following information:&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.7.3 released</title>
      <link>https://restic.net/blog/2017-09-20/restic-0.7.3-released/</link>
      <pubDate>Wed, 20 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-09-20/restic-0.7.3-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.3&#34;&gt;restic 0.7.3&lt;/a&gt; to correct a bug with the Google Cloud Storage and Azure backends. When &lt;code&gt;restic prune&lt;/code&gt; or &lt;code&gt;restic rebuild-index&lt;/code&gt; was run, not all files stored in these backends were considered.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.3&#34;&gt;GitHub&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;p&gt;The binaries released with each restic version are &lt;a href=&#34;https://reproducible-builds.org/&#34;&gt;reproducible&lt;/a&gt;, which means that you can easily reproduce a byte identical version from the source code for that release. Instructions on how to do that are contained in the &lt;a href=&#34;https://github.com/restic/builder&#34;&gt;builder repository&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.7.2 released</title>
      <link>https://restic.net/blog/2017-09-13/restic-0.7.2-released/</link>
      <pubDate>Wed, 13 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-09-13/restic-0.7.2-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re very pleased to announce that &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.2&#34;&gt;restic 0.7.2&lt;/a&gt; has been released!&#xA;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.2&#34;&gt;GitHub&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;p&gt;The binaries released with each restic version are &lt;a href=&#34;https://reproducible-builds.org/&#34;&gt;reproducible&lt;/a&gt;, which means that you can easily reproduce a byte identical version from the source code for that release. Instructions on how to do that are contained in the &lt;a href=&#34;https://github.com/restic/builder&#34;&gt;builder repository&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h1 id=&#34;important-changes-in-072&#34;&gt;Important Changes in 0.7.2&lt;/h1&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve added an official docker image and a Dockerfile to build this image in &lt;code&gt;docker/&lt;/code&gt;.&#xA;&lt;a href=&#34;https://github.com/restic/restic/pull/1061&#34;&gt;#1061&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meeting at FrOSCon 2017 - Details</title>
      <link>https://restic.net/blog/2017-08-14/FrOSCon-Bonn-Details/</link>
      <pubDate>Mon, 14 Aug 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-08-14/FrOSCon-Bonn-Details/</guid>
      <description>&lt;p&gt;As announced &lt;a href=&#34;https://restic.net/blog/2017-07-21/FrOSCon-Bonn/&#34;&gt;a few weeks ago&lt;/a&gt; we&amp;rsquo;re meeting at this year&amp;rsquo;s &lt;a href=&#34;https://www.froscon.de&#34;&gt;FrOSCon&lt;/a&gt; on 19 August 2017, 15:00 CEST in &lt;a href=&#34;https://goo.gl/maps/Rj2Z6ZQfyXK2&#34;&gt;Sankt Augustin&lt;/a&gt; near Bonn/Cologne in Germany (free entry)! We&amp;rsquo;ll get a project room for the afternoon, the room number will be announced as an update to this blog entry, &lt;a href=&#34;https://fosstodon.org/@restic&#34;&gt;on Fosstodon&lt;/a&gt; and in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;It&amp;rsquo;d be nice to know how many of you will be able to join us, so please leave a comment in the &lt;a href=&#34;https://github.com/restic/restic/issues/1110&#34;&gt;GitHub issue #1110&lt;/a&gt; or in the forum. We&amp;rsquo;re looking forward to meeting you all, thanks!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Discourse Forum</title>
      <link>https://restic.net/blog/2017-08-11/discourse-forum/</link>
      <pubDate>Fri, 11 Aug 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-08-11/discourse-forum/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve noticed that there are &lt;a href=&#34;https://github.com/restic/restic/issues?q=is%3Aissue%20label%3Aquestion&#34;&gt;many questions raised as issues&lt;/a&gt; on GitHub, so we&amp;rsquo;ve installed a Discourse forum at &lt;a href=&#34;https://forum.restic.net&#34;&gt;https://forum.restic.net&lt;/a&gt;! For now, this is an experiment to see if a forum is better suited to answer questions. We&amp;rsquo;ll see how that goes.&lt;/p&gt;&#xA;&lt;p&gt;Please let us know any feedback you have (in &lt;a href=&#34;https://forum.restic.net&#34;&gt;the forum&lt;/a&gt;, obviously)!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Please upgrade to restic 0.7.1!</title>
      <link>https://restic.net/blog/2017-07-25/please-upgrade-to-0.7.1/</link>
      <pubDate>Tue, 25 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-07-25/please-upgrade-to-0.7.1/</guid>
      <description>&lt;p&gt;TL;DR:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Under some circumstances, data in the repo was not stored properly&lt;/li&gt;&#xA;&lt;li&gt;This could have caused incomplete backups&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Upgrade restic to at least 0.7.1 and run &lt;code&gt;restic rebuild-index&lt;/code&gt; before the next backup&lt;/strong&gt;&lt;/li&gt;&#xA;&lt;li&gt;It is good practice to run &lt;code&gt;restic check&lt;/code&gt; regularly&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;&#xA;&lt;p&gt;We always knew that at some point there may be a more serious bug in restic&#xA;that warrants a broader announcement. This is the story of how a small&#xA;improvement that makes the code even more conservative lead to a small error&#xA;which then caused a couple of unintended consequences. In the end, under some&#xA;specific circumstances restic wrote incomplete snapshots to the repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.7.1 released</title>
      <link>https://restic.net/blog/2017-07-22/restic-0.7.1-released/</link>
      <pubDate>Sat, 22 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-07-22/restic-0.7.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re proud to present &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.1&#34;&gt;restic 0.7.1&lt;/a&gt;!&#xA;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.1&#34;&gt;GitHub&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;p&gt;The binaries released with each restic version starting are &lt;a href=&#34;https://reproducible-builds.org/&#34;&gt;reproducible&lt;/a&gt;, which means that you can easily reproduce a byte identical version from the source code for that release. Instructions on how to do that are contained in the &lt;a href=&#34;https://github.com/restic/builder&#34;&gt;builder repository&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h1 id=&#34;important-changes-in-071&#34;&gt;Important Changes in 0.7.1&lt;/h1&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The &lt;code&gt;migrate&lt;/code&gt; command for changing the &lt;code&gt;s3legacy&lt;/code&gt; layout to the &lt;code&gt;default&lt;/code&gt; layout for s3 backends has been improved: It can now be restarted with &lt;code&gt;restic migrate --force s3_layout&lt;/code&gt; and automatically retries operations on error. &lt;a href=&#34;https://github.com/restic/restic/issues/1073&#34;&gt;#1073&lt;/a&gt; &lt;a href=&#34;https://github.com/restic/restic/pull/1075&#34;&gt;#1075&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;small-changes&#34;&gt;Small changes&lt;/h2&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;The local and sftp backends now create the subdirs below &lt;code&gt;data/&lt;/code&gt; on open/init. This way, restic makes sure that they always exist. This is connected to an issue for the sftp server: &lt;a href=&#34;https://github.com/restic/rest-server/pull/11#issuecomment-309879710&#34;&gt;#11&lt;/a&gt; &lt;a href=&#34;https://github.com/restic/restic/issues/1055&#34;&gt;#1055&lt;/a&gt; &lt;a href=&#34;https://github.com/restic/restic/pull/1077&#34;&gt;#1077&lt;/a&gt; &lt;a href=&#34;https://github.com/restic/restic/pull/1105&#34;&gt;#1105&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Meeting at FrOSCon 2017</title>
      <link>https://restic.net/blog/2017-07-21/FrOSCon-Bonn/</link>
      <pubDate>Fri, 21 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-07-21/FrOSCon-Bonn/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re planning to have a restic meeting at this year&amp;rsquo;s &lt;a href=&#34;https://www.froscon.de&#34;&gt;FrOSCon&lt;/a&gt;, which takes place on 19 and 20 August 2017 in &lt;a href=&#34;https://goo.gl/maps/Rj2Z6ZQfyXK2&#34;&gt;Sankt Augustin&lt;/a&gt; near Bonn/Cologne in Germany. The entry is free! In order to organize this, please add a &amp;ldquo;+1&amp;rdquo; reaction to &lt;a href=&#34;https://github.com/restic/restic/issues/1110&#34;&gt;the GitHub issue #1110&lt;/a&gt;. We&amp;rsquo;re looking forward to meeting you!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.7.0 released</title>
      <link>https://restic.net/blog/2017-07-01/restic-0.7.0-released/</link>
      <pubDate>Sat, 01 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-07-01/restic-0.7.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.0&#34;&gt;restic 0.7.0&lt;/a&gt;!&#xA;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.7.0&#34;&gt;GitHub&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;h1 id=&#34;important-changes-in-070&#34;&gt;Important Changes in 0.7.0&lt;/h1&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;New &amp;ldquo;swift&amp;rdquo; backend: A new backend for the OpenStack Swift cloud storage&#xA;protocol has been added, &lt;a href=&#34;https://wiki.openstack.org/wiki/Swift&#34;&gt;https://wiki.openstack.org/wiki/Swift&lt;/a&gt;&#xA;&lt;a href=&#34;https://github.com/restic/restic/pull/975&#34;&gt;https://github.com/restic/restic/pull/975&lt;/a&gt;&#xA;&lt;a href=&#34;https://github.com/restic/restic/pull/648&#34;&gt;https://github.com/restic/restic/pull/648&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;New &amp;ldquo;b2&amp;rdquo; backend: A new backend for Backblaze B2 cloud storage&#xA;service has been added, &lt;a href=&#34;https://www.backblaze.com&#34;&gt;https://www.backblaze.com&lt;/a&gt;&#xA;&lt;a href=&#34;https://github.com/restic/restic/issues/512&#34;&gt;https://github.com/restic/restic/issues/512&lt;/a&gt;&#xA;&lt;a href=&#34;https://github.com/restic/restic/pull/978&#34;&gt;https://github.com/restic/restic/pull/978&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;Improved performance for the &lt;code&gt;find&lt;/code&gt; command: Restic recognizes paths it has&#xA;already checked for the files in question, so the number of backend requests&#xA;is reduced a lot.&#xA;&lt;a href=&#34;https://github.com/restic/restic/issues/989&#34;&gt;https://github.com/restic/restic/issues/989&lt;/a&gt;&#xA;&lt;a href=&#34;https://github.com/restic/restic/pull/993&#34;&gt;https://github.com/restic/restic/pull/993&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic on GoTime #48</title>
      <link>https://restic.net/blog/2017-06-01/restic-on-gotime/</link>
      <pubDate>Thu, 01 Jun 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-06-01/restic-on-gotime/</guid>
      <description>&lt;p&gt;Last week &lt;a href=&#34;https://github.com/fd0&#34;&gt;Alex&lt;/a&gt; had the honour to join &lt;a href=&#34;https://x.com/ashleymcnamara&#34;&gt;Ashley&lt;/a&gt;, &lt;a href=&#34;https://x.com/erikstmartin&#34;&gt;Erik&lt;/a&gt;, and &lt;a href=&#34;https://x.com/bketelsen&#34;&gt;Brian&lt;/a&gt; at &lt;a href=&#34;https://changelog.com/gotime&#34;&gt;GoTime&lt;/a&gt;. GoTime is a podcast about Go, the community, and everything in between. It was a lot of fun (and he got to do the intro in German). The episode can be found on the &lt;a href=&#34;https://changelog.com/gotime/48&#34;&gt;website&lt;/a&gt;, you can also listen to it right here:&lt;/p&gt;&#xA;&lt;p&gt;&lt;audio data-theme=&#34;night&#34; data-src=&#34;https://changelog.com/gotime/48/embed&#34; src=&#34;https://cdn.changelog.com/uploads/gotime/48/go-time-48.mp3&#34; preload=&#34;none&#34; class=&#34;changelog-episode&#34; controls&gt;&lt;/audio&gt;&lt;p&gt;&lt;a href=&#34;https://changelog.com/gotime/48&#34;&gt;Go Time 48: Restic and Backups (Done Right) with Alexander Neumann&lt;/a&gt; – Listen on &lt;a href=&#34;https://changelog.com/&#34;&gt;Changelog.com&lt;/a&gt;&lt;/p&gt;&lt;script async src=&#34;//cdn.changelog.com/embed.js&#34;&gt;&lt;/script&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.6.0 released</title>
      <link>https://restic.net/blog/2017-05-29/restic-0.6.0-released/</link>
      <pubDate>Mon, 29 May 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-05-29/restic-0.6.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.6.0&#34;&gt;restic 0.6.0&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;No grave bugs have been found, so the final version is identical to the &lt;code&gt;-rc.1&lt;/code&gt; version. This release contains many bug fixes and several improvements for the user interface, the most important changes are listed below (and also contained in the &lt;code&gt;CHANGELOG.md&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.6.0&#34;&gt;https://github.com/restic/restic/releases/tag/v0.6.0&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;h1 id=&#34;important-changes-in-060&#34;&gt;Important Changes in 0.6.0&lt;/h1&gt;&#xA;&lt;h2 id=&#34;consistent-forget-policy&#34;&gt;Consistent forget policy&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;forget&lt;/code&gt; command was corrected to be more consistent in which snapshots are to be forgotten. It is possible that the new code removes more snapshots than before, so please review what would be deleted by using the &lt;code&gt;--dry-run&lt;/code&gt; option. &lt;a href=&#34;https://github.com/restic/restic/pull/957&#34;&gt;https://github.com/restic/restic/pull/957&lt;/a&gt; &lt;a href=&#34;https://github.com/restic/restic/issues/953&#34;&gt;https://github.com/restic/restic/issues/953&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.6.1 released</title>
      <link>https://restic.net/blog/2017-05-29/restic-0.6.1-released/</link>
      <pubDate>Mon, 29 May 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-05-29/restic-0.6.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.6.1&#34;&gt;restic 0.6.1&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;Just a few days after the release of restic 0.6.0 we&amp;rsquo;ve released 0.6.1 as a bugfix release to address two annoying bugs. The changes are listed below.&lt;/p&gt;&#xA;&lt;p&gt;This is the first release of restic that uses the new &lt;a href=&#34;https://github.com/restic/builder&#34;&gt;build Docker container&lt;/a&gt; which allows you to reproduce a byte identical version of the released binaries. This is called &lt;a href=&#34;https://reproducible-builds.org/&#34;&gt;Reproducible Builds&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.6.1&#34;&gt;GitHub&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.6.0-rc.1 released</title>
      <link>https://restic.net/blog/2017-05-25/restic-0.6.0-rc.1-released/</link>
      <pubDate>Thu, 25 May 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-05-25/restic-0.6.0-rc.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.6.0-rc.1&#34;&gt;restic 0.6.0-rc.1&lt;/a&gt;!&lt;/p&gt;&#xA;&lt;p&gt;This is the Release Candidate version. If no grave bugs occur, it will be released as the final version in a few days. This release contains many bug fixes and several improvements for the user interface, the most important changes are listed below (and also contained in the &lt;code&gt;CHANGELOG.md&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;For downloading the code, head over to &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.6.0-rc.1&#34;&gt;https://github.com/restic/restic/releases/tag/v0.6.0-rc.1&lt;/a&gt;&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;h1 id=&#34;important-changes-in-060&#34;&gt;Important Changes in 0.6.0&lt;/h1&gt;&#xA;&lt;h2 id=&#34;consistent-forget-policy&#34;&gt;Consistent forget policy&lt;/h2&gt;&#xA;&lt;p&gt;The &lt;code&gt;forget&lt;/code&gt; command was corrected to be more consistent in which snapshots are to be forgotten. It is possible that the new code removes more snapshots than before, so please review what would be deleted by using the &lt;code&gt;--dry-run&lt;/code&gt; option. &lt;a href=&#34;https://github.com/restic/restic/pull/957&#34;&gt;https://github.com/restic/restic/pull/957&lt;/a&gt; &lt;a href=&#34;https://github.com/restic/restic/issues/953&#34;&gt;https://github.com/restic/restic/issues/953&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.5.0 released</title>
      <link>https://restic.net/blog/2017-03-11/restic-0.5.0-released/</link>
      <pubDate>Sat, 11 Mar 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-03-11/restic-0.5.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.5.0&#34;&gt;restic 0.5.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release contains (among many bug fixes) several improvements to the user interface:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;more progress bars&lt;/li&gt;&#xA;&lt;li&gt;consistent filtering for tags, hostname, or path&lt;/li&gt;&#xA;&lt;li&gt;a new command tag which allows modifying tags of existing snapshots&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Since we&amp;rsquo;ve internally started using the new &lt;code&gt;context&lt;/code&gt; package, Go 1.7 is now&#xA;required for compiling restic. Running &lt;code&gt;build.go&lt;/code&gt; will check this for you. The&#xA;released binaries have been compiled with Go 1.8.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.4.0 released</title>
      <link>https://restic.net/blog/2017-02-02/restic-0.4.0-released/</link>
      <pubDate>Thu, 02 Feb 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-02-02/restic-0.4.0-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve just released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.4.0&#34;&gt;restic 0.4.0&lt;/a&gt;. This release will use much less memory during certain operations (notably &lt;code&gt;prune&lt;/code&gt;, but also during backup). There have also been some major internal changes which will hopefully contribute to an even larger improvement in memory usage.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Go Devroom at FOSDEM 2017</title>
      <link>https://restic.net/blog/2017-02-02/FOSDEM-2017-Brussels/</link>
      <pubDate>Thu, 02 Feb 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-02-02/FOSDEM-2017-Brussels/</guid>
      <description>&lt;p&gt;For the third time at this year&amp;rsquo;s &lt;a href=&#34;https://fosdem.org&#34;&gt;FOSDEM&lt;/a&gt; (which stands for &amp;ldquo;Free and Open&#xA;Source Software Developers&amp;rsquo; European Meeting&amp;rdquo; &lt;a href=&#34;https://en.wikipedia.org/wiki/FOSDEM&#34;&gt;according to Wikipedia&lt;/a&gt;)&#xA;features a room on Sunday (5 February 2017) dedicated to Go development: &lt;a href=&#34;https://fosdem.org/2017/schedule/track/go/&#34;&gt;The Go Devroom&lt;/a&gt;.&#xA;&lt;a href=&#34;https://github.com/fd0&#34;&gt;fd0&lt;/a&gt; will be available for a chat about restic and Go development the whole day!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.3.3 released, Debian package</title>
      <link>https://restic.net/blog/2017-01-08/restic-0.3.3-released/</link>
      <pubDate>Sun, 08 Jan 2017 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2017-01-08/restic-0.3.3-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;ve released another minor version: &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.3.3&#34;&gt;restic 0.3.3&lt;/a&gt;.&#xA;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;&#xA;&lt;p&gt;Recently, several people &lt;a href=&#34;https://github.com/restic/restic/issues/355&#34;&gt;worked together&lt;/a&gt; to create and upload an official Debian package for restic.&#xA;A few days ago on 2 January 2017, that package entered the &lt;code&gt;testing&lt;/code&gt; distribution, so restic will be part of the next Debian stable release!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.3.2 released</title>
      <link>https://restic.net/blog/2016-12-18/restic-0.3.2-released/</link>
      <pubDate>Sun, 18 Dec 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-12-18/restic-0.3.2-released/</guid>
      <description>&lt;p&gt;A few days ago we&amp;rsquo;ve &lt;a href=&#34;https://restic.net/blog/2016-12-13/restic-0.3.1-released/&#34;&gt;released restic 0.3.1&lt;/a&gt;, unfortunately that introduced a bug which let&amp;rsquo;s restic panic when there is an error during backup. The details are described in GitHub issues &lt;a href=&#34;https://github.com/restic/restic/issues/699&#34;&gt;#699&lt;/a&gt; and &lt;a href=&#34;https://github.com/restic/restic/issues/700&#34;&gt;#700&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;So, here it is: &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.3.2&#34;&gt;restic version 0.3.2&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.3.1 released</title>
      <link>https://restic.net/blog/2016-12-13/restic-0.3.1-released/</link>
      <pubDate>Tue, 13 Dec 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-12-13/restic-0.3.1-released/</guid>
      <description>&lt;p&gt;We&amp;rsquo;re proud to announce the release of &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.3.1&#34;&gt;restic version 0.3.1&lt;/a&gt;. This is mainly a small bugfix release, no major new features have been added.&lt;/p&gt;&#xA;&lt;p&gt;The detailed change log can be found &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.3.1&#34;&gt;in the release notes&lt;/a&gt; or &lt;a href=&#34;https://github.com/restic/restic/compare/v0.3.0...v0.3.1&#34;&gt;on GitHub&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;As always, thanks for &lt;a href=&#34;https://github.com/restic/restic/issues/new&#34;&gt;reporting any issues&lt;/a&gt; you encounter!&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.3.0 released</title>
      <link>https://restic.net/blog/2016-10-01/restic-0.3.0-released/</link>
      <pubDate>Sat, 01 Oct 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-10-01/restic-0.3.0-released/</guid>
      <description>&lt;p&gt;After two months development we&amp;rsquo;re proud to release &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.3.0&#34;&gt;restic version 0.3.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The most notable change is the addition of the &lt;code&gt;prune&lt;/code&gt; and &lt;code&gt;forget&lt;/code&gt; commands (we&amp;rsquo;ve covered them in &lt;a href=&#34;https://restic.net/blog/2016-08-22/removing-snapshots/&#34;&gt;an earlier blog post&lt;/a&gt;) which allow removing backups from the repository according to configurable criteria. Since this was one of the most requested features, now that it is implemented there&amp;rsquo;s really no excuse for not making backups any more!&lt;/p&gt;&#xA;&lt;p&gt;The detailed change log can be found &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.3.0&#34;&gt;in the release notes&lt;/a&gt; or &lt;a href=&#34;https://github.com/restic/restic/compare/v0.2.0...v0.3.0&#34;&gt;on GitHub&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Removing Snapshots</title>
      <link>https://restic.net/blog/2016-08-22/removing-snapshots/</link>
      <pubDate>Mon, 22 Aug 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-08-22/removing-snapshots/</guid>
      <description>&lt;p&gt;The feature that was most often requested feature for restic is the ability to&#xA;remove snapshots from the repository. Sometimes, restic was even (rightfully)&#xA;criticised for not having such a function.&lt;/p&gt;&#xA;&lt;p&gt;After about three months of work, &lt;a href=&#34;https://github.com/restic/restic/pull/518&#34;&gt;PR #518&lt;/a&gt;&#xA;was merged into the master branch a few days ago. This pull request brings two&#xA;new commands to restic: &lt;code&gt;forget&lt;/code&gt; and &lt;code&gt;prune&lt;/code&gt;, which allows you to not only&#xA;remove a single snapshot manually, but rather specify a policy according to&#xA;which restic should automatically remove snapshots (so you don&amp;rsquo;t have to bother&#xA;with them). The remainder of this post will give a short introduction on how&#xA;you can use the new commands to implement your own strategy for limiting growth&#xA;of the restic repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>restic 0.2.0 released</title>
      <link>https://restic.net/blog/2016-08-05/restic-0.2.0-released/</link>
      <pubDate>Fri, 05 Aug 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-08-05/restic-0.2.0-released/</guid>
      <description>&lt;p&gt;A few days ago we&amp;rsquo;ve released &lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.2.0&#34;&gt;restic 0.2.0&lt;/a&gt;,&#xA;the detailed change log and released files can be found over at GitHub:&#xA;&lt;a href=&#34;https://github.com/restic/restic/releases/tag/v0.2.0&#34;&gt;https://github.com/restic/restic/releases/tag/v0.2.0&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;This release includes around 550 commits since version 0.1.0 (August 2015).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Documentation and Manual</title>
      <link>https://restic.net/blog/2016-02-24/Documentation/</link>
      <pubDate>Wed, 24 Feb 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-02-24/Documentation/</guid>
      <description>&lt;p&gt;Documentation in software projects is one of the things most developers hate.&#xA;It is no secret that the docs always seem to be out of date.&lt;/p&gt;&#xA;&lt;p&gt;In order to improve this situation for restic, since a &lt;a href=&#34;https://github.com/restic/restic/commit/eaa2f899d5f7c1d6e21d058cd5f5b6dc65eb45e6&#34;&gt;few days&#xA;ago&lt;/a&gt;&#xA;the manual and documentation is part of the main restic repository. Having the&#xA;documentation in the main repository means that all users have instant access&#xA;to the exact version of the documentation they&amp;rsquo;ll need and developers can&#xA;document new features in the same Pull Request they&amp;rsquo;re submitting the code.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenChaos at CCC Cologne: restic - Backups mal richtig</title>
      <link>https://restic.net/blog/2016-02-04/CCC-Cologne-OpenChaos/</link>
      <pubDate>Thu, 04 Feb 2016 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2016-02-04/CCC-Cologne-OpenChaos/</guid>
      <description>&lt;p&gt;On Friday, 30 January &lt;a href=&#34;https://github.com/fd0&#34;&gt;fd0&lt;/a&gt; gave a talk at the &lt;a href=&#34;http://koeln.ccc.de&#34;&gt;Chaos&#xA;Computer Club Cologne (C4) e.V.&lt;/a&gt; in Cologne, Germany in&#xA;their monthly series of public lectures called OpenChaos. Unfortunately for our&#xA;international readers the talk was given in German.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://media.ccc.de/v/c4.openchaos.2016.01.restic&#34;&gt;The recording&lt;/a&gt; is embedded&#xA;below. If you&amp;rsquo;ve watched the talk and have a question or other feedback, please&#xA;&lt;a href=&#34;https://restic.net/#contact&#34;&gt;contact fd0&lt;/a&gt;, he&amp;rsquo;d love to hear your feedback!&lt;/p&gt;&#xA;&lt;iframe width=&#34;853&#34; height=&#34;480&#34; src=&#34;//media.ccc.de/v/c4.openchaos.2016.01.restic/oembed&#34; frameborder=&#34;0&#34; allowfullscreen&gt;&lt;/iframe&gt;</description>
    </item>
    <item>
      <title>Verifying Code Archive Integrity</title>
      <link>https://restic.net/blog/2015-09-16/verifying-code-archive-integrity/</link>
      <pubDate>Wed, 16 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2015-09-16/verifying-code-archive-integrity/</guid>
      <description>&lt;p&gt;The restic project and all the source code, even this website is hosted by&#xA;GitHub, and they provide an awesome service! This post describes how we sign&#xA;releases of restic by using &lt;a href=&#34;https://www.gnupg.org&#34;&gt;GnuPG&lt;/a&gt; so you can&#xA;independently verify the integrity of the source code. In addition it is show&#xA;how the automatically generated &lt;code&gt;tar.gz&lt;/code&gt; files can be recreated with from the&#xA;git repository.&lt;/p&gt;&#xA;&lt;h3 id=&#34;signing-git-tags&#34;&gt;Signing Git Tags&lt;/h3&gt;&#xA;&lt;p&gt;In a git repository, &amp;ldquo;tags&amp;rdquo; can be created which basically are just named&#xA;pointers to a commit, optionally annotated with other data. You can read about&#xA;tags in detail &lt;a href=&#34;https://git-scm.com/book/en/v2/Git-Basics-Tagging&#34;&gt;here&lt;/a&gt;.&#xA;Creating a signed tag is really easy: just call &lt;code&gt;git tag&lt;/code&gt; with &lt;code&gt;--annotate&lt;/code&gt; and&#xA;&lt;code&gt;--sign&lt;/code&gt;, e.g. to sign the current commit as version 0.1.0 run:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Foundation - Introducing Content Defined Chunking (CDC)</title>
      <link>https://restic.net/blog/2015-09-12/restic-foundation1-cdc/</link>
      <pubDate>Sat, 12 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2015-09-12/restic-foundation1-cdc/</guid>
      <description>&lt;p&gt;This post will explain Content Defined Chunking (CDC) and how it is used by&#xA;restic.&lt;/p&gt;&#xA;&lt;p&gt;Backup programs need to deal with large volumes of changing data. Saving the&#xA;whole copy of each file again to the backup location when a subsequent (usually&#xA;called &amp;ldquo;incremental&amp;rdquo;) backup is created is not efficient. Over time, different&#xA;strategies have emerged to handle data in such a case.&lt;/p&gt;&#xA;&lt;p&gt;In a backup program, data de-duplication can be applied in two locations:&#xA;Removing duplicate data from the same or different files within the same backup&#xA;process (&lt;em&gt;inter-file de-duplication&lt;/em&gt;), e.g. during the initial backup, or&#xA;removing it between several backups that contain some of the same data&#xA;(&lt;em&gt;inter-backup de-duplication&lt;/em&gt;). While the former is desirable to have, the&#xA;latter is much more important.&lt;/p&gt;</description>
    </item>
    <item>
      <title>FrOSCon 2015 Lecture: A Solution to the Backup Inconvenience</title>
      <link>https://restic.net/blog/2015-09-12/FROSCON-2015-talk-about-restic/</link>
      <pubDate>Sat, 12 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2015-09-12/FROSCON-2015-talk-about-restic/</guid>
      <description>&lt;p&gt;For the tenth time, FrOSCon took place at the University of Applied Sciences&#xA;Bonn-Rhein-Sieg in Sankt Augustin near Bonn/Cologne on 22nd and 23rd of August.&#xA;We took the chance and submitted a talk about restic titled &amp;ldquo;A Solution to the&#xA;Backup Inconvenience&amp;rdquo;, which was accepted.&lt;/p&gt;&#xA;&lt;p&gt;You can watch &lt;a href=&#34;https://media.ccc.de/browse/conferences/froscon/2015/froscon2015-1515-a_solution_to_the_backup_inconvenience.html&#34;&gt;the recording&lt;/a&gt;&#xA;and view &lt;a href=&#34;http://programm.froscon.de/2015/system/attachments/341/original/Presentation_Froscon.pdf&#34;&gt;the slides&lt;/a&gt;.&#xA;If you do so, please &lt;del&gt;&lt;a href=&#34;&#34;&gt;leave feedback&lt;/a&gt;&lt;/del&gt;&lt;sup&gt;1&lt;/sup&gt;&lt;/p&gt;&#xA;&lt;p&gt;The recording is embedded below:&lt;/p&gt;&#xA;&lt;iframe width=&#34;853&#34; height=&#34;480&#34; src=&#34;//media.ccc.de/v/froscon2015-1515-a_solution_to_the_backup_inconvenience/oembed&#34; frameborder=&#34;0&#34; allowfullscreen&gt;&lt;/iframe&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;&lt;em&gt;[1] The feedback link is non-functional (2020-10-06)&lt;/em&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Introduction to the restic Blog - Welcome!</title>
      <link>https://restic.net/blog/2015-09-12/intro/</link>
      <pubDate>Sat, 12 Sep 2015 00:00:00 +0000</pubDate>
      <guid>https://restic.net/blog/2015-09-12/intro/</guid>
      <description>&lt;p&gt;If you&amp;rsquo;re reading this, you&amp;rsquo;ve found your way to the restic development blog,&#xA;awesome! Let me welcome you on behalf of the whole development team.&lt;/p&gt;&#xA;&lt;p&gt;In this blog we&amp;rsquo;ll publish articles that explain the foundation techniques that&#xA;restic is built upon and will give some insights into what&amp;rsquo;s happening on the&#xA;development side of restic. Once restic is widely in use, we&amp;rsquo;ll probably shift&#xA;the focus a bit towards the user perspective of backups and present tips and&#xA;tricks for using restic more efficiently.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
