Go to file
Michael Eischer e4bbde7036 rclone: Workaround for incorrect "not found" errors while listing files
rclone returns a "not found" error if an internal error occurs while
listing a folder. Ignoring this error lets restic erroneously think that
there are no files, which can cause `prune` to wipe the whole
repository.
2024-01-09 18:28:17 +01:00
.github sync CI and go dependencies with master branch 2024-01-08 21:33:05 +01:00
changelog rclone: Workaround for incorrect "not found" errors while listing files 2024-01-09 18:28:17 +01:00
cmd/restic Fix repository not being printed when using repository file 2024-01-08 21:33:05 +01:00
contrib bump cobra and add completions for fish 2021-05-21 13:47:52 +10:00
doc Add a note that the oldest snapshot may be kept additionally 2024-01-08 21:33:05 +01:00
docker Remove additional `--update` for apk in Dockerfile 2023-10-01 18:00:15 +08:00
helpers Restore support for ARMv5 platforms 2023-10-27 19:52:14 +02:00
internal rclone: Workaround for incorrect "not found" errors while listing files 2024-01-09 18:28:17 +01:00
.gitattributes internal/repository: Fix LoadBlob + fuzz test 2022-06-06 17:02:28 +02:00
.gitignore Added restic.exe to the .gitignore 2023-03-28 23:07:25 -04:00
.golangci.yml Ignore deprecated imports for poly1305 and openpgp 2023-05-18 21:15:45 +02:00
.readthedocs.yaml Remove readthedocs special case from docs configuration 2023-10-27 19:47:19 +02:00
CHANGELOG.md regenerate changelog 2024-01-08 21:33:05 +01:00
CONTRIBUTING.md ask for debug statistics in resource usage issues 2023-07-08 23:04:47 +02:00
GOVERNANCE.md Document project governance 2018-05-28 22:29:06 +02:00
LICENSE Update LICENSE 2017-11-02 11:39:49 +01:00
Makefile Remove vendor from build scripts 2020-03-01 11:30:02 +01:00
README.md README: add Mastodon link 2023-08-27 10:52:12 +02:00
VERSION Add version for 0.16.2 2023-10-29 19:50:07 +01:00
build.go bump minimum go version on Solaris to 1.20 2023-04-07 15:40:57 +02:00
doc.go gofmt all files 2022-08-19 19:12:26 +02:00
go.mod sync CI and go dependencies with master branch 2024-01-08 21:33:05 +01:00
go.sum sync CI and go dependencies with master branch 2024-01-08 21:33:05 +01:00

README.md

Documentation Build Status Go Report Card

Introduction

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.

Backends

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.

News

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

License

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

Sponsorship

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

Sponsored by AppsCode