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

feat: ClickHouse auto backup before powering off a service #640

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
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
4 changes: 2 additions & 2 deletions docs/products/clickhouse/concepts/disaster-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,9 +31,9 @@ Also see [cross-availability-zone data distribution](/docs/platform/concepts/ava
### Service backup

Backups of Aiven for ClickHouse services happen automatically on a daily
basis.
basis. An automatic backup is also taken before powering off a service.
wojcik-dorota marked this conversation as resolved.
Show resolved Hide resolved

They cover the following:
Backups cover the following:

- Access entities (for example, users, roles, passwords, or secrets)
stored in Zookeeper
Expand Down
9 changes: 5 additions & 4 deletions docs/products/clickhouse/reference/limitations.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,11 +28,12 @@ a
<td>
Since Aiven for ClickHouse service takes a single snapshot a day only:
<ul>
<li>When powering off the service, all data after the last backup is lost.</li>
<li>Point-in-time recovery is not supported. A database can be restored to
one of the daily backups states only.</li>
<li>Point-in-time recovery is not supported. A database can be
[restored to one of the daily backups states](/docs/products/clickhouse/howto/restore-backup)
only.</li>
<li>When creating a database fork,
you can only create a fork that matches the state of one of the backups.</li>
you can only [create a fork](/docs/products/clickhouse/howto/restore-backup)
that matches the state of one of the backups.</li>
<li>Any data inserted before the next snapshot is lost if all nodes in a
given shard malfunction and need to be replaced. This limitation doesn't
apply to patches, migrations, or scaling, which are handled safely and
Expand Down
Loading