.. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit! .. _borg_version: borg version ------------ .. code-block:: none borg [common options] version [options] [REPOSITORY] .. only:: html .. class:: borg-options-table +-------------------------------------------------------+----------------+--------------------------------------------------------+ | **positional arguments** | +-------------------------------------------------------+----------------+--------------------------------------------------------+ | | ``REPOSITORY`` | repository (used to determine client/server situation) | +-------------------------------------------------------+----------------+--------------------------------------------------------+ | .. class:: borg-common-opt-ref | | | | :ref:`common_options` | +-------------------------------------------------------+----------------+--------------------------------------------------------+ .. raw:: html .. only:: latex REPOSITORY repository (used to determine client/server situation) :ref:`common_options` | Description ~~~~~~~~~~~ This command displays the Borg client version / Borg server version. If a local repository is given, the client code directly accesses the repository, thus we show the client version also as the server version. If a remote repository is given (e.g., ssh:), the remote Borg is queried and its version is displayed as the server version. Examples:: # local repo (client uses 1.4.0 alpha version) $ borg version /mnt/backup 1.4.0a / 1.4.0a # remote repo (client uses 1.4.0 alpha, server uses 1.2.7 release) $ borg version ssh://borg@borgbackup:repo 1.4.0a / 1.2.7 Due to the version tuple format used in Borg client/server negotiation, only a simplified version is displayed (as provided by ``borg.version.format_version``). There is also ``borg --version`` to display a potentially more precise client version.