installation.rst 11 KB

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