You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
MichaelEischer 814a399e4c
Merge pull request #3283 from dennypage/master
1 week ago
.github Update golangci-lint version 1 month ago
changelog Merge pull request #3283 from dennypage/master 1 week ago
cmd/restic Merge pull request #3283 from dennypage/master 1 week ago
contrib Small change for RHEL6 which does not know about the %license macro 2 years ago
doc Update manpages and auto-completion 3 weeks ago
docker [FIX] Timezone in docker image 3 months ago
helpers helpers: Also push versioned image to Docker 2 weeks ago
internal local: Ignore files in intermediate folders 1 week ago
.gitignore Add .vscode to gitignore 4 months ago
.golangci.yml Add config for golangci-lint 1 month ago Generate for 0.12.0 3 weeks ago Add a section explaining golangci-lint 1 month ago Document project governance 2 years ago
LICENSE Update LICENSE 3 years ago
Makefile Remove vendor from build scripts 1 year ago Replace badges in README 3 months ago
VERSION Add version for 0.12.0 3 weeks ago
build.go Drop support for Go version 1.11 7 months ago
doc.go Add minimal docs for the top-level package 2 years ago
go.mod Update pkg/xattr to handle EINTR on Linux 3 months ago
go.sum Update pkg/xattr to handle EINTR on Linux 3 months ago

Documentation Build Status Go Report Card


restic is a backup program that is fast, efficient and secure. It supports the three major operating systems (Linux, macOS, Windows) and a few smaller ones (FreeBSD, OpenBSD).

For detailed usage and installation instructions check out the documentation.

You can ask questions in our Discourse forum.

Quick start

Once you’ve installed restic, start off with creating a repository for your backups:

$ restic init --repo /tmp/backup
enter password for new backend:
enter password again:
created restic backend 085b3c76b9 at /tmp/backup
Please note that knowledge of your password is required to access the repository.
Losing your password means that your data is irrecoverably lost.

and add some data:

$ restic --repo /tmp/backup backup ~/work
enter password for repository:
scan [/home/user/work]
scanned 764 directories, 1816 files in 0:00
[0:29] 100.00%  54.732 MiB/s  1.582 GiB / 1.582 GiB  2580 / 2580 items  0 errors  ETA 0:00
duration: 0:29, 54.47MiB/s
snapshot 40dc1520 saved

Next you can either use restic restore to restore files or use restic mount to mount the repository via fuse and browse the files from previous snapshots.

For more options check out the online documentation.


Saving a backup on the same machine is nice but not a real backup strategy. Therefore, restic supports the following backends for storing backups natively:

Design Principles

Restic is a program that does backups right and was designed with the following principles in mind:

  • Easy: Doing backups should be a frictionless process, otherwise you might be tempted to skip it. Restic should be easy to configure and use, so that, in the 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 back end to save precious backup space.

Reproducible Builds

The binaries released with each restic version starting at 0.6.1 are reproducible, which means that you can reproduce a byte identical version from the source code for that release. Instructions on how to do that are contained in the builder repository.


You can follow the restic project on Twitter @resticbackup or by subscribing to the project blog.


Restic is licensed under BSD 2-Clause License. You can find the complete text in LICENSE.


Backend integration tests for Google Cloud Storage and Microsoft Azure Blob Storage are sponsored by AppsCode!

Sponsored by AppsCode