restic is a program that does backups right. The design goals are:
Easy: Doing backups should be a frictionless process, otherwise you are tempted to skip it. Restic should be easy to configure and use, so that in the unlikely event of a data loss you can just restore it. Likewise, restoring data should not be complicated.
Fast: Backing up your data with restic should only be limited by your network or hard disk bandwidth so that you can backup your files every day. Nobody does backups if it takes too much time. Restoring backups should only transfer data that is needed for the files that are to be restored, so that this process is also fast.
Verifiable: Much more important than backup is restore, so restic enables you to easily verify that all data can be restored.
Secure: Restic uses cryptography to guarantee confidentiality and integrity of your data. The location the backup data is stored is assumed not to be a trusted environment (e.g. a shared space where others like system administrators are able to access your backups). Restic is built to secure your data against such attackers.
Efficient: With the growth of data, additional snapshots should only take the storage of the actual increment. Even more, duplicate data should be de-duplicated before it is actually written to the storage backend to save precious backup space.
A short recorded demo of restic:
To learn more about restic, checkout the user manual:
Backward compatibility for backups is important so that our users are always able to restore saved data. Therefore restic follows Semantic Versioning to clearly define which versions are compatible. The repository and data structures contained therein are considered the “Public API” in the sense of Semantic Versioning.
We guarantee backward compatibility of all repositories within one major version; as long as we do not increment the major version, data can be read and restored. We strive to be fully backward compatible to all prior versions.
Contributions are welcome! More information can be found in the restic contribution guidelines. A document describing the design of restic and the data structures stored on disc is contained in the design document.
If you discover a bug or find something surprising, please feel free to open a github issue. If you would like to chat about restic, there is also the IRC channel
irc.freenode.net. Or just write an email :)
Important: If you discover something that you believe to be a possible critical security problem, please do not open a GitHub issue but send an email directly to firstname.lastname@example.org. If possible, please encrypt your email using PGP (0xD3F7A907).
The following talks will be or have been given about restic:
For more information regarding restic development, have a look at our blog. The latest posts are:
14 Aug 2017 » Meeting at FrOSCon 2017 - Details
11 Aug 2017 » Discourse Forum
25 Jul 2017 » Please upgrade to restic 0.7.1!
Restic is licensed under “BSD 2-Clause License”. You can find the complete text in the file