Go to file
Thomas Waldmann 3a38457def Merge branch 'merge-all' of ../attic into experimental 2015-06-05 22:58:08 +02:00
borg Merge branch 'merge-all' of ../attic into experimental 2015-06-05 22:58:08 +02:00
docs Merge branch 'merge-all' of ../attic into experimental 2015-06-05 22:58:08 +02:00
scripts fix all references to package name 2015-05-22 19:21:41 +02:00
.gitattributes fix all references to package name 2015-05-22 19:21:41 +02:00
.gitignore PR #206 - Merge branch 'fixes' of https://github.com/thomaswaldmann/attic into merge 2015-03-06 23:18:08 +01:00
.travis.yml use py.test for testing, document it 2015-05-22 21:26:41 +02:00
AUTHORS fork: s/attic/borg/g, fix URLs, add new section to AUTHORS 2015-05-13 15:02:33 +02:00
CHANGES Merge branch 'master' of github.com:jborg/attic 2015-05-31 17:37:02 +02:00
CHANGES-experimental.txt Merge branch 'merge-all' of ../attic into experimental 2015-06-05 22:58:08 +02:00
LICENSE fork: s/attic/borg/g, fix URLs, add new section to AUTHORS 2015-05-13 15:02:33 +02:00
MANIFEST.in fix all references to package name 2015-05-22 19:21:41 +02:00
README.rst Merge branch 'merge-all' of ../attic into experimental 2015-06-05 22:58:08 +02:00
setup.cfg add flake8 configuration (style checker) 2015-05-22 21:28:00 +02:00
setup.py Merge branch 'merge-all' of ../attic into experimental 2015-06-05 22:58:08 +02:00
tox.ini use py.test for testing, document it 2015-05-22 21:26:41 +02:00
versioneer.py upgrade versioneer to 0.14, makes PEP440 compliant version numbers now 2015-05-14 01:25:18 +02:00

README.rst

|build|

What is Borg?
-------------
Borg is a deduplicating backup program. The main goal of Borg is to provide
an efficient and secure way to backup data. The data deduplication
technique used makes Borg suitable for daily backups since only changes
are stored.

Borg is a fork of Attic and maintained by "The Borg Collective" (see AUTHORS file).

BORG IS NOT COMPATIBLE WITH ORIGINAL ATTIC.
UNTIL FURTHER NOTICE, EXPECT THAT WE WILL BREAK COMPATIBILITY REPEATEDLY.
THIS IS SOFTWARE IN DEVELOPMENT, DECIDE YOURSELF IF IT FITS YOUR NEEDS.

Read issue #1 on the issue tracker, goals are being defined there.

Please also see the LICENSE for more informations.

Easy to use
~~~~~~~~~~~
Initialize backup repository and create a backup archive::

    $ borg init /mnt/backup
    $ borg create -v /mnt/backup::documents ~/Documents

Main features
~~~~~~~~~~~~~
Space efficient storage
  Variable block size deduplication is used to reduce the number of bytes 
  stored by detecting redundant data. Each file is split into a number of
  variable length chunks and only chunks that have never been seen before are
  compressed and added to the repository.

Optional data encryption
    All data can be protected using 256-bit AES encryption and data integrity
    and authenticity is verified using a MAC (message authentication code).

Off-site backups
    Borg can store data on any remote host accessible over SSH.  This is
    most efficient if Borg is also installed on the remote host.

Backups mountable as filesystems
    Backup archives are mountable as userspace filesystems for easy backup
    verification and restores.

What do I need?
---------------
Borg requires Python 3.2 or above to work.
Borg also requires a sufficiently recent OpenSSL (>= 1.0.0).
In order to mount archives as filesystems, llfuse is required.
For other python requirements, please see setup.py install_requires.

How do I install it?
--------------------
::

  $ pip3 install borgbackup

Where are the docs?
-------------------
Go to https://borgbackup.github.io/ for a prebuilt version of the documentation.
You can also build it yourself from the docs folder.

Where are the tests?
--------------------
The tests are in the borg/testsuite package. To run the test suite use the
following command::

  $ fakeroot -u tox  # you need to have tox installed

.. |build| image:: https://travis-ci.org/borgbackup/borg.svg
        :alt: Build Status
        :target: https://travis-ci.org/borgbackup/borg