diff --git a/README.md b/README.md index 846652f..c44e0b8 100644 --- a/README.md +++ b/README.md @@ -361,24 +361,25 @@ In such a config, an unknown key or a value of the wrong type is refused. local index, 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 `3`. 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 `1`, on every run until the path holds + and every older snapshot is kept. One of them may be the only one that holds + what was skipped. The command says so and exits `3`. The prune does not run + either when the backup found nothing in a configured path, as in the mount + point of a volume that is not mounted. Every older snapshot is kept, and the + command names the path and exits `1`, 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 non-zero, on every run until the volume - is mounted again. A backup also does not find the volume when it finds no such - entry in its directory, as when an automounted volume cannot be mounted, or - when that directory is no longer backed up, because it is excluded or its - configured path was removed. If any of this is on purpose, as for a retired - volume, remove the older snapshots by hand with `snapshot purge`. A file - removed during the backup does not stop the prune. + remove the older snapshots by hand with `snapshot purge`. The prune does not + run either when this backup does not find a volume that an earlier snapshot of + the same name in the local index found. The volume's mount point is a + directory at or below a configured path. That directory is on a different + filesystem from its parent and holds an entry the backup does not exclude. + Every older snapshot is kept, and the command names the directory and exits + `1`, on every run until the volume is mounted again. A backup also does not + find the volume when it finds no such entry in its directory, as when an + automounted volume cannot be mounted. Nor does it find the volume when that + directory is no longer backed up, because it is excluded or its configured + path was removed. If any of this is on purpose, as for a retired volume, + remove the older snapshots by hand with `snapshot purge`. A file removed + during the backup does not stop the prune. - `--keep-newer-than `: With `--prune`, keep snapshots newer than this duration instead of only the latest (e.g. `4w`, `30d`, `6mo`, `1y`). Without `--prune`, or with a value that is not a valid duration, the command fails