Skip to content

Commit e2fd771

Browse files
authored
Revert "Update export-backups-to-own-cloud-account.md"
1 parent ece99ed commit e2fd771

File tree

2 files changed

+15
-58
lines changed

2 files changed

+15
-58
lines changed

docs/cloud/manage/backups/export-backups-to-own-cloud-account.md

Lines changed: 14 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -61,19 +61,18 @@ You will need the following details to export/restore backups to your own CSP st
6161
2. Access HMAC key and HMAC secret.
6262
6363
<hr/>
64-
65-
# Backup / restore {#backup-restoer}
64+
# Backup / Restore
6665
6766
:::note:::
6867
1. For restoring the backup from your own bucket into a new service, you will need to update the trust policy of your backups storage bucket to allow access from the new service.
6968
2. The Backup / Restore commands need to be run from the database command line. For restore to a new service, you will first need to create the service and then run the command.
7069
:::
7170
72-
## Backup / restore to AWS S3 bucket {#backup--restore-to-aws-s3-bucket}
71+
## Backup / Restore to AWS S3 Bucket {#backup--restore-to-aws-s3-bucket}
7372
74-
### Take a DB backup {#take-a-db-backup}
73+
### Take a DB Backup {#take-a-db-backup}
7574
76-
**Full backup**
75+
**Full Backup**
7776
7877
```sql
7978
BACKUP DATABASE test_backups
@@ -87,11 +86,11 @@ You will need to use a different UUID for each new backup in this subdirectory,
8786
For example, if you are taking daily backups, you will need to use a new UUID each day.
8887
:::
8988

90-
**Incremental backup**
89+
**Incremental Backup**
9190

9291
```sql
9392
BACKUP DATABASE test_backups
94-
TO S3('https://testchbackups.s3.amazonaws.com/backups/<uuid>/my_incremental', '<key id>', '<key secret>')
93+
TO S3('https://testchbackups.s3.amazonaws.com/backups/<uuid>', '<key id>', '<key secret>')
9594
SETTINGS base_backup = S3('https://testchbackups.s3.amazonaws.com/backups/<base-backup-uuid>', '<key id>', '<key secret>')
9695
```
9796

@@ -105,11 +104,11 @@ FROM S3('https://testchbackups.s3.amazonaws.com/backups/<uuid>', '<key id>', '<k
105104

106105
See: [Configuring BACKUP/RESTORE to use an S3 Endpoint](/operations/backup#configuring-backuprestore-to-use-an-s3-endpoint) for more details.
107106

108-
## Backup / restore to Azure Blob Storage {#backup--restore-to-azure-blob-storage}
107+
## Backup / Restore to Azure Blob Storage {#backup--restore-to-azure-blob-storage}
109108

110-
### Take a DB backup {#take-a-db-backup-1}
109+
### Take a DB Backup {#take-a-db-backup-1}
111110

112-
**Full backup**
111+
**Full Backup**
113112

114113
```sql
115114
BACKUP DATABASE test_backups
@@ -118,7 +117,7 @@ TO AzureBlobStorage('<AzureBlobStorage endpoint connection string>', '<container
118117

119118
Where `uuid` is a unique identifier, used to differentiate a set of backups.
120119

121-
**Incremental backup**
120+
**Incremental Backup**
122121

123122
```sql
124123
BACKUP DATABASE test_backups
@@ -136,19 +135,19 @@ FROM AzureBlobStorage('<AzureBlobStorage endpoint connection string>', '<contain
136135

137136
See: [Configuring BACKUP/RESTORE to use an S3 Endpoint](/operations/backup#configuring-backuprestore-to-use-an-azureblobstorage-endpoint) for more details.
138137

139-
## Backup / restore to Google Cloud Storage (GCS) {#backup--restore-to-google-cloud-storage-gcs}
138+
## Backup / Restore to Google Cloud Storage (GCS) {#backup--restore-to-google-cloud-storage-gcs}
140139

141-
### Take a DB backup {#take-a-db-backup-2}
140+
### Take a DB Backup {#take-a-db-backup-2}
142141

143-
**Full backup**
142+
**Full Backup**
144143

145144
```sql
146145
BACKUP DATABASE test_backups
147146
TO S3('https://storage.googleapis.com/<bucket>/<uuid>', <hmac-key>', <hmac-secret>)
148147
```
149148
Where `uuid` is a unique identifier, used to differentiate a set of backups.
150149
151-
**Incremental backup**
150+
**Incremental Backup**
152151
153152
```sql
154153
BACKUP DATABASE test_backups
@@ -163,43 +162,3 @@ RESTORE DATABASE test_backups
163162
AS test_backups_restored_gcs
164163
FROM S3('https://storage.googleapis.com/test_gcs_backups/<uuid>', 'key', 'secret')
165164
```
166-
167-
# Granular backups {#granular-backups}
168-
169-
The `BACKUP` command also works with granular backups of specific tables. Example AWS commands for backing up a specific table are listed below. GCP and Azure commands are similar to the ones explained above, except that they need to be customized to backup specific tables.
170-
171-
### Take a granular backup {#take-a-granular-backup}
172-
173-
**Full Backup**
174-
```sql
175-
BACKUP TABLE data TO S3('https://testchbackups.s3.amazonaws.com/backups/<uuid>', '<key id>', '<key
176-
secret>')
177-
```
178-
179-
**Incremental backup**
180-
181-
```sql
182-
BACKUP TABLE data TO S3('https://testchbackups.s3.amazonaws.com/backups/my_incremental/', '<key id>', '<key
183-
secret>') SETTINGS base_backup = S3('https://testchbackups.s3.amazonaws.com/backups/<base-backup-uuid>', '<key id>', '<key
184-
secret>')
185-
```
186-
187-
### Restore from a granular backup {#restore-from-granular-backup}
188-
```sql
189-
RESTORE TABLE data AS data3 FROM
190-
S3('https://testchbackups.s3.amazonaws.com/backups/my_incremental', '<key id>', '<key secret>')
191-
```
192-
193-
### Backup and restore all service data {#backup-and-restore-all-service-data}
194-
195-
**Backup**
196-
197-
```sql
198-
BACKUP TABLE system.settings_profiles, TABLE system.row_policies, TABLE system.quotas, TABLE system.functions, ALL EXCEPT DATABASES INFORMATION_SCHEMA,information_schema,system TO S3('https://testchbackups.s3.amazonaws.com/backups/', '<key id>', '<key secret>')
199-
```
200-
201-
**Restore**
202-
203-
```sql
204-
RESTORE ALL FROM S3('https://testchbackups.s3.amazonaws.com/backups/', '<key id>', '<key secret>')
205-
```

styles/ClickHouse/Headings.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,6 @@ exceptions:
6363
- Docker Compose
6464
- Kafka
6565
- Google Cloud Run
66-
- Google Cloud Storage
67-
- GCS
6866
- NPM
6967
- OTel
70-
- SQL
68+
- SQL

0 commit comments

Comments
 (0)