From 94133cc8b1498bf4b699d6bc4b9c93341ef80f08 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Tue, 16 Apr 2024 10:57:34 -0700 Subject: [PATCH] Add note about running spot check on a separate schedule (#656). --- docs/how-to/deal-with-very-large-backups.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/how-to/deal-with-very-large-backups.md b/docs/how-to/deal-with-very-large-backups.md index 11a964f4..8850ef75 100644 --- a/docs/how-to/deal-with-very-large-backups.md +++ b/docs/how-to/deal-with-very-large-backups.md @@ -174,6 +174,11 @@ want the spot check to fail the next time it's run? Run `borgmatic create` to create a new backup, thereby allowing the next spot check to run against an archive that contains your recent changes. +Because the spot check only looks at the most recent archive, you may not want +to run it immediately after a `create` action (borgmatic's default behavior). +Instead, it may make more sense to run the spot check on a separate schedule +from `create`. + As long as the spot check feature is in beta, it may be subject to breaking changes. But feel free to use it in production if you're okay with that caveat, and please [provide any