Skip to content

Commit

Permalink
Add note in docs about incompatibility of backup types
Browse files Browse the repository at this point in the history
Adds a note to both file-level and block-level incremental backup
sections to highlight that they're currently incompatible with each
other.

References: BAR-281

Signed-off-by: Gustavo William <gustavo.oliveira@enterprisedb.com>
  • Loading branch information
gustabowill committed Aug 22, 2024
1 parent 841335d commit 4575aa3
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions doc/manual/50-feature-details.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,10 @@ barman backup --reuse-backup=link <server_name>
> **IMPORTANT:** The `reuse_backup` option must be used along with
> `rsync` or `local-rsync` as backup method.
> **NOTE:** Incremental backups of different backup types are currently incompatible
> i.e. a file-level incremental backup can not be taken upon a streaming backup and
> vice-versa.

### Block-level incremental backups

Expand Down Expand Up @@ -118,6 +122,10 @@ To be able to perform a block-level incremental backup in Barman you must:
> it is adivised to take a new full-backup as divergent checkum configurations can potentially
> lead to issues during recovery.
> **NOTE:** Incremental backups of different backup types are currently incompatible
> i.e. a block-level incremental backup can not be taken upon an Rsync backup and
> vice-versa.
### Limiting bandwidth usage

It is possible to limit the usage of I/O bandwidth through the
Expand Down

0 comments on commit 4575aa3

Please sign in to comment.