check.rst.inc 15 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159
  1. .. IMPORTANT: this file is auto-generated from borg's built-in help, do not edit!
  2. .. _borg_check:
  3. borg check
  4. ----------
  5. .. code-block:: none
  6. borg [common options] check [options] [REPOSITORY_OR_ARCHIVE]
  7. .. only:: html
  8. .. class:: borg-options-table
  9. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  10. | **positional arguments** |
  11. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  12. | | ``REPOSITORY_OR_ARCHIVE`` | repository or archive to check consistency of |
  13. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  14. | **optional arguments** |
  15. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  16. | | ``--repository-only`` | only perform repository checks |
  17. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  18. | | ``--archives-only`` | only perform archives checks |
  19. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  20. | | ``--verify-data`` | perform cryptographic archive data integrity verification (conflicts with ``--repository-only``) |
  21. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  22. | | ``--repair`` | attempt to repair any inconsistencies found |
  23. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  24. | | ``--save-space`` | work slower, but using less space |
  25. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  26. | | ``--max-duration SECONDS`` | do only a partial repo check for max. SECONDS seconds (Default: unlimited) |
  27. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  28. | .. class:: borg-common-opt-ref |
  29. | |
  30. | :ref:`common_options` |
  31. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  32. | **Archive filters** — Archive filters can be applied to repository targets. |
  33. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  34. | | ``-P PREFIX``, ``--prefix PREFIX`` | only consider archive names starting with this prefix. |
  35. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  36. | | ``-a GLOB``, ``--glob-archives GLOB`` | only consider archive names matching the glob. sh: rules apply, see "borg help patterns". ``--prefix`` and ``--glob-archives`` are mutually exclusive. |
  37. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  38. | | ``--sort-by KEYS`` | Comma-separated list of sorting keys; valid keys are: timestamp, name, id; default is: timestamp |
  39. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  40. | | ``--first N`` | consider first N archives after other filters were applied |
  41. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  42. | | ``--last N`` | consider last N archives after other filters were applied |
  43. +-----------------------------------------------------------------------------+---------------------------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------+
  44. .. raw:: html
  45. <script type='text/javascript'>
  46. $(document).ready(function () {
  47. $('.borg-options-table colgroup').remove();
  48. })
  49. </script>
  50. .. only:: latex
  51. REPOSITORY_OR_ARCHIVE
  52. repository or archive to check consistency of
  53. optional arguments
  54. --repository-only only perform repository checks
  55. --archives-only only perform archives checks
  56. --verify-data perform cryptographic archive data integrity verification (conflicts with ``--repository-only``)
  57. --repair attempt to repair any inconsistencies found
  58. --save-space work slower, but using less space
  59. --max-duration SECONDS do only a partial repo check for max. SECONDS seconds (Default: unlimited)
  60. :ref:`common_options`
  61. |
  62. Archive filters
  63. -P PREFIX, --prefix PREFIX only consider archive names starting with this prefix.
  64. -a GLOB, --glob-archives GLOB only consider archive names matching the glob. sh: rules apply, see "borg help patterns". ``--prefix`` and ``--glob-archives`` are mutually exclusive.
  65. --sort-by KEYS Comma-separated list of sorting keys; valid keys are: timestamp, name, id; default is: timestamp
  66. --first N consider first N archives after other filters were applied
  67. --last N consider last N archives after other filters were applied
  68. Description
  69. ~~~~~~~~~~~
  70. The check command verifies the consistency of a repository and the corresponding archives.
  71. check --repair is a potentially dangerous function and might lead to data loss
  72. (for kinds of corruption it is not capable of dealing with). BE VERY CAREFUL!
  73. Pursuant to the previous warning it is also highly recommended to test the
  74. reliability of the hardware running this software with stress testing software
  75. such as memory testers. Unreliable hardware can also lead to data loss especially
  76. when this command is run in repair mode.
  77. First, the underlying repository data files are checked:
  78. - For all segments, the segment magic header is checked.
  79. - For all objects stored in the segments, all metadata (e.g. CRC and size) and
  80. all data is read. The read data is checked by size and CRC. Bit rot and other
  81. types of accidental damage can be detected this way.
  82. - In repair mode, if an integrity error is detected in a segment, try to recover
  83. as many objects from the segment as possible.
  84. - In repair mode, make sure that the index is consistent with the data stored in
  85. the segments.
  86. - If checking a remote repo via ``ssh:``, the repo check is executed on the server
  87. without causing significant network traffic.
  88. - The repository check can be skipped using the ``--archives-only`` option.
  89. - A repository check can be time consuming. Partial checks are possible with the
  90. ``--max-duration`` option.
  91. Second, the consistency and correctness of the archive metadata is verified:
  92. - Is the repo manifest present? If not, it is rebuilt from archive metadata
  93. chunks (this requires reading and decrypting of all metadata and data).
  94. - Check if archive metadata chunk is present; if not, remove archive from manifest.
  95. - For all files (items) in the archive, for all chunks referenced by these
  96. files, check if chunk is present. In repair mode, if a chunk is not present,
  97. replace it with a same-size replacement chunk of zeroes. If a previously lost
  98. chunk reappears (e.g. via a later backup), in repair mode the all-zero replacement
  99. chunk will be replaced by the correct chunk. This requires reading of archive and
  100. file metadata, but not data.
  101. - In repair mode, when all the archives were checked, orphaned chunks are deleted
  102. from the repo. One cause of orphaned chunks are input file related errors (like
  103. read errors) in the archive creation process.
  104. - In verify-data mode, a complete cryptographic verification of the archive data
  105. integrity is performed. This conflicts with ``--repository-only`` as this mode
  106. only makes sense if the archive checks are enabled. The full details of this mode
  107. are documented below.
  108. - If checking a remote repo via ``ssh:``, the archive check is executed on the
  109. client machine because it requires decryption, and this is always done client-side
  110. as key access is needed.
  111. - The archive checks can be time consuming; they can be skipped using the
  112. ``--repository-only`` option.
  113. The ``--max-duration`` option can be used to split a long-running repository check
  114. into multiple partial checks. After the given number of seconds the check is
  115. interrupted. The next partial check will continue where the previous one stopped,
  116. until the complete repository has been checked. Example: Assuming a complete check took 7
  117. hours, then running a daily check with --max-duration=3600 (1 hour) resulted in one
  118. completed check per week.
  119. Attention: A partial --repository-only check can only do way less checking than a full
  120. --repository-only check: only the non-cryptographic checksum checks on segment file
  121. entries are done, while a full --repository-only check would also do a repo index check.
  122. A partial check cannot be combined with the ``--repair`` option. Partial checks
  123. may therefore be useful only with very large repositories where a full check would take
  124. too long.
  125. Doing a full repository check aborts a partial check; the next partial check will restart
  126. from the beginning.
  127. The ``--verify-data`` option will perform a full integrity verification (as opposed to
  128. checking the CRC32 of the segment) of data, which means reading the data from the
  129. repository, decrypting and decompressing it. This is a cryptographic verification,
  130. which will detect (accidental) corruption. For encrypted repositories it is
  131. tamper-resistant as well, unless the attacker has access to the keys. It is also very
  132. slow.