Restic clone for my possible forks
Go to file
Michael Dorner fe3f326d8d
- improved formatting of license information (BSD 2-clase) so Github can automatically detect it.
2017-11-02 11:39:49 +01:00
.github Update issue template 2017-10-21 10:17:58 +02:00
cmd/restic Merge pull request #1389 from wojas/fix-modtime-tests-on-apfs 2017-10-29 14:20:40 +01:00
doc Use lowercase in messages from check/tag commands, too 2017-10-27 21:06:34 +02:00
docker install fuse and ca-certificates 2017-06-23 10:38:19 +02:00
internal Pass in a nil buffer to Open() 2017-11-01 10:30:40 +01:00
scripts Add release script 2017-09-26 22:14:58 +02:00
vendor Upadte vendored dependencies 2017-10-22 10:07:36 +02:00
.gitignore Update other files 2017-07-23 14:40:05 +02:00
.hound.yml Enable HoundCI checking for Go 2016-02-05 21:15:46 +01:00
.travis.yml travis: update go versions 2017-09-17 19:02:22 +02:00 Add entry to CHANGELOG 2017-10-21 12:22:50 +02:00 Remove integration test for manpage 2017-09-26 13:16:55 +02:00
Gopkg.lock Upadte vendored dependencies 2017-10-22 10:07:36 +02:00
Gopkg.toml Remove explicit version constraints 2017-10-22 10:07:23 +02:00
LICENSE Update LICENSE 2017-11-02 11:39:49 +01:00
Makefile test 2017-09-09 16:33:51 +02:00
README.rst Update README.rst 2017-11-02 11:36:25 +01:00
VERSION Add VERSION file for 0.7.3 2017-09-20 20:50:07 +02:00
appveyor.yml Update Go versions for CI 2017-09-02 09:29:02 +02:00
build.go Upgrade min Go version to 1.8 2017-08-06 21:47:04 +02:00
run_integration_tests.go CI: Check the vendor dir and Gopkg.lock 2017-10-21 10:50:38 +02:00


|Documentation| |Build Status| |Build status| |Report Card| |Say Thanks| |TestCoverage|


restic is a backup program that is fast, efficient and secure.

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 -r /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/rest_backend.rst>`__ `rest-server <>`__)
- `AWS S3 <>`__ (either from Amazon or using the `Minio <>`__ server)
- `OpenStack Swift <>`__
- `BackBlaze B2 <>`__
- `Microsoft Azure Blob Storage <>`__
- `Google Cloud Storage <>`__

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``.

.. |Documentation| image::
.. |Build Status| image::
.. |Build status| image::
.. |Report Card| image::
.. |Say Thanks| image::!-1EAEDB.svg
.. |TestCoverage| image::