README.rst 8.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207
  1. |screencast|
  2. .. highlight:: bash
  3. What is BorgBackup?
  4. ===================
  5. BorgBackup (short: Borg) is a deduplicating backup program.
  6. Optionally, it supports compression and authenticated encryption.
  7. The main goal of Borg is to provide an efficient and secure way to backup data.
  8. The data deduplication technique used makes Borg suitable for daily backups
  9. since only changes are stored.
  10. The authenticated encryption technique makes it suitable for backups to not
  11. fully trusted targets.
  12. See the `installation manual`_ or, if you have already
  13. downloaded Borg, ``docs/installation.rst`` to get started with Borg.
  14. .. _installation manual: https://borgbackup.readthedocs.org/en/stable/installation.html
  15. Main features
  16. -------------
  17. **Space efficient storage**
  18. Deduplication based on content-defined chunking is used to reduce the number
  19. of bytes stored: each file is split into a number of variable length chunks
  20. and only chunks that have never been seen before are added to the repository.
  21. To deduplicate, all the chunks in the same repository are considered, no
  22. matter whether they come from different machines, from previous backups,
  23. from the same backup or even from the same single file.
  24. Compared to other deduplication approaches, this method does NOT depend on:
  25. * file/directory names staying the same: So you can move your stuff around
  26. without killing the deduplication, even between machines sharing a repo.
  27. * complete files or time stamps staying the same: If a big file changes a
  28. little, only a few new chunks need to be stored - this is great for VMs or
  29. raw disks.
  30. * The absolute position of a data chunk inside a file: Stuff may get shifted
  31. and will still be found by the deduplication algorithm.
  32. **Speed**
  33. * performance critical code (chunking, compression, encryption) is
  34. implemented in C/Cython
  35. * local caching of files/chunks index data
  36. * quick detection of unmodified files
  37. **Data encryption**
  38. All data can be protected using 256-bit AES encryption, data integrity and
  39. authenticity is verified using HMAC-SHA256. Data is encrypted clientside.
  40. **Compression**
  41. All data can be compressed by lz4 (super fast, low compression), zlib
  42. (medium speed and compression) or lzma (low speed, high compression).
  43. **Off-site backups**
  44. Borg can store data on any remote host accessible over SSH. If Borg is
  45. installed on the remote host, big performance gains can be achieved
  46. compared to using a network filesystem (sshfs, nfs, ...).
  47. **Backups mountable as filesystems**
  48. Backup archives are mountable as userspace filesystems for easy interactive
  49. backup examination and restores (e.g. by using a regular file manager).
  50. **Easy installation on multiple platforms**
  51. We offer single-file binaries that do not require installing anything -
  52. you can just run them on these platforms:
  53. * Linux
  54. * Mac OS X
  55. * FreeBSD
  56. * OpenBSD and NetBSD (no xattrs/ACLs support or binaries yet)
  57. * Cygwin (not supported, no binaries yet)
  58. **Free and Open Source Software**
  59. * security and functionality can be audited independently
  60. * licensed under the BSD (3-clause) license
  61. Easy to use
  62. -----------
  63. Initialize a new backup repository and create a backup archive::
  64. $ borg init /path/to/repo
  65. $ borg create /path/to/repo::Saturday1 ~/Documents
  66. Now doing another backup, just to show off the great deduplication:
  67. .. code-block:: none
  68. $ borg create -v --stats /path/to/repo::Saturday2 ~/Documents
  69. -----------------------------------------------------------------------------
  70. Archive name: Saturday2
  71. Archive fingerprint: 622b7c53c...
  72. Time (start): Sat, 2016-02-27 14:48:13
  73. Time (end): Sat, 2016-02-27 14:48:14
  74. Duration: 0.88 seconds
  75. Number of files: 163
  76. -----------------------------------------------------------------------------
  77. Original size Compressed size Deduplicated size
  78. This archive: 6.85 MB 6.85 MB 30.79 kB <-- !
  79. All archives: 13.69 MB 13.71 MB 6.88 MB
  80. Unique chunks Total chunks
  81. Chunk index: 167 330
  82. -----------------------------------------------------------------------------
  83. For a graphical frontend refer to our complementary project `BorgWeb <https://borgweb.readthedocs.io/>`_.
  84. Checking Release Authenticity and Security Contact
  85. ==================================================
  86. `Releases <https://github.com/borgbackup/borg/releases>`_ are signed with this GPG key,
  87. please use GPG to verify their authenticity.
  88. In case you discover a security issue, please use this contact for reporting it privately
  89. and please, if possible, use encrypted E-Mail:
  90. Thomas Waldmann <tw@waldmann-edv.de>
  91. GPG Key Fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393
  92. The public key can be fetched from any GPG keyserver, but be careful: you must
  93. use the **full fingerprint** to check that you got the correct key.
  94. Links
  95. =====
  96. * `Main Web Site <https://borgbackup.readthedocs.org/>`_
  97. * `Releases <https://github.com/borgbackup/borg/releases>`_,
  98. `PyPI packages <https://pypi.python.org/pypi/borgbackup>`_ and
  99. `ChangeLog <https://github.com/borgbackup/borg/blob/master/docs/changes.rst>`_
  100. * `GitHub <https://github.com/borgbackup/borg>`_,
  101. `Issue Tracker <https://github.com/borgbackup/borg/issues>`_ and
  102. `Bounties & Fundraisers <https://www.bountysource.com/teams/borgbackup>`_
  103. * `Web-Chat (IRC) <http://webchat.freenode.net/?randomnick=1&channels=%23borgbackup&uio=MTY9dHJ1ZSY5PXRydWUa8>`_ and
  104. `Mailing List <https://mail.python.org/mailman/listinfo/borgbackup>`_
  105. * `License <https://borgbackup.readthedocs.org/en/stable/authors.html#license>`_
  106. Notes
  107. -----
  108. Borg is a fork of `Attic`_ and maintained by "`The Borg collective`_".
  109. .. _Attic: https://github.com/jborg/attic
  110. .. _The Borg collective: https://borgbackup.readthedocs.org/en/latest/authors.html
  111. Differences between Attic and Borg
  112. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  113. Here's a (incomplete) list of some major changes:
  114. * more open, faster paced development (see `issue #1 <https://github.com/borgbackup/borg/issues/1>`_)
  115. * lots of attic issues fixed (see `issue #5 <https://github.com/borgbackup/borg/issues/5>`_)
  116. * less chunk management overhead (less memory and disk usage for chunks index)
  117. * faster remote cache resync (useful when backing up multiple machines into same repo)
  118. * compression: no, lz4, zlib or lzma compression, adjustable compression levels
  119. * repokey replaces problematic passphrase mode (you can't change the passphrase nor the pbkdf2 iteration count in "passphrase" mode)
  120. * simple sparse file support, great for virtual machine disk files
  121. * can read special files (e.g. block devices) or from stdin, write to stdout
  122. * mkdir-based locking is more compatible than attic's posix locking
  123. * uses fadvise to not spoil / blow up the fs cache
  124. * better error messages / exception handling
  125. * better logging, screen output, progress indication
  126. * tested on misc. Linux systems, 32 and 64bit, FreeBSD, OpenBSD, NetBSD, Mac OS X
  127. Please read the `ChangeLog`_ (or ``docs/changes.rst`` in the source distribution) for more
  128. information.
  129. BORG IS NOT COMPATIBLE WITH ORIGINAL ATTIC (but there is a one-way conversion).
  130. EXPECT THAT WE WILL BREAK COMPATIBILITY REPEATEDLY WHEN MAJOR RELEASE NUMBER
  131. CHANGES (like when going from 0.x.y to 1.0.0 or from 1.x.y to 2.0.0).
  132. NOT RELEASED DEVELOPMENT VERSIONS HAVE UNKNOWN COMPATIBILITY PROPERTIES.
  133. THIS IS SOFTWARE IN DEVELOPMENT, DECIDE YOURSELF WHETHER IT FITS YOUR NEEDS.
  134. Borg is distributed under a 3-clause BSD license, see `License`_ for the complete license.
  135. |doc| |build| |coverage| |bestpractices|
  136. .. |doc| image:: https://readthedocs.org/projects/borgbackup/badge/?version=stable
  137. :alt: Documentation
  138. :target: https://borgbackup.readthedocs.org/en/stable/
  139. .. |build| image:: https://api.travis-ci.org/borgbackup/borg.svg
  140. :alt: Build Status
  141. :target: https://travis-ci.org/borgbackup/borg
  142. .. |coverage| image:: https://codecov.io/github/borgbackup/borg/coverage.svg?branch=master
  143. :alt: Test Coverage
  144. :target: https://codecov.io/github/borgbackup/borg?branch=master
  145. .. |screencast| image:: https://asciinema.org/a/28691.png
  146. :alt: BorgBackup Installation and Basic Usage
  147. :target: https://asciinema.org/a/28691?autoplay=1&speed=2
  148. .. |bestpractices| image:: https://bestpractices.coreinfrastructure.org/projects/271/badge
  149. :alt: Best Practices Score
  150. :target: https://bestpractices.coreinfrastructure.org/projects/271