Let prune delete old .partial uploads and remote info count them (closes #466) #474

Open
clawbot wants to merge 6 commits from issue-466-prune-partial-uploads into next
pull from: issue-466-prune-partial-uploads
Showing only changes of commit 332c2d30a2 - Show all commits
+13 -17
View File
@@ -340,23 +340,19 @@ In such a config, an unknown key or a value of the wrong type is refused.
error that explains how to fix it
- `--cron`: Silent on total success; warnings and errors are still printed (for
crontab)
- `--prune`: After backup, drop older snapshots of each backed-up name, remove
orphaned blobs older than `prune_grace_period` from remote storage, and delete
each directory under `metadata/` that has no `manifest.json.zst` once every
object in it is older than `prune_grace_period` and its snapshot is not in the
local index, and delete each `.partial` object older than
`prune_grace_period`, as `prune` does. By default keeps only the latest
snapshot per name; use `--keep-newer-than` for a rolling window. When
`--skip-errors` skipped a file or directory it could not read or list, the
prune does not run and every older snapshot is kept, since one of them may be
the only one that holds what was skipped; the command says so and exits
non-zero. When the backup found nothing in a configured path, as in the mount
point of a volume that is not mounted, the prune does not run either: every
older snapshot is kept, and the command names the path and exits non-zero, on
every run until the path holds something again. Take a path that is empty on
purpose out of the config, or remove the older snapshots by hand with
`snapshot purge`. When an earlier snapshot of the same name in the local index
found a volume mounted at or below a configured path (a directory on a
- `--prune`: After backup, drop older snapshots of each backed-up name, then
delete from the destination store what `prune` deletes there. By default keeps
only the latest snapshot per name; use `--keep-newer-than` for a rolling
window. When `--skip-errors` skipped a file or directory it could not read or
list, the prune does not run and every older snapshot is kept, since one of
them may be the only one that holds what was skipped; the command says so and
exits non-zero. When the backup found nothing in a configured path, as in the
mount point of a volume that is not mounted, the prune does not run either:
every older snapshot is kept, and the command names the path and exits
non-zero, on every run until the path holds something again. Take a path that
is empty on purpose out of the config, or remove the older snapshots by hand
with `snapshot purge`. When an earlier snapshot of the same name in the local
index found a volume mounted at or below a configured path (a directory on a
different filesystem from its parent, with an entry in it that the backup does
not exclude) and this backup does not, the prune does not run either: every
older snapshot is kept, and the command names the directory and exits