installation.rst 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279
  1. .. include:: global.rst.inc
  2. .. _installation:
  3. Installation
  4. ============
  5. There are different ways to install |project_name|:
  6. - :ref:`distribution-package` - easy and fast if a package is
  7. available from your distribution.
  8. - :ref:`pyinstaller-binary` - easy and fast, we provide a ready-to-use binary file
  9. that comes bundled with all dependencies.
  10. - :ref:`source-install`, either:
  11. - :ref:`pip-installation` - installing a source package with pip needs
  12. more installation steps and requires all dependencies with
  13. development headers and a compiler.
  14. - :ref:`git-installation` - for developers and power users who want to
  15. have the latest code or use revision control (each release is
  16. tagged).
  17. .. _distribution-package:
  18. Distribution Package
  19. --------------------
  20. Some distributions might offer a ready-to-use ``borgbackup``
  21. package which can be installed with the package manager. As |project_name| is
  22. still a young project, such a package might be not available for your system
  23. yet.
  24. ============ ============================================= =======
  25. Distribution Source Command
  26. ============ ============================================= =======
  27. Arch Linux `[community]`_ ``pacman -S borg``
  28. Debian `jessie-backports`_, `stretch`_, `sid`_ ``apt install borgbackup``
  29. Gentoo `ebuild`_ ``emerge borgbackup``
  30. GNU Guix `GNU Guix`_ ``guix package --install borg``
  31. NetBSD `pkgsrc`_ ``pkg_add py-borgbackup``
  32. NixOS `.nix file`_ N/A
  33. OpenBSD `OpenBSD ports`_ ``pkg_add borgbackup``
  34. openSUSE `openSUSE official repository`_ ``zypper in python3-borgbackup``
  35. OS X `Brew cask`_ ``brew cask install borgbackup``
  36. Ubuntu `16.04`_, backports (PPA): `15.10`_, `14.04`_ ``apt install borgbackup``
  37. ============ ============================================= =======
  38. .. _[community]: https://www.archlinux.org/packages/?name=borg
  39. .. _jessie-backports: https://packages.debian.org/jessie-backports/borgbackup
  40. .. _stretch: https://packages.debian.org/stretch/borgbackup
  41. .. _unstable/sid: https://packages.debian.org/sid/borgbackup
  42. .. _ebuild: https://packages.gentoo.org/packages/app-backup/borgbackup
  43. .. _pkgsrc: http://pkgsrc.se/sysutils/py-borgbackup
  44. .. _16.04: https://launchpad.net/ubuntu/xenial/+source/borgbackup
  45. .. _15.10: https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  46. .. _14.04: https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  47. .. _.nix file: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/backup/borg/default.nix
  48. .. _OpenBSD ports: http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/borgbackup/
  49. .. _openSUSE official repository: http://software.opensuse.org/package/python3-borgbackup
  50. .. _Brew cask: http://caskroom.io/
  51. .. _GNU Guix: https://www.gnu.org/software/guix/package-list.html#borg
  52. Please ask package maintainers to build a package or, if you can package /
  53. submit it yourself, please help us with that! See :issue:`105` on
  54. github to followup on packaging efforts.
  55. If a package is available, it might be interesting to check its version
  56. and compare that to our latest release and review the :doc:`changes`.
  57. .. _pyinstaller-binary:
  58. Standalone Binary
  59. -----------------
  60. |project_name| binaries (generated with `pyinstaller`_) are available
  61. on the releases_ page for the following platforms:
  62. * **Linux**: glibc >= 2.13 (ok for most supported Linux releases). Maybe older
  63. glibc versions also work, if they are compatible to 2.13.
  64. * **Mac OS X**: 10.10 (does not work with older OS X releases)
  65. * **FreeBSD**: 10.2 (unknown whether it works for older releases)
  66. To install such a binary, just drop it into a directory in your ``PATH``,
  67. make borg readable and executable for its users and then you can run ``borg``::
  68. sudo cp borg-linux64 /usr/local/bin/borg
  69. sudo chown root:root /usr/local/bin/borg
  70. sudo chmod 755 /usr/local/bin/borg
  71. Optionally you can create a symlink to have ``borgfs`` available, which is an
  72. alias for ``borg mount``::
  73. ln -s /usr/local/bin/borg /usr/local/bin/borgfs
  74. Note that the binary uses /tmp to unpack |project_name| with all dependencies.
  75. It will fail if /tmp has not enough free space or is mounted with the ``noexec`` option.
  76. You can change the temporary directory by setting the ``TEMP`` environment variable before running |project_name|.
  77. If a new version is released, you will have to manually download it and replace
  78. the old version using the same steps as shown above.
  79. .. _pyinstaller: http://www.pyinstaller.org
  80. .. _releases: https://github.com/borgbackup/borg/releases
  81. .. _source-install:
  82. From Source
  83. -----------
  84. Dependencies
  85. ~~~~~~~~~~~~
  86. To install |project_name| from a source package (including pip), you have to install the
  87. following dependencies first:
  88. * `Python 3`_ >= 3.4.0, plus development headers. Even though Python 3 is not
  89. the default Python version on most systems, it is usually available as an
  90. optional install.
  91. * OpenSSL_ >= 1.0.0, plus development headers.
  92. * libacl_ (that pulls in libattr_ also), both plus development headers.
  93. * liblz4_, plus development headers.
  94. * some Python dependencies, pip will automatically install them for you
  95. * optionally, the llfuse_ Python package is required if you wish to mount an
  96. archive as a FUSE filesystem. See setup.py about the version requirements.
  97. If you have troubles finding the right package names, have a look at the
  98. distribution specific sections below and also at the Vagrantfile in our repo.
  99. In the following, the steps needed to install the dependencies are listed for a
  100. selection of platforms. If your distribution is not covered by these
  101. instructions, try to use your package manager to install the dependencies. On
  102. FreeBSD, you may need to get a recent enough OpenSSL version from FreeBSD
  103. ports.
  104. After you have installed the dependencies, you can proceed with steps outlined
  105. under :ref:`pip-installation`.
  106. Debian / Ubuntu
  107. +++++++++++++++
  108. Install the dependencies with development headers::
  109. sudo apt-get install python3 python3-dev python3-pip python-virtualenv \
  110. libssl-dev openssl \
  111. libacl1-dev libacl1 \
  112. liblz4-dev liblz4-1 \
  113. build-essential
  114. sudo apt-get install libfuse-dev fuse pkg-config # optional, for FUSE support
  115. In case you get complaints about permission denied on ``/etc/fuse.conf``: on
  116. Ubuntu this means your user is not in the ``fuse`` group. Add yourself to that
  117. group, log out and log in again.
  118. Fedora / Korora
  119. +++++++++++++++
  120. Install the dependencies with development headers::
  121. sudo dnf install python3 python3-devel python3-pip python3-virtualenv
  122. sudo dnf install openssl-devel openssl
  123. sudo dnf install libacl-devel libacl
  124. sudo dnf install lz4-devel
  125. sudo dnf install gcc gcc-c++
  126. sudo dnf install fuse-devel fuse pkgconfig # optional, for FUSE support
  127. Mac OS X
  128. ++++++++
  129. Assuming you have installed homebrew_, the following steps will install all the
  130. dependencies::
  131. brew install python3 lz4 openssl
  132. pip3 install virtualenv
  133. For FUSE support to mount the backup archives, you need at least version 3.0 of
  134. FUSE for OS X, which is available as a pre-release_.
  135. .. _pre-release: https://github.com/osxfuse/osxfuse/releases
  136. FreeBSD
  137. ++++++++
  138. Listed below are packages you will need to install |project_name|, its dependencies,
  139. and commands to make fuse work for using the mount command.
  140. ::
  141. pkg install -y python3 openssl liblz4 fusefs-libs pkgconf
  142. pkg install -y git
  143. python3.4 -m ensurepip # to install pip for Python3
  144. To use the mount command:
  145. echo 'fuse_load="YES"' >> /boot/loader.conf
  146. echo 'vfs.usermount=1' >> /etc/sysctl.conf
  147. kldload fuse
  148. sysctl vfs.usermount=1
  149. Cygwin
  150. ++++++
  151. .. note::
  152. Running under Cygwin is experimental and has only been tested with Cygwin
  153. (x86-64) v2.1.0.
  154. Use the Cygwin installer to install the dependencies::
  155. python3 python3-setuptools
  156. python3-cython # not needed for releases
  157. binutils gcc-g++
  158. libopenssl openssl-devel
  159. liblz4_1 liblz4-devel # from cygwinports.org
  160. git make openssh
  161. You can then install ``pip`` and ``virtualenv``::
  162. easy_install-3.4 pip
  163. pip install virtualenv
  164. In case the creation of the virtual environment fails, try deleting this file::
  165. /usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
  166. .. _pip-installation:
  167. Using pip
  168. ~~~~~~~~~
  169. Virtualenv_ can be used to build and install |project_name| without affecting
  170. the system Python or requiring root access. Using a virtual environment is
  171. optional, but recommended except for the most simple use cases.
  172. .. note::
  173. If you install into a virtual environment, you need to **activate** it
  174. first (``source borg-env/bin/activate``), before running ``borg``.
  175. Alternatively, symlink ``borg-env/bin/borg`` into some directory that is in
  176. your ``PATH`` so you can just run ``borg``.
  177. This will use ``pip`` to install the latest release from PyPi::
  178. virtualenv --python=python3 borg-env
  179. source borg-env/bin/activate
  180. # install Borg + Python dependencies into virtualenv
  181. pip install borgbackup
  182. # or alternatively (if you want FUSE support):
  183. pip install borgbackup[fuse]
  184. To upgrade |project_name| to a new version later, run the following after
  185. activating your virtual environment::
  186. pip install -U borgbackup # or ... borgbackup[fuse]
  187. .. _git-installation:
  188. Using git
  189. ~~~~~~~~~
  190. This uses latest, unreleased development code from git.
  191. While we try not to break master, there are no guarantees on anything. ::
  192. # get borg from github
  193. git clone https://github.com/borgbackup/borg.git
  194. virtualenv --python=python3 borg-env
  195. source borg-env/bin/activate # always before using!
  196. # install borg + dependencies into virtualenv
  197. pip install sphinx # optional, to build the docs
  198. cd borg
  199. pip install -r requirements.d/development.txt
  200. pip install -r requirements.d/fuse.txt # optional, for FUSE support
  201. pip install -e . # in-place editable mode
  202. # optional: run all the tests, on all supported Python versions
  203. # requires fakeroot, available through your package manager
  204. fakeroot -u tox
  205. .. note:: As a developer or power user, you always want to use a virtual environment.