mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

archive: say the check reads from the bucket with the s3 backend

Browse source
This commit is contained in:
atlas 2026-11-14 11:56:22 +01:00
commit c7580ac3dd
1 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

12
docs/2-handbook/swarm/archive.md
View file

@ -130,9 +130,15 @@ restore fails. Once a week (`deploy.archive.checkSchedule`, default `weekly`)
the archive host runs `restic check` on every repository. It checks the the archive host runs `restic check` on every repository. It checks the
repository's structure in full and reads a random `deploy.archive.checkSubset` repository's structure in full and reads a random `deploy.archive.checkSubset`
of its data (default `5%`), so repeated weekly runs cover a repository without of its data (default `5%`), so repeated weekly runs cover a repository without
any one run reading all of it. The check runs on the archive host because the any one run reading all of it. The check runs on the archive host because it
repositories are local there, so it reads no data over the network and needs no already holds every repository and the passwords, so it needs no credential
credential beyond the passwords the prune already reads. beyond the ones the prune reads.
With local storage the check reads the repositories from the host's disk.
With `deploy.archive.backend = "s3"` it reads each repository's structure and
its subset from the bucket through rclone every week, which costs bandwidth and
requests on your S3 service. `deploy.archive.checkSubset` is the lever: lower
it to read less.
The check and the prune share one lock and never run on a repository together; The check and the prune share one lock and never run on a repository together;
whichever starts second waits. A run that fails for an agent logs whichever starts second waits. A run that fails for an agent logs