installation.rst 12 KB

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