-
Notifications
You must be signed in to change notification settings - Fork 345
Update export-backups-to-own-cloud-account.md #3948
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
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
## Backup / Restore to AWS S3 Bucket {#backup--restore-to-aws-s3-bucket} | ||
# Backup / restore {#backup-restore} | ||
|
||
:::note |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This note is only for aws (role based authentication). We also need more context about role based authentication, which would be https://clickhouse.com/docs/cloud/security/secure-s3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also in example command for role based authentication, and not that that is only possible for AWS
S3('https://testchbackups.s3.amazonaws.com/backups/my_incremental', '<key id>', '<key secret>') | ||
``` | ||
|
||
### Backup and restore all service data {#backup-and-restore-all-service-data} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Recommended full backup or something similar. Also we should note that BACKUP ALL
will not work, because they won't have enough permissions to restore it
**Full Backup** | ||
### Take a DB backup {#take-a-db-backup} | ||
|
||
**Full backup** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a full backup
**Full Backup** | ||
### Take a DB backup {#take-a-db-backup} | ||
|
||
**Full backup** | ||
|
||
```sql |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Backup single database, similar for tables, see command summary here https://clickhouse.com/docs/operations/backup#command-summary
**Full Backup** | ||
### Take a DB backup {#take-a-db-backup} | ||
|
||
**Full backup** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should move up the recommended command, it should be first, otherwise it could be missed
|
||
```sql | ||
BACKUP DATABASE test_backups | ||
TO S3('https://storage.googleapis.com/test_gcs_backups/<uuid>/my_incremental', 'key', 'secret') | ||
SETTINGS base_backup = S3('https://storage.googleapis.com/test_gcs_backups/<uuid>', 'key', 'secret') | ||
``` | ||
|
||
### Restore from a backup {#restore-from-a-backup-2} | ||
# Granular backups {#granular-backups} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not necessary, if you want you can add a section about granular restores
Summary
Changes from:
#3945
#3944
Checklist