Skip to content

Commit 781759c

Browse files
committed
Fixes for CI
1 parent 72c6ed5 commit 781759c

File tree

10 files changed

+44
-68
lines changed

10 files changed

+44
-68
lines changed

docs/cloud/features/08_backups.md

Lines changed: 40 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,7 @@ ClickHouse Cloud allows you to configure the schedule for your backups for **Sca
4747

4848
:::note
4949
The custom schedule will override the default backup policy in ClickHouse Cloud for your given service.
50-
:::
5150

52-
:::note
5351
In some rare scenarios, the backup scheduler will not respect the **Start Time** specified for backups. Specifically, this happens if there was a successful backup triggered < 24 hours from the time of the currently scheduled backup. This could happen due to a retry mechanism we have in place for backups. In such instances, the scheduler will skip over the backup for the current day, and will retry the backup the next day at the scheduled time.
5452
:::
5553

@@ -59,10 +57,45 @@ See ["Configure backup schedules"](/cloud/manage/backups/configurable-backups) f
5957

6058
<EnterprisePlanFeatureBadge/>
6159

62-
For enterprise customers, ClickHouse Cloud offers Bring Your Own Bucket (BYOB) functionality that allows customers to store backups in their own cloud provider buckets.
63-
You can take backups to your own cloud service provider (CSP) account:
64-
- AWS S3
65-
- Google Cloud Storage
66-
- Azure Blob Storage
60+
ClickHouse Cloud allows exporting backups to your own cloud service provider (CSP) account storage (AWS S3, Google Cloud Storage, or Azure Blob Storage).
61+
If you configure backups to your own bucket, ClickHouse Cloud will still take daily backups to its own bucket.
62+
This is to ensure that we have at least one copy of the data to restore from in case the backups in your bucket get corrupted.
63+
For details of how ClickHouse Cloud backups work, see the [backups](/cloud/manage/backups/overview) docs.
64+
65+
In this guide, we walk through how you can export backups to your AWS, GCP, Azure object storage, as well as how to restore these backups in your account to a new ClickHouse Cloud service.
66+
We also share backup / restore commands that allow you to export backups to your bucket and restore them.
67+
68+
:::note Cross-region backups
69+
Users should be aware that any usage where backups are being exported to a
70+
different region in the same cloud provider will incur [data transfer](/cloud/manage/network-data-transfer)
71+
charges.
72+
73+
Currently, we do not support cross-cloud backups, nor backup / restore for services utilizing [Transparent Data Encryption (TDE)](/cloud/security/cmek#transparent-data-encryption-tde) or for regulated services.
74+
:::
6775

6876
See ["Export backups to your own Cloud account"](/cloud/manage/backups/export-backups-to-own-cloud-account) for examples of how to take full and incremental backups to AWS, GCP, Azure object storage as well as how to restore from the backups.
77+
78+
### Backup options {#backup-options}
79+
80+
To export backups to your own cloud account, you have two options:
81+
82+
<VerticalStepper headerLevel="h5">
83+
84+
##### Via Cloud Console UI {#via-ui}
85+
86+
External backups can be [configured in the UI](/cloud/manage/backups/backup-restore-via-ui).
87+
By default, backups will then be taken daily (as specified in the [default backup policy](/manage/backups/overview#default-backup-policy)).
88+
However, we also support [configurable](/cloud/manage/backups/configurable-backups) backups to your own cloud account, which allows for setting a custom schedule.
89+
It is important to note that all backups to your bucket are full backups with no relationship to other previous or future backups.
90+
91+
##### Using SQL commands {#using-commands}
92+
93+
You can use [SQL commands](/cloud/manage/backups/backup-restore-via-commands) to export backups to your bucket.
94+
95+
</VerticalStepper>
96+
97+
:::warning
98+
ClickHouse Cloud will not manage the lifecycle of backups in customer buckets.
99+
Customers are responsible for ensuring that backups in their bucket are managed appropriately for adhering to compliance standards as well as managing cost.
100+
If the backups are corrupted, they will not be able to be restored.
101+
:::

docs/cloud/features/08_backups/backups-to-own-cloud/_category_.yml

Lines changed: 0 additions & 3 deletions
This file was deleted.

docs/cloud/features/08_backups/backups-to-own-cloud/export-backups-to-own-cloud-account.md

Lines changed: 0 additions & 57 deletions
This file was deleted.
File renamed without changes.
File renamed without changes.
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
label: 'Bring Your Own Backup'
2+
collapsible: true
3+
collapsed: false

docs/cloud/reference/data-resiliency.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
slug: /cloud/disaster-recovery
2+
slug: /cloud/data-resiliency
33
sidebar_label: 'Data resiliency'
44
title: 'Disaster recovery'
55
description: 'This guide provides an overview of disaster recovery.'

0 commit comments

Comments
 (0)