installation.rst 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352
  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 `Debian packages`_ ``apt install borgbackup``
  36. Gentoo `ebuild`_ ``emerge borgbackup``
  37. GNU Guix `GNU Guix`_ ``guix package --install borg``
  38. Fedora/RHEL `Fedora official repository`_ ``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`_ ``nix-env -i borgbackup``
  43. OpenBSD `OpenBSD ports`_ ``pkg_add borgbackup``
  44. OpenIndiana `OpenIndiana hipster repository`_ ``pkg install borg``
  45. openSUSE `openSUSE official repository`_ ``zypper in borgbackup``
  46. OS X `Brew cask`_ ``brew cask install borgbackup``
  47. Raspbian `Raspbian testing`_ ``apt install borgbackup``
  48. Ubuntu `Ubuntu packages`_, `Ubuntu PPA`_ ``apt install borgbackup``
  49. ============ ============================================= =======
  50. .. _[community]: https://www.archlinux.org/packages/?name=borg
  51. .. _Debian packages: https://packages.debian.org/search?keywords=borgbackup&searchon=names&exact=1&suite=all&section=all
  52. .. _Fedora official repository: https://apps.fedoraproject.org/packages/borgbackup
  53. .. _FreeBSD ports: http://www.freshports.org/archivers/py-borgbackup/
  54. .. _ebuild: https://packages.gentoo.org/packages/app-backup/borgbackup
  55. .. _GNU Guix: https://www.gnu.org/software/guix/package-list.html#borg
  56. .. _pkgsrc: http://pkgsrc.se/sysutils/py-borgbackup
  57. .. _cauldron: http://madb.mageia.org/package/show/application/0/release/cauldron/name/borgbackup
  58. .. _.nix file: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/backup/borg/default.nix
  59. .. _OpenBSD ports: http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/sysutils/borgbackup/
  60. .. _OpenIndiana hipster repository: http://pkg.openindiana.org/hipster/en/search.shtml?token=borg&action=Search
  61. .. _openSUSE official repository: http://software.opensuse.org/package/borgbackup
  62. .. _Brew cask: https://caskroom.github.io/
  63. .. _Raspbian testing: http://archive.raspbian.org/raspbian/pool/main/b/borgbackup/
  64. .. _Ubuntu packages: http://packages.ubuntu.com/xenial/borgbackup
  65. .. _Ubuntu PPA: https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/borgbackup
  66. Please ask package maintainers to build a package or, if you can package /
  67. submit it yourself, please help us with that! See :issue:`105` on
  68. github to followup on packaging efforts.
  69. .. _pyinstaller-binary:
  70. Standalone Binary
  71. -----------------
  72. .. note:: Releases are signed with an OpenPGP key, see
  73. :ref:`security-contact` for more instructions.
  74. |project_name| binaries (generated with `pyinstaller`_) are available
  75. on the releases_ page for the following platforms:
  76. * **Linux**: glibc >= 2.13 (ok for most supported Linux releases).
  77. Older glibc releases are untested and may not work.
  78. * **Mac OS X**: 10.10 (does not work with older OS X releases)
  79. * **FreeBSD**: 10.2 (unknown whether it works for older releases)
  80. To install such a binary, just drop it into a directory in your ``PATH``,
  81. make borg readable and executable for its users and then you can run ``borg``::
  82. sudo cp borg-linux64 /usr/local/bin/borg
  83. sudo chown root:root /usr/local/bin/borg
  84. sudo chmod 755 /usr/local/bin/borg
  85. Optionally you can create a symlink to have ``borgfs`` available, which is an
  86. alias for ``borg mount``::
  87. ln -s /usr/local/bin/borg /usr/local/bin/borgfs
  88. Note that the binary uses /tmp to unpack |project_name| with all dependencies.
  89. It will fail if /tmp has not enough free space or is mounted with the ``noexec`` option.
  90. You can change the temporary directory by setting the ``TEMP`` environment variable before running |project_name|.
  91. If a new version is released, you will have to manually download it and replace
  92. the old version using the same steps as shown above.
  93. Windows zip
  94. +++++++++++
  95. Tested on Windows10. (Should work on Vista and up)
  96. To install on Windows just extract the zip anywhere and add the bin directory to your ``PATH`` environment variable.
  97. .. _pyinstaller: http://www.pyinstaller.org
  98. .. _releases: https://github.com/borgbackup/borg/releases
  99. .. _source-install:
  100. From Source
  101. -----------
  102. .. note::
  103. Some older Linux systems (like RHEL/CentOS 5) and Python interpreter binaries
  104. compiled to be able to run on such systems (like Python installed via Anaconda)
  105. might miss functions required by Borg.
  106. This issue will be detected early and Borg will abort with a fatal error.
  107. Dependencies
  108. ~~~~~~~~~~~~
  109. To install |project_name| from a source package (including pip), you have to install the
  110. following dependencies first:
  111. * `Python 3`_ >= 3.5.0, plus development headers. Even though Python 3 is not
  112. the default Python version on most systems, it is usually available as an
  113. optional install.
  114. * OpenSSL_ >= 1.0.0, plus development headers.
  115. * libacl_ (which depends on libattr_), both plus development headers.
  116. * liblz4_, plus development headers.
  117. * ZeroMQ_ >= 4.0.0, plus development headers.
  118. * some Python dependencies, pip will automatically install them for you
  119. * optionally, the llfuse_ Python package is required if you wish to mount an
  120. archive as a FUSE filesystem. See setup.py about the version requirements.
  121. * optionally libb2_. If it is not found a bundled implementation is used instead.
  122. If you have troubles finding the right package names, have a look at the
  123. distribution specific sections below or the Vagrantfile in the git repository,
  124. which contains installation scripts for a number of operating systems.
  125. In the following, the steps needed to install the dependencies are listed for a
  126. selection of platforms. If your distribution is not covered by these
  127. instructions, try to use your package manager to install the dependencies. On
  128. FreeBSD, you may need to get a recent enough OpenSSL version from FreeBSD
  129. ports.
  130. After you have installed the dependencies, you can proceed with steps outlined
  131. under :ref:`pip-installation`.
  132. Debian / Ubuntu
  133. +++++++++++++++
  134. Install the dependencies with development headers::
  135. sudo apt-get install python3 python3-dev python3-pip python-virtualenv \
  136. libssl-dev openssl \
  137. libacl1-dev libacl1 \
  138. liblz4-dev liblz4-1 \
  139. libzmq3-dev libzmq3 \
  140. build-essential
  141. sudo apt-get install libfuse-dev fuse pkg-config # optional, for FUSE support
  142. In case you get complaints about permission denied on ``/etc/fuse.conf``: on
  143. Ubuntu this means your user is not in the ``fuse`` group. Add yourself to that
  144. group, log out and log in again.
  145. Fedora / Korora
  146. +++++++++++++++
  147. .. todo:: Add zeromq, use python 3.5 or 3.6
  148. Install the dependencies with development headers::
  149. sudo dnf install python3 python3-devel python3-pip python3-virtualenv
  150. sudo dnf install openssl-devel openssl
  151. sudo dnf install libacl-devel libacl
  152. sudo dnf install lz4-devel
  153. sudo dnf install gcc gcc-c++
  154. sudo dnf install redhat-rpm-config # not needed in Korora
  155. sudo dnf install fuse-devel fuse pkgconfig # optional, for FUSE support
  156. openSUSE Tumbleweed / Leap
  157. ++++++++++++++++++++++++++
  158. .. todo:: Add zeromq, use python 3.5 or 3.6
  159. Install the dependencies automatically using zypper::
  160. sudo zypper source-install --build-deps-only borgbackup
  161. Alternatively, you can enumerate all build dependencies in the command line::
  162. sudo zypper install python3 python3-devel \
  163. libacl-devel liblz4-devel openssl-devel \
  164. python3-Cython python3-Sphinx python3-msgpack-python \
  165. python3-pytest python3-setuptools python3-setuptools_scm \
  166. python3-sphinx_rtd_theme python3-llfuse gcc gcc-c++
  167. Mac OS X
  168. ++++++++
  169. .. todo:: Add zeromq, use python 3.5 or 3.6
  170. Assuming you have installed homebrew_, the following steps will install all the
  171. dependencies::
  172. brew install python3 lz4 openssl
  173. brew install pkg-config # optional, for FUSE support
  174. pip3 install virtualenv
  175. For FUSE support to mount the backup archives, you need at least version 3.0 of
  176. FUSE for OS X, which is available as a pre-release_.
  177. .. _pre-release: https://github.com/osxfuse/osxfuse/releases
  178. FreeBSD
  179. ++++++++
  180. .. todo:: Add zeromq, use python 3.5 or 3.6
  181. Listed below are packages you will need to install Borg, its dependencies,
  182. and commands to make FUSE work for using the mount command.
  183. ::
  184. pkg install -y python3 openssl liblz4 fusefs-libs pkgconf
  185. pkg install -y git
  186. python3.4 -m ensurepip # to install pip for Python3
  187. To use the mount command:
  188. echo 'fuse_load="YES"' >> /boot/loader.conf
  189. echo 'vfs.usermount=1' >> /etc/sysctl.conf
  190. kldload fuse
  191. sysctl vfs.usermount=1
  192. Windows 10's Linux Subsystem
  193. ++++++++++++++++++++++++++++
  194. .. note::
  195. Running under Windows 10's Linux Subsystem is experimental and has not been tested much yet.
  196. Just follow the Ubuntu Linux installation steps. You can omit the FUSE stuff, it won't work anyway.
  197. Windows
  198. +++++++
  199. See development_ on how to build on windows.
  200. run `python3 buildwin32.py` to create standalone windows executable in `win32exe`.
  201. You can rename or move that folder. Add the bin folder to your ``PATH`` and you can run ``borg``.
  202. Cygwin
  203. ++++++
  204. .. note::
  205. Running under Cygwin is experimental and has only been tested with Cygwin
  206. (x86-64) v2.5.2. Remote repositories are known broken, local repositories should work.
  207. .. todo:: Add zeromq, use python 3.5 or 3.6
  208. Use the Cygwin installer to install the dependencies::
  209. python3 python3-devel python3-setuptools
  210. binutils gcc-g++
  211. libopenssl openssl-devel
  212. liblz4_1 liblz4-devel
  213. git make openssh
  214. You can then install ``pip`` and ``virtualenv``::
  215. easy_install-3.4 pip
  216. pip install virtualenv
  217. .. _pip-installation:
  218. Using pip
  219. ~~~~~~~~~
  220. Virtualenv_ can be used to build and install |project_name| without affecting
  221. the system Python or requiring root access. Using a virtual environment is
  222. optional, but recommended except for the most simple use cases.
  223. .. note::
  224. If you install into a virtual environment, you need to **activate** it
  225. first (``source borg-env/bin/activate``), before running ``borg``.
  226. Alternatively, symlink ``borg-env/bin/borg`` into some directory that is in
  227. your ``PATH`` so you can just run ``borg``.
  228. This will use ``pip`` to install the latest release from PyPi::
  229. virtualenv --python=python3 borg-env
  230. source borg-env/bin/activate
  231. # install Borg + Python dependencies into virtualenv
  232. pip install borgbackup
  233. # or alternatively (if you want FUSE support):
  234. pip install borgbackup[fuse]
  235. To upgrade |project_name| to a new version later, run the following after
  236. activating your virtual environment::
  237. pip install -U borgbackup # or ... borgbackup[fuse]
  238. .. _git-installation:
  239. Using git
  240. ~~~~~~~~~
  241. This uses latest, unreleased development code from git.
  242. While we try not to break master, there are no guarantees on anything. ::
  243. # get borg from github
  244. git clone https://github.com/borgbackup/borg.git
  245. virtualenv --python=python3 borg-env
  246. source borg-env/bin/activate # always before using!
  247. # install borg + dependencies into virtualenv
  248. cd borg
  249. pip install -r requirements.d/development.txt
  250. pip install -r requirements.d/docs.txt # optional, to build the docs
  251. pip install -r requirements.d/fuse.txt # optional, for FUSE support
  252. pip install -e . # in-place editable mode
  253. # optional: run all the tests, on all supported Python versions
  254. # requires fakeroot, available through your package manager
  255. fakeroot -u tox
  256. .. note:: As a developer or power user, you always want to use a virtual environment.