Skip to content

Commit

Permalink
Merge branch 'master' of github.com:Altinity/clickhouse-backup
Browse files Browse the repository at this point in the history
  • Loading branch information
Slach committed Apr 23, 2024
2 parents b1ee434 + db8625f commit 31e5df0
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Examples.md
Original file line number Diff line number Diff line change
Expand Up @@ -633,7 +633,7 @@ spec:

## How incremental backups work with remote storage
- Incremental backup calculates the increment only while executing `upload` or `create_remote` commands or similar REST API requests.
- When `use_embedded_backup_restore: false`, then incremental backup calculates the increment only on the table parts level; otherwise the increment is also calculated based on `checksums.txt`. For ClickHouse version 23.3+, see the ClickHouse documentation to find the difference between [data parts](https://clickhouse.tech/docs/en/operations/system-tables/parts/) and [table partitions](https://clickhouse.tech/docs/en/operations/system-tables/partitions/). Currently `clickhouse-baskup` does not support incremental backups when `use_embedded_backup_restore: true`.
- When `use_embedded_backup_restore: false`, then incremental backup calculates the increment only on the table parts level; otherwise the increment is also calculated based on `checksums.txt`. For ClickHouse version 23.3+, see the ClickHouse documentation to find the difference between [data parts](https://clickhouse.tech/docs/en/operations/system-tables/parts/) and [table partitions](https://clickhouse.tech/docs/en/operations/system-tables/partitions/). Currently `clickhouse-backup` does not support incremental backups when `use_embedded_backup_restore: true`.
- To calculate the increment, the backup listed on the `--diff-from` parameter is required to be present as a local backup. Check the `clickhouse-backup list` command results for errors.
- During upload, `base_backup` is added to current backup metadata as required. All data parts that exist in `base_backup` also mark in the backup metadata table level with `required` flag and skip data uploading.
- During download, if a backup contains link to a `required` backup, each table which contains parts marked as `required` will download these parts to local storage after complete downloading for non `required` parts. If you have a chain of incremental backups and required parts exist in this chain, then this action applies recursively.
Expand Down

0 comments on commit 31e5df0

Please sign in to comment.