mirror/borg
1
0
Fork 0
mirror of https://github.com/borgbackup/borg.git synced 2025-03-09 13:53:09 +00:00
Code Issues Releases Wiki Activity
borg/docs/usage/info.rst.inc

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

85 lines
8.3 KiB
PHP
Raw Normal View History

update usage files
2016-07-05 23:30:08 +02:00
.. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 10:42:16 -05:00
.. _borg_info:
borg info
---------
docs: usage: avoid bash highlight, [options] instead of <options>
2017-06-07 00:44:53 +02:00
.. code-block:: none
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 10:42:16 -05:00
build_usage / build_man / doc updates
2022-06-24 01:19:19 +02:00
borg [common options] info [options]
Better help texts and Sphinx reproduction of usage - Group options - Nicer list of options in Sphinx - Deduplicate 'Common options' (including --help) The latter is done by explicitly declaring --help in the common_parser, which is then inherited by the sub-parsers; no change in observable behaviour.
2016-04-10 01:28:18 +02:00
ran build_usage
2017-06-20 15:22:24 +02:00
.. only:: html
.. class:: borg-options-table
build_usage
2024-02-20 17:11:43 +01:00
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
build_usage / build_man
2024-07-19 20:40:15 +02:00
| **optional arguments** |
build_usage
2024-02-20 17:11:43 +01:00
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--json`` | format output as JSON |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| .. class:: borg-common-opt-ref |
| |
| :ref:`common_options` |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| **Archive filters** — Archive filters can be applied to repository targets. |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``-a PATTERN``, ``--match-archives PATTERN`` | only consider archive names matching the pattern. see "borg help match-archives". |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--sort-by KEYS`` | Comma-separated list of sorting keys; valid keys are: timestamp, archive, name, id; default is: timestamp |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--first N`` | consider first N archives after other filters were applied |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--last N`` | consider last N archives after other filters were applied |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--oldest TIMESPAN`` | consider archives between the oldest archive's timestamp and (oldest + TIMESPAN), e.g. 7d or 12m. |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--newest TIMESPAN`` | consider archives between the newest archive's timestamp and (newest - TIMESPAN), e.g. 7d or 12m. |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--older TIMESPAN`` | consider archives older than (now - TIMESPAN), e.g. 7d or 12m. |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
| | ``--newer TIMESPAN`` | consider archives newer than (now - TIMESPAN), e.g. 7d or 12m. |
+-----------------------------------------------------------------------------+----------------------------------------------+-----------------------------------------------------------------------------------------------------------+
ran build_usage
2017-06-20 15:22:24 +02:00
.. raw:: html
<script type='text/javascript'>
docs: use DOM ready event, not document loaded event
2017-06-20 15:48:30 +02:00
$(document).ready(function () {
ran build_usage
2017-06-20 15:22:24 +02:00
$('.borg-options-table colgroup').remove();
})
</script>
.. only:: latex
build_usage / build_man
2024-07-19 20:40:15 +02:00
optional arguments
ran build_usage
2017-06-20 15:22:24 +02:00
--json format output as JSON
:ref:`common_options`
|
python setup.py build_usage
2017-07-23 17:12:01 +02:00
Archive filters
build_man / build_usage
2022-10-02 15:51:17 +02:00
-a PATTERN, --match-archives PATTERN only consider archive names matching the pattern. see "borg help match-archives".
build_usage
2024-02-20 17:11:43 +01:00
--sort-by KEYS Comma-separated list of sorting keys; valid keys are: timestamp, archive, name, id; default is: timestamp
build_man / build_usage
2022-10-02 15:51:17 +02:00
--first N consider first N archives after other filters were applied
--last N consider last N archives after other filters were applied
build_usage
2023-02-26 21:30:28 +01:00
--oldest TIMESPAN consider archives between the oldest archive's timestamp and (oldest + TIMESPAN), e.g. 7d or 12m.
--newest TIMESPAN consider archives between the newest archive's timestamp and (newest - TIMESPAN), e.g. 7d or 12m.
build_usage
2024-02-20 17:11:43 +01:00
--older TIMESPAN consider archives older than (now - TIMESPAN), e.g. 7d or 12m.
build_usage
2023-02-26 21:30:28 +01:00
--newer TIMESPAN consider archives newer than (now - TIMESPAN), e.g. 7d or 12m.
ran build_usage
2017-06-20 11:49:26 +02:00
ran build_usage
2016-10-01 18:23:36 +02:00
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384
2015-11-13 10:42:16 -05:00
Description
~~~~~~~~~~~
build_usage / build_man / doc updates
2022-06-24 01:19:19 +02:00
This command displays detailed information about the specified archive.
Merge branch '1.0-maint'
2016-07-06 01:33:53 +02:00
ran build_usage
2016-10-01 18:23:36 +02:00
Please note that the deduplicated sizes of the individual archives do not add
up to the deduplicated size of the repository ("all archives"), because the two
are meaning different things:
ran build_usage
2016-08-28 00:17:24 +02:00
ran build_usage
2016-10-01 18:23:36 +02:00
This archive / deduplicated size = amount of data stored ONLY for this archive
build_usage (master) also: add new borgfs.rst.inc
2017-11-25 14:35:52 +01:00
= unique chunks of this archive.
ran build_usage
2016-10-01 18:23:36 +02:00
All archives / deduplicated size = amount of data stored in the repo
build_usage build_man
2022-08-07 19:20:34 +02:00
= all chunks in the repository.
Reference in a new issue Copy permalink