2
2
mirror of https://github.com/octoleo/restic.git synced 2024-11-02 11:46:36 +00:00
Go to file
Klaus Post 2e7b40baca Make UID/GID '0' on Windows.
We ignore parser errors on Uid/Gid, since they are not numbers on Windows.

UID/GID is usually 'root' on Linux, so I am not sure if 0/0 is a good idea.
Maybe if the type of the fields were changed from uint32 to int, we could set it
to -1 to indicate "no value".
2015-08-14 15:50:14 +02:00
backend Only use Setsid on Unix. 2015-08-14 15:32:07 +02:00
checker Remove dead code 2015-07-26 14:56:34 +02:00
cmd/restic Change repository type detection to first check if path is a directory that exists. 2015-08-14 15:39:16 +02:00
crypto Extract chunker 2015-07-08 16:58:23 -04:00
debug Fix debug functions 2015-06-24 20:00:01 +02:00
doc doc: Add obsolete Index files 2015-07-05 11:07:10 +02:00
filter Add exclude filter to archiver and 'backup' command 2015-07-20 19:21:01 +02:00
fuse fuse test: remove debug output 2015-07-26 20:57:03 +02:00
Godeps Update bazil.org/fuse version 2015-07-19 23:03:32 +02:00
pack Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00
pipe Remove dead code 2015-07-26 14:56:34 +02:00
repository Address code review comments 2015-07-26 18:01:20 +02:00
test Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00
.gitignore Add Vagrantfile 2015-07-18 23:25:30 +02:00
.travis.yml Don't test fuse on non-darwin 2015-07-19 23:24:52 +02:00
archiver_int_test.go restorer: unexport archive pipe 2015-05-02 15:31:31 +02:00
archiver_test.go Extract chunker 2015-07-08 16:58:23 -04:00
archiver.go Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00
build.go Output EXE file on Windows platform. 2015-08-14 15:08:07 +02:00
cache_test.go tests: Remove more flags 2015-06-28 13:52:22 +02:00
cache.go Refactor configuration of cache dir and repository 2015-06-07 18:15:03 +02:00
CONTRIBUTING.md Add a word about git commits 2015-08-12 20:38:43 +02:00
doc.go Add minimal documentatation to restic package 2015-05-09 12:52:46 +02:00
LICENSE LICENSE: Add email address 2014-09-18 21:10:30 +02:00
lock_test.go Use bigger offset in test to avoid random test failures. 2015-08-14 15:19:45 +02:00
lock.go Skip UID/GID and SIGHUP lock-check on Windows 2015-08-14 15:13:11 +02:00
Makefile Makefile: Use new build system 2015-06-24 20:29:58 +02:00
node_darwin.go node/Linux: Implement setting timestamps for symlinks 2015-05-14 23:06:11 +02:00
node_freebsd.go node/Linux: Implement setting timestamps for symlinks 2015-05-14 23:06:11 +02:00
node_linux.go Move error annotation for symlink timestamp restore 2015-05-16 13:25:10 +02:00
node_openbsd.go node/Linux: Implement setting timestamps for symlinks 2015-05-14 23:06:11 +02:00
node_test.go Refactor skipping symlink ModTime checks, add OpenBSD 2015-07-20 21:29:21 +02:00
node.go Reduce memory usage for fuse mount 2015-07-26 14:25:59 +02:00
progress.go Small refactorings and ceosmetic changes 2015-04-29 20:59:06 -04:00
README.md Add FROSCON talk 2015-07-25 12:17:26 +02:00
restorer.go Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00
run_tests.go run_tests: Exit with error if failed tests were found 2015-06-28 13:52:22 +02:00
snapshot_test.go tests: Standardize use of SetupRepo/Teardown 2015-06-28 13:52:22 +02:00
snapshot.go Make UID/GID '0' on Windows. 2015-08-14 15:50:14 +02:00
tree_test.go tests: Standardize use of SetupRepo/Teardown 2015-06-28 13:52:22 +02:00
tree.go Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00
Vagrantfile Fix tests on freebsd 2015-07-20 21:08:29 +02:00
walk_test.go Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00
walk.go Use array instead of hash for backend.ID 2015-07-25 18:01:57 +02:00

Stories in Ready Build Status sourcegraph status Coverage Status

WARNING

WARNING: At the moment, consider restic as alpha quality software, it is not yet finished. Do not use it for real data!

Restic

Restic is a program that does backups right. The design goals are:

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

Building

Install Go/Golang (at least version 1.3), then run go run build.go, afterwards you'll find the binary in the current directory:

$ go run build.go

$ ./restic --help
Usage:
  restic [OPTIONS] <command>

Application Options:
  -r, --repo= Repository directory to backup to/restore from

Help Options:
  -h, --help  Show this help message

Available commands:
  backup     save file/directory
  cache      manage cache
  cat        dump something
  check      check the repository
  find       find a file/directory
  init       create repository
  key        manage keys
  list       lists data
  ls         list files
  restore    restore a snapshot
  snapshots  show snapshots
  unlock     remove locks
  version    display version

A short demo recording can be found here: asciicast

Contribute and Documentation

Contributions are welcome! More information can be found in CONTRIBUTING.md. A document describing the design of restic and the data structures stored on disc is contained in doc/Design.md.

Development

For development, please have a look at CONTRIBUTING.md, especially the section "Development Environment". If you have any questions, please get in touch!

Contact

If you discover a bug or find something surprising, please feel free to open a github issue. If you would like to chat about restic, there is also the IRC channel #restic on irc.freenode.net. Or just write me an email :)

Important: If you discover something that you believe to be a possible critical security problem, please do not open a GitHub issue but send an email directly to alexander@bumpern.de. If possible, please encrypt your email using PGP (0xD3F7A907).

Talks

The following talks will be or have been given about restic:

License

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