installation.rst 14 KB

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