From 1ef82a27fa18d71820aafe2cf3075fd5bd2dc204 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Mon, 12 Dec 2022 16:03:05 -0800 Subject: [PATCH] Clarify data/archives check implicit enabling. --- docs/how-to/deal-with-very-large-backups.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/how-to/deal-with-very-large-backups.md b/docs/how-to/deal-with-very-large-backups.md index d7c81ec83..c880c83e8 100644 --- a/docs/how-to/deal-with-very-large-backups.md +++ b/docs/how-to/deal-with-very-large-backups.md @@ -67,7 +67,10 @@ Here are the available checks from fastest to slowest: * `repository`: Checks the consistency of the repository itself. * `archives`: Checks all of the archives in the repository. * `extract`: Performs an extraction dry-run of the most recent archive. - * `data`: Verifies the data integrity of all archives contents, decrypting and decompressing all data (implies `archives` as well). + * `data`: Verifies the data integrity of all archives contents, decrypting and decompressing all data. + +Note that the `data` check is a more thorough version of the `archives` check, +so enabling the `data` check implicitly enables the `archives` check as well. See [Borg's check documentation](https://borgbackup.readthedocs.io/en/stable/usage/check.html)