Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add doc about keep restriction on incremental backups #986

Merged
merged 1 commit into from
Aug 19, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions doc/manual/43-backup-commands.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,21 @@ the server then you can make it an archival backup with:
barman keep <server_name> <backup_id> [--target TARGET, --status, --release]
```

> **NOTE:**
andremagui marked this conversation as resolved.
Show resolved Hide resolved
> To ensure the integrity of your backup system, incremental backups
> cannot use the keep annotation in Barman. This restriction is due to
> the way incremental backups depend on each other. Using the keep
> annotation with incremental backups could result in orphaned backups,
> which means that certain backups might exist without their necessary
> parent backups.
>
> In simpler terms, if you were allowed to apply the keep annotation to
> an incremental backup, there would be a risk that parts of the backup
> chain would be retained without their required predecessors. This
> situation could create backups that would be no longer useful or
> complete, as they would be missing the essential parent backups needed
> to restore them properly.

Possible values for `TARGET` are:

* `full`: The backup can always be used to recover to the latest point in
Expand Down
Loading