installation.rst 14 KB

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