Cleanups for cmd_debug/repository and remove dead code from restic package
|4 days ago|
|.github||2 weeks ago|
|changelog||4 days ago|
|cmd/restic||4 days ago|
|contrib||1 year ago|
|doc||4 days ago|
|docker||1 year ago|
|helpers||4 weeks ago|
|internal||4 days ago|
|.dockerignore||1 year ago|
|.gitattributes||4 months ago|
|.gitignore||2 years ago|
|.golangci.yml||1 week ago|
|CHANGELOG.md||1 month ago|
|CONTRIBUTING.md||2 months ago|
|GOVERNANCE.md||4 years ago|
|LICENSE||5 years ago|
|Makefile||3 years ago|
|README.md||11 months ago|
|VERSION||1 month ago|
|build.go||7 months ago|
|doc.go||2 months ago|
|go.mod||1 month ago|
|go.sum||1 month ago|
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.
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
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:
- Local directory
- sftp server (via SSH)
- HTTP REST server (protocol, rest-server)
- Amazon S3 (either from Amazon or using the Minio server)
- OpenStack Swift
- BackBlaze B2
- Microsoft Azure Blob Storage
- Google Cloud Storage
- And many other services via the rclone Backend
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.
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.
Backend integration tests for Google Cloud Storage and Microsoft Azure Blob Storage are sponsored by AppsCode!