borg-check.1 4.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148
  1. .\" Man page generated from reStructuredText.
  2. .
  3. .TH BORG-CHECK 1 "2017-06-18" "" "borg backup tool"
  4. .SH NAME
  5. borg-check \- Check repository consistency
  6. .
  7. .nr rst2man-indent-level 0
  8. .
  9. .de1 rstReportMargin
  10. \\$1 \\n[an-margin]
  11. level \\n[rst2man-indent-level]
  12. level margin: \\n[rst2man-indent\\n[rst2man-indent-level]]
  13. -
  14. \\n[rst2man-indent0]
  15. \\n[rst2man-indent1]
  16. \\n[rst2man-indent2]
  17. ..
  18. .de1 INDENT
  19. .\" .rstReportMargin pre:
  20. . RS \\$1
  21. . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin]
  22. . nr rst2man-indent-level +1
  23. .\" .rstReportMargin post:
  24. ..
  25. .de UNINDENT
  26. . RE
  27. .\" indent \\n[an-margin]
  28. .\" old: \\n[rst2man-indent\\n[rst2man-indent-level]]
  29. .nr rst2man-indent-level -1
  30. .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]]
  31. .in \\n[rst2man-indent\\n[rst2man-indent-level]]u
  32. ..
  33. .SH SYNOPSIS
  34. .sp
  35. borg [common options] check <options> REPOSITORY_OR_ARCHIVE
  36. .SH DESCRIPTION
  37. .sp
  38. The check command verifies the consistency of a repository and the corresponding archives.
  39. .sp
  40. First, the underlying repository data files are checked:
  41. .INDENT 0.0
  42. .IP \(bu 2
  43. For all segments the segment magic (header) is checked
  44. .IP \(bu 2
  45. For all objects stored in the segments, all metadata (e.g. crc and size) and
  46. all data is read. The read data is checked by size and CRC. Bit rot and other
  47. types of accidental damage can be detected this way.
  48. .IP \(bu 2
  49. If we are in repair mode and a integrity error is detected for a segment,
  50. we try to recover as many objects from the segment as possible.
  51. .IP \(bu 2
  52. In repair mode, it makes sure that the index is consistent with the data
  53. stored in the segments.
  54. .IP \(bu 2
  55. If you use a remote repo server via ssh:, the repo check is executed on the
  56. repo server without causing significant network traffic.
  57. .IP \(bu 2
  58. The repository check can be skipped using the \fB\-\-archives\-only\fP option.
  59. .UNINDENT
  60. .sp
  61. Second, the consistency and correctness of the archive metadata is verified:
  62. .INDENT 0.0
  63. .IP \(bu 2
  64. Is the repo manifest present? If not, it is rebuilt from archive metadata
  65. chunks (this requires reading and decrypting of all metadata and data).
  66. .IP \(bu 2
  67. Check if archive metadata chunk is present. if not, remove archive from
  68. manifest.
  69. .IP \(bu 2
  70. For all files (items) in the archive, for all chunks referenced by these
  71. files, check if chunk is present.
  72. If a chunk is not present and we are in repair mode, replace it with a same\-size
  73. replacement chunk of zeros.
  74. If a previously lost chunk reappears (e.g. via a later backup) and we are in
  75. repair mode, the all\-zero replacement chunk will be replaced by the correct chunk.
  76. This requires reading of archive and file metadata, but not data.
  77. .IP \(bu 2
  78. If we are in repair mode and we checked all the archives: delete orphaned
  79. chunks from the repo.
  80. .IP \(bu 2
  81. if you use a remote repo server via ssh:, the archive check is executed on
  82. the client machine (because if encryption is enabled, the checks will require
  83. decryption and this is always done client\-side, because key access will be
  84. required).
  85. .IP \(bu 2
  86. The archive checks can be time consuming, they can be skipped using the
  87. \fB\-\-repository\-only\fP option.
  88. .UNINDENT
  89. .sp
  90. The \fB\-\-verify\-data\fP option will perform a full integrity verification (as opposed to
  91. checking the CRC32 of the segment) of data, which means reading the data from the
  92. repository, decrypting and decompressing it. This is a cryptographic verification,
  93. which will detect (accidental) corruption. For encrypted repositories it is
  94. tamper\-resistant as well, unless the attacker has access to the keys.
  95. .sp
  96. It is also very slow.
  97. .SH OPTIONS
  98. .sp
  99. See \fIborg\-common(1)\fP for common options of Borg commands.
  100. .SS arguments
  101. .INDENT 0.0
  102. .TP
  103. .B REPOSITORY_OR_ARCHIVE
  104. repository or archive to check consistency of
  105. .UNINDENT
  106. .SS optional arguments
  107. .INDENT 0.0
  108. .TP
  109. .B \-\-repository\-only
  110. only perform repository checks
  111. .TP
  112. .B \-\-archives\-only
  113. only perform archives checks
  114. .TP
  115. .B \-\-verify\-data
  116. perform cryptographic archive data integrity verification (conflicts with \fB\-\-repository\-only\fP)
  117. .TP
  118. .B \-\-repair
  119. attempt to repair any inconsistencies found
  120. .TP
  121. .B \-\-save\-space
  122. work slower, but using less space
  123. .UNINDENT
  124. .SS filters
  125. .INDENT 0.0
  126. .TP
  127. .B \-P\fP,\fB \-\-prefix
  128. only consider archive names starting with this prefix.
  129. .TP
  130. .B \-a\fP,\fB \-\-glob\-archives
  131. only consider archive names matching the glob. sh: rules apply, see "borg help patterns". \fB\-\-prefix\fP and \fB\-\-glob\-archives\fP are mutually exclusive.
  132. .TP
  133. .B \-\-sort\-by
  134. Comma\-separated list of sorting keys; valid keys are: timestamp, name, id; default is: timestamp
  135. .TP
  136. .BI \-\-first \ N
  137. consider first N archives after other filters were applied
  138. .TP
  139. .BI \-\-last \ N
  140. consider last N archives after other filters were applied
  141. .UNINDENT
  142. .SH SEE ALSO
  143. .sp
  144. \fIborg\-common(1)\fP
  145. .SH AUTHOR
  146. The Borg Collective
  147. .\" Generated by docutils manpage writer.
  148. .