-
Notifications
You must be signed in to change notification settings - Fork 30
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
RFC: Databend Disaster Recovery #1548
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
Signed-off-by: Xuanwo <[email protected]>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
`BACKUP` and `RESTORE` database: | ||
|
||
```sql | ||
BACKUP DATABASE <database_name> |
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.
Maybe we can allow users to specify a single database, multiple databases, or all databases within one SQL statement.
|
||
During the backup process, Databend reads existing table snapshots to generate a `BackupManifest` file, dumps metadata from the metasrv, and copies all related data files to the backup storage. | ||
|
||
During the restore process, Databend reads the `BackupManifest` file from the backup storage, copies all related data files to their original location, and restores the metadata to the metasrv. |
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.
What does "original location" refer to?
Rendered: https://github.com/Xuanwo/databend-docs/blob/rfc-dr/docs/en/guides/90-community/02-rfcs/20250109-disaster-recovery.md