diff options
Diffstat (limited to 'docs/man')
40 files changed, 193 insertions, 129 deletions
diff --git a/docs/man/borg-benchmark-cpu.1 b/docs/man/borg-benchmark-cpu.1 index 6a221e43b..52eea6a24 100644 --- a/docs/man/borg-benchmark-cpu.1 +++ b/docs/man/borg-benchmark-cpu.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-BENCHMARK-CPU" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-BENCHMARK-CPU" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-benchmark-cpu \- Benchmark CPU bound operations. .SH SYNOPSIS diff --git a/docs/man/borg-benchmark-crud.1 b/docs/man/borg-benchmark-crud.1 index f62c0b6a4..4def48ef0 100644 --- a/docs/man/borg-benchmark-crud.1 +++ b/docs/man/borg-benchmark-crud.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-BENCHMARK-CRUD" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-BENCHMARK-CRUD" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-benchmark-crud \- Benchmark Create, Read, Update, Delete for archives. .SH SYNOPSIS diff --git a/docs/man/borg-benchmark.1 b/docs/man/borg-benchmark.1 index 14092a348..27314f65f 100644 --- a/docs/man/borg-benchmark.1 +++ b/docs/man/borg-benchmark.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-BENCHMARK" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-BENCHMARK" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-benchmark \- benchmark command .SH SYNOPSIS diff --git a/docs/man/borg-break-lock.1 b/docs/man/borg-break-lock.1 index a48c4f993..a5621c3b7 100644 --- a/docs/man/borg-break-lock.1 +++ b/docs/man/borg-break-lock.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-BREAK-LOCK" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-BREAK-LOCK" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-break-lock \- Break the repository lock (e.g. in case it was left by a dead borg. .SH SYNOPSIS diff --git a/docs/man/borg-check.1 b/docs/man/borg-check.1 index 80c0f0a73..a4dc3822a 100644 --- a/docs/man/borg-check.1 +++ b/docs/man/borg-check.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-CHECK" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-CHECK" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-check \- Check repository consistency .SH SYNOPSIS @@ -35,94 +35,123 @@ borg-check \- Check repository consistency borg [common options] check [options] .SH DESCRIPTION .sp -The check command verifies the consistency of a repository and the corresponding archives. +The check command verifies the consistency of a repository and its archives. +It consists of two major steps: +.INDENT 0.0 +.IP 1. 3 +Checking the consistency of the repository itself. This includes checking +the segment magic headers, and both the metadata and data of all objects in +the segments. The read data is checked by size and CRC. Bit rot and other +types of accidental damage can be detected this way. Running the repository +check can be split into multiple partial checks using \fB\-\-max\-duration\fP\&. +When checking a remote repository, please note that the checks run on the +server and do not cause significant network traffic. +.IP 2. 3 +Checking consistency and correctness of the archive metadata and optionally +archive data (requires \fB\-\-verify\-data\fP). This includes ensuring that the +repository manifest exists, the archive metadata chunk is present, and that +all chunks referencing files (items) in the archive exist. This requires +reading archive and file metadata, but not data. To cryptographically verify +the file (content) data integrity pass \fB\-\-verify\-data\fP, but keep in mind +that this requires reading all data and is hence very time consuming. When +checking archives of a remote repository, archive checks run on the client +machine because they require decrypting data and therefore the encryption +key. +.UNINDENT .sp -check \-\-repair is a potentially dangerous function and might lead to data loss -(for kinds of corruption it is not capable of dealing with). BE VERY CAREFUL! +Both steps can also be run independently. Pass \fB\-\-repository\-only\fP to run the +repository checks only, or pass \fB\-\-archives\-only\fP to run the archive checks +only. .sp -Pursuant to the previous warning it is also highly recommended to test the -reliability of the hardware running this software with stress testing software -such as memory testers. Unreliable hardware can also lead to data loss especially -when this command is run in repair mode. +The \fB\-\-max\-duration\fP option can be used to split a long\-running repository +check into multiple partial checks. After the given number of seconds the check +is interrupted. The next partial check will continue where the previous one +stopped, until the full repository has been checked. Assuming a complete check +would take 7 hours, then running a daily check with \fB\-\-max\-duration=3600\fP +(1 hour) would result in one full repository check per week. Doing a full +repository check aborts any previous partial check; the next partial check will +restart from the beginning. With partial repository checks you can run neither +archive checks, nor enable repair mode. Consequently, if you want to use +\fB\-\-max\-duration\fP you must also pass \fB\-\-repository\-only\fP, and must not pass +\fB\-\-archives\-only\fP, nor \fB\-\-repair\fP\&. +.sp +\fBWarning:\fP Please note that partial repository checks (i.e. running it with +\fB\-\-max\-duration\fP) can only perform non\-cryptographic checksum checks on the +segment files. A full repository check (i.e. without \fB\-\-max\-duration\fP) can +also do a repository index check. Enabling partial repository checks excepts +archive checks for the same reason. Therefore partial checks may be useful with +very large repositories only where a full check would take too long. +.sp +The \fB\-\-verify\-data\fP option will perform a full integrity verification (as +opposed to checking the CRC32 of the segment) of data, which means reading the +data from the repository, decrypting and decompressing it. It is a complete +cryptographic verification and hence very time consuming, but will detect any +accidental and malicious corruption. Tamper\-resistance is only guaranteed for +encrypted repositories against attackers without access to the keys. You can +not use \fB\-\-verify\-data\fP with \fB\-\-repository\-only\fP\&. +.SS About repair mode +.sp +The check command is a readonly task by default. If any corruption is found, +Borg will report the issue and proceed with checking. To actually repair the +issues found, pass \fB\-\-repair\fP\&. .sp -First, the underlying repository data files are checked: +\fBNOTE:\fP .INDENT 0.0 -.IP \(bu 2 -For all segments, the segment magic header is checked. -.IP \(bu 2 -For all objects stored in the segments, all metadata (e.g. CRC and size) and -all data is read. The read data is checked by size and CRC. Bit rot and other -types of accidental damage can be detected this way. -.IP \(bu 2 -In repair mode, if an integrity error is detected in a segment, try to recover -as many objects from the segment as possible. -.IP \(bu 2 -In repair mode, make sure that the index is consistent with the data stored in -the segments. -.IP \(bu 2 -If checking a remote repo via \fBssh:\fP, the repo check is executed on the server -without causing significant network traffic. -.IP \(bu 2 -The repository check can be skipped using the \fB\-\-archives\-only\fP option. -.IP \(bu 2 -A repository check can be time consuming. Partial checks are possible with the -\fB\-\-max\-duration\fP option. +.INDENT 3.5 +\fB\-\-repair\fP is a \fBPOTENTIALLY DANGEROUS FEATURE\fP and might lead to data +loss! This does not just include data that was previously lost anyway, but +might include more data for kinds of corruption it is not capable of +dealing with. \fBBE VERY CAREFUL!\fP .UNINDENT +.UNINDENT +.sp +Pursuant to the previous warning it is also highly recommended to test the +reliability of the hardware running Borg with stress testing software. This +especially includes storage and memory testers. Unreliable hardware might lead +to additional data loss. .sp -Second, the consistency and correctness of the archive metadata is verified: +It is highly recommended to create a backup of your repository before running +in repair mode (i.e. running it with \fB\-\-repair\fP). +.sp +Repair mode will attempt to fix any corruptions found. Fixing corruptions does +not mean recovering lost data: Borg can not magically restore data lost due to +e.g. a hardware failure. Repairing a repository means sacrificing some data +for the sake of the repository as a whole and the remaining data. Hence it is, +by definition, a potentially lossy task. +.sp +In practice, repair mode hooks into both the repository and archive checks: .INDENT 0.0 -.IP \(bu 2 -Is the repo manifest present? If not, it is rebuilt from archive metadata -chunks (this requires reading and decrypting of all metadata and data). -.IP \(bu 2 -Check if archive metadata chunk is present; if not, remove archive from manifest. -.IP \(bu 2 -For all files (items) in the archive, for all chunks referenced by these -files, check if chunk is present. In repair mode, if a chunk is not present, -replace it with a same\-size replacement chunk of zeroes. If a previously lost -chunk reappears (e.g. via a later backup), in repair mode the all\-zero replacement -chunk will be replaced by the correct chunk. This requires reading of archive and -file metadata, but not data. -.IP \(bu 2 -In repair mode, when all the archives were checked, orphaned chunks are deleted -from the repo. One cause of orphaned chunks are input file related errors (like -read errors) in the archive creation process. -.IP \(bu 2 -In verify\-data mode, a complete cryptographic verification of the archive data -integrity is performed. This conflicts with \fB\-\-repository\-only\fP as this mode -only makes sense if the archive checks are enabled. The full details of this mode -are documented below. -.IP \(bu 2 -If checking a remote repo via \fBssh:\fP, the archive check is executed on the -client machine because it requires decryption, and this is always done client\-side -as key access is needed. -.IP \(bu 2 -The archive checks can be time consuming; they can be skipped using the -\fB\-\-repository\-only\fP option. +.IP 1. 3 +When checking the repository\(aqs consistency, repair mode will try to recover +as many objects from segments with integrity errors as possible, and ensure +that the index is consistent with the data stored in the segments. +.IP 2. 3 +When checking the consistency and correctness of archives, repair mode might +remove whole archives from the manifest if their archive metadata chunk is +corrupt or lost. On a chunk level (i.e. the contents of files), repair mode +will replace corrupt or lost chunks with a same\-size replacement chunk of +zeroes. If a previously zeroed chunk reappears, repair mode will restore +this lost chunk using the new chunk. Lastly, repair mode will also delete +orphaned chunks (e.g. caused by read errors while creating the archive). .UNINDENT .sp -The \fB\-\-max\-duration\fP option can be used to split a long\-running repository check -into multiple partial checks. After the given number of seconds the check is -interrupted. The next partial check will continue where the previous one stopped, -until the complete repository has been checked. Example: Assuming a complete check took 7 -hours, then running a daily check with \-\-max\-duration=3600 (1 hour) resulted in one -completed check per week. -.sp -Attention: A partial \-\-repository\-only check can only do way less checking than a full -\-\-repository\-only check: only the non\-cryptographic checksum checks on segment file -entries are done, while a full \-\-repository\-only check would also do a repo index check. -A partial check cannot be combined with the \fB\-\-repair\fP option. Partial checks -may therefore be useful only with very large repositories where a full check would take -too long. -Doing a full repository check aborts a partial check; the next partial check will restart -from the beginning. -.sp -The \fB\-\-verify\-data\fP option will perform a full integrity verification (as opposed to -checking the CRC32 of the segment) of data, which means reading the data from the -repository, decrypting and decompressing it. This is a cryptographic verification, -which will detect (accidental) corruption. For encrypted repositories it is -tamper\-resistant as well, unless the attacker has access to the keys. It is also very -slow. +Most steps taken by repair mode have a one\-time effect on the repository, like +removing a lost archive from the repository. However, replacing a corrupt or +lost chunk with an all\-zero replacement will have an ongoing effect on the +repository: When attempting to extract a file referencing an all\-zero chunk, +the \fBextract\fP command will distinctly warn about it. The FUSE filesystem +created by the \fBmount\fP command will reject reading such a \(dqzero\-patched\(dq +file unless a special mount option is given. +.sp +As mentioned earlier, Borg might be able to \(dqheal\(dq a \(dqzero\-patched\(dq file in +repair mode, if all its previously lost chunks reappear (e.g. via a later +backup). This is achieved by Borg not only keeping track of the all\-zero +replacement chunks, but also by keeping metadata about the lost chunks. In +repair mode Borg will check whether a previously lost chunk reappeared and will +replace the all\-zero replacement chunk by the reappeared chunk. If all lost +chunks of a \(dqzero\-patched\(dq file reappear, this effectively \(dqheals\(dq the file. +Consequently, if lost chunks were repaired earlier, it is advised to run +\fB\-\-repair\fP a second time after creating some new backups. .SH OPTIONS .sp See \fIborg\-common(1)\fP for common options of Borg commands. diff --git a/docs/man/borg-common.1 b/docs/man/borg-common.1 index cc65bce9e..dc37457fb 100644 --- a/docs/man/borg-common.1 +++ b/docs/man/borg-common.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-COMMON" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-COMMON" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-common \- Common options of Borg commands .SH SYNOPSIS diff --git a/docs/man/borg-compact.1 b/docs/man/borg-compact.1 index 595030b34..1aa765eac 100644 --- a/docs/man/borg-compact.1 +++ b/docs/man/borg-compact.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-COMPACT" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-COMPACT" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-compact \- compact segment files in the repository .SH SYNOPSIS diff --git a/docs/man/borg-compression.1 b/docs/man/borg-compression.1 index e4adfdca3..bc65a9886 100644 --- a/docs/man/borg-compression.1 +++ b/docs/man/borg-compression.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-COMPRESSION" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-COMPRESSION" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-compression \- Details regarding compression .SH DESCRIPTION @@ -56,7 +56,6 @@ Use lz4 compression. Very high speed, very low compression. (default) Use zstd (\(dqzstandard\(dq) compression, a modern wide\-range algorithm. If you do not explicitly give the compression level L (ranging from 1 to 22), it will use level 3. -Archives compressed with zstd are not compatible with borg < 1.1.4. .TP .B zlib[,L] Use zlib (\(dqgz\(dq) compression. Medium speed, medium compression. diff --git a/docs/man/borg-config.1 b/docs/man/borg-config.1 index a521084c7..5abc675d6 100644 --- a/docs/man/borg-config.1 +++ b/docs/man/borg-config.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-CONFIG" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-CONFIG" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-config \- get, set, and delete values in a repository or cache config file .SH SYNOPSIS diff --git a/docs/man/borg-create.1 b/docs/man/borg-create.1 index 669a4cf47..d0f497569 100644 --- a/docs/man/borg-create.1 +++ b/docs/man/borg-create.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-CREATE" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-CREATE" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-create \- Create new archive .SH SYNOPSIS @@ -299,8 +299,7 @@ $ cd .. $ fusermount \-u sshfs\-mount # Make a big effort in fine granular deduplication (big chunk management -# overhead, needs a lot of RAM and disk space, see formula in internals -# docs \- same parameters as borg < 1.0): +# overhead, needs a lot of RAM and disk space, see formula in internals docs): $ borg create \-\-chunker\-params buzhash,10,23,16,4095 small /smallstuff # Backup a raw device (must not be active/in use/mounted at that time) diff --git a/docs/man/borg-delete.1 b/docs/man/borg-delete.1 index 5537168cb..11bfe4bb0 100644 --- a/docs/man/borg-delete.1 +++ b/docs/man/borg-delete.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-DELETE" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-DELETE" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-delete \- Delete archives .SH SYNOPSIS @@ -110,7 +110,7 @@ consider archives newer than (now \- TIMESPAN), e.g. 7d or 12m. .nf .ft C # delete a single backup archive: -$ borg delete Monday +$ borg delete \-a Monday # actually free disk space: $ borg compact diff --git a/docs/man/borg-diff.1 b/docs/man/borg-diff.1 index 8c73f281d..0f84b9966 100644 --- a/docs/man/borg-diff.1 +++ b/docs/man/borg-diff.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-DIFF" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-DIFF" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-diff \- Diff contents of two archives .SH SYNOPSIS diff --git a/docs/man/borg-export-tar.1 b/docs/man/borg-export-tar.1 index 792c812e0..a82f16207 100644 --- a/docs/man/borg-export-tar.1 +++ b/docs/man/borg-export-tar.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-EXPORT-TAR" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-EXPORT-TAR" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-export-tar \- Export archive contents as a tarball .SH SYNOPSIS diff --git a/docs/man/borg-extract.1 b/docs/man/borg-extract.1 index d5d734aa9..89989def5 100644 --- a/docs/man/borg-extract.1 +++ b/docs/man/borg-extract.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-EXTRACT" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-EXTRACT" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-extract \- Extract archive contents .SH SYNOPSIS diff --git a/docs/man/borg-import-tar.1 b/docs/man/borg-import-tar.1 index 7714750cc..d84c53a9b 100644 --- a/docs/man/borg-import-tar.1 +++ b/docs/man/borg-import-tar.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-IMPORT-TAR" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-IMPORT-TAR" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-import-tar \- Create a backup archive from a tarball .SH SYNOPSIS diff --git a/docs/man/borg-info.1 b/docs/man/borg-info.1 index 86940f570..4962ddd2d 100644 --- a/docs/man/borg-info.1 +++ b/docs/man/borg-info.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-INFO" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-INFO" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-info \- Show archive details such as disk space used .SH SYNOPSIS diff --git a/docs/man/borg-key-change-location.1 b/docs/man/borg-key-change-location.1 index ead426667..292200f3a 100644 --- a/docs/man/borg-key-change-location.1 +++ b/docs/man/borg-key-change-location.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-KEY-CHANGE-LOCATION" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-KEY-CHANGE-LOCATION" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-key-change-location \- Change repository key location .SH SYNOPSIS diff --git a/docs/man/borg-key-change-passphrase.1 b/docs/man/borg-key-change-passphrase.1 index 74ebf60dd..7f2468615 100644 --- a/docs/man/borg-key-change-passphrase.1 +++ b/docs/man/borg-key-change-passphrase.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-KEY-CHANGE-PASSPHRASE" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-KEY-CHANGE-PASSPHRASE" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-key-change-passphrase \- Change repository key file passphrase .SH SYNOPSIS diff --git a/docs/man/borg-key-export.1 b/docs/man/borg-key-export.1 index 1ed16caab..c4916175b 100644 --- a/docs/man/borg-key-export.1 +++ b/docs/man/borg-key-export.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-KEY-EXPORT" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-KEY-EXPORT" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-key-export \- Export the repository key for backup .SH SYNOPSIS diff --git a/docs/man/borg-key-import.1 b/docs/man/borg-key-import.1 index 97c8c8130..7aca05fc5 100644 --- a/docs/man/borg-key-import.1 +++ b/docs/man/borg-key-import.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-KEY-IMPORT" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-KEY-IMPORT" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-key-import \- Import the repository key from backup .SH SYNOPSIS diff --git a/docs/man/borg-key.1 b/docs/man/borg-key.1 index bc984eefe..18287bee3 100644 --- a/docs/man/borg-key.1 +++ b/docs/man/borg-key.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-KEY" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-KEY" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-key \- Manage a keyfile or repokey of a repository .SH SYNOPSIS diff --git a/docs/man/borg-list.1 b/docs/man/borg-list.1 index b54c78a50..d6868c8ad 100644 --- a/docs/man/borg-list.1 +++ b/docs/man/borg-list.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-LIST" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-LIST" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-list \- List archive contents .SH SYNOPSIS @@ -106,11 +106,11 @@ drwxrwxr\-x user user 0 Sun, 2015\-02\-01 11:00:00 code/myproject \-rw\-rw\-r\-\- user user 1416192 Sun, 2015\-02\-01 11:00:00 code/myproject/file.text \&... -$ borg list archiveA \-\-pattern \(aqre:\e.ext$\(aq +$ borg list archiveA \-\-pattern \(aq+ re:\e.ext$\(aq \-\-pattern \(aq\- re:^.*$\(aq \-rw\-rw\-r\-\- user user 1416192 Sun, 2015\-02\-01 11:00:00 code/myproject/file.ext \&... -$ borg list archiveA \-\-pattern \(aqre:.ext$\(aq +$ borg list archiveA \-\-pattern \(aq+ re:.ext$\(aq \-\-pattern \(aq\- re:^.*$\(aq \-rw\-rw\-r\-\- user user 1416192 Sun, 2015\-02\-01 11:00:00 code/myproject/file.ext \-rw\-rw\-r\-\- user user 1416192 Sun, 2015\-02\-01 11:00:00 code/myproject/file.text \&... diff --git a/docs/man/borg-match-archives.1 b/docs/man/borg-match-archives.1 index 7e6344529..3dfb70b9d 100644 --- a/docs/man/borg-match-archives.1 +++ b/docs/man/borg-match-archives.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-MATCH-ARCHIVES" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-MATCH-ARCHIVES" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-match-archives \- Details regarding match-archives .SH DESCRIPTION diff --git a/docs/man/borg-mount.1 b/docs/man/borg-mount.1 index 828c4e5d7..9e06af762 100644 --- a/docs/man/borg-mount.1 +++ b/docs/man/borg-mount.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-MOUNT" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-MOUNT" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-mount \- Mount archive or an entire repository as a FUSE filesystem .SH SYNOPSIS diff --git a/docs/man/borg-patterns.1 b/docs/man/borg-patterns.1 index a4918695b..545bed825 100644 --- a/docs/man/borg-patterns.1 +++ b/docs/man/borg-patterns.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-PATTERNS" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-PATTERNS" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-patterns \- Details regarding patterns .SH DESCRIPTION diff --git a/docs/man/borg-placeholders.1 b/docs/man/borg-placeholders.1 index 8810acb99..175e27e7a 100644 --- a/docs/man/borg-placeholders.1 +++ b/docs/man/borg-placeholders.1 @@ -27,7 +27,7 @@ level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] .\" new: \\n[rst2man-indent\\n[rst2man-indent-level]] .in \\n[rst2man-indent\\n[rst2man-indent-level]]u .. -.TH "BORG-PLACEHOLDERS" 1 "2023-06-11" "" "borg backup tool" +.TH "BORG-PLACEHOLDERS" 1 "2023-09-14" "" "borg backup tool" .SH NAME borg-placeholders \- Details regarding placeholders .SH DESCRIPTION |