mirror of https://github.com/borgbackup/borg.git
resolve clarify borg check --verify-data (#5808)
This commit is contained in:
parent
64bbe399df
commit
4f9e30e980
|
@ -125,6 +125,10 @@ Second, the consistency and correctness of the archive metadata is verified:
|
||||||
- In repair mode, when all the archives were checked, orphaned chunks are deleted
|
- 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
|
from the repo. One cause of orphaned chunks are input file related errors (like
|
||||||
read errors) in the archive creation process.
|
read errors) in the archive creation process.
|
||||||
|
- In verify-data mode, a complete cryptographic verification of the archive data
|
||||||
|
integrity is performed. This conflicts with ``--repository-only`` as this mode
|
||||||
|
only makes sense if the archive checks are enabled. The full details of this mode
|
||||||
|
are documented below.
|
||||||
- If checking a remote repo via ``ssh:``, the archive check is executed on the
|
- If checking a remote repo via ``ssh:``, the archive check is executed on the
|
||||||
client machine because it requires decryption, and this is always done client-side
|
client machine because it requires decryption, and this is always done client-side
|
||||||
as key access is needed.
|
as key access is needed.
|
||||||
|
|
|
@ -3072,6 +3072,10 @@ class Archiver:
|
||||||
- In repair mode, when all the archives were checked, orphaned chunks are deleted
|
- 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
|
from the repo. One cause of orphaned chunks are input file related errors (like
|
||||||
read errors) in the archive creation process.
|
read errors) in the archive creation process.
|
||||||
|
- In verify-data mode, a complete cryptographic verification of the archive data
|
||||||
|
integrity is performed. This conflicts with ``--repository-only`` as this mode
|
||||||
|
only makes sense if the archive checks are enabled. The full details of this mode
|
||||||
|
are documented below.
|
||||||
- If checking a remote repo via ``ssh:``, the archive check is executed on the
|
- If checking a remote repo via ``ssh:``, the archive check is executed on the
|
||||||
client machine because it requires decryption, and this is always done client-side
|
client machine because it requires decryption, and this is always done client-side
|
||||||
as key access is needed.
|
as key access is needed.
|
||||||
|
|
Loading…
Reference in New Issue