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 b84f5177cb
Merge pull request #2790 from greatroar/fix-quadratic-read
2 days ago
.github Delete (not used anymore) 3 months ago
changelog Changelog entry for subquadratic reading in mount 2 days ago
cmd/restic Replace mount's per-file cache by a global LRU cache 2 days ago
contrib Small change for RHEL6 which does not know about the %license macro 1 year ago
doc Update 040_backup.rst 2 days ago
docker Update Go version to 1.13.6 in Docker build script 5 months ago
helpers Remove -mod=vendor from all documentation and code 4 months ago
internal Replace mount's per-file cache by a global LRU cache 2 days ago
.gitignore Document the build and release processes 1 year ago
.hound.yml Enable HoundCI checking for Go 4 years ago
.travis.yml Update Go versions, drop Go 1.10 4 months ago Fix typos 1 month ago Reword parts of Providing Patches in 2 months ago Document project governance 2 years ago
LICENSE Update LICENSE 2 years ago
Makefile Remove vendor from build scripts 4 months ago
README.rst Remove coverage badge 7 months ago
VERSION Add version for 0.9.6 7 months ago
appveyor.yml Remove -mod=vendor from all documentation and code 4 months ago
build.go build: Preserve debug symbols in debug and profile build 2 months ago
doc.go Add minimal docs for the top-level package 1 year ago
go.mod Replace mount's per-file cache by a global LRU cache 2 days ago
go.sum Update for fewer allocations in http2 1 month ago
run_integration_tests.go Remove Solaris build workaround in integration tests 1 month ago


|Documentation| |Build Status| |Build status| |Report Card| |Say Thanks| |Reviewed by Hound|


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:

.. code-block:: console

$ 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:

.. code-block:: console

$ 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 <doc/100_references.rst#rest-backend>`__ `rest-server <>`__)
- `AWS 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 <>`__

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
easily 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 `development 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 <>`__!


.. |Documentation| image::
.. |Build Status| image::
.. |Build status| image::
.. |Report Card| image::
.. |Say Thanks| image::!-1EAEDB.svg
.. |AppsCode| image::
.. |Reviewed by Hound| image::