-
Notifications
You must be signed in to change notification settings - Fork 339
Update overview.md #3955
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?
Update overview.md #3955
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -171,6 +171,16 @@ | |||||
``` | ||||||
::: | ||||||
|
||||||
## Backup and Restore Duration | ||||||
|
||||||
Backup and restore durations depend on several factors such as the size of the database as well as the schema and the number of tables in the database. Incremental backups will usually complete much faster than a full backup as less data is being backed up. Restoring from an incremental backup, however, will not be faster than restoring from a full backup as all incremental backups and the last full backup in the chain have to be included in the restore as explained above. | ||||||
|
||||||
In our testing, we have seen that smaller backups ~1 TB could take up to 10-15 mins or longer to backup. Backups less than 20 TB should complete within an hour, and backing up 50 TB of data should take about 2-3 hours. Backups get economies of scale at larger sizes, and we have seen backups of up to 1 PB for some internal services complete in about 10 hours. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should note these are VERY broad generalizations |
||||||
|
||||||
Restore durations are about the same as the backup durations. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Check this |
||||||
|
||||||
We recommend testing with your own database and sample data to get better estimates as the actual duration depends on several factors as outlined above. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
## Configurable Backups {#configurable-backups} | ||||||
|
||||||
If you want to set up a backups schedule different from the default backup schedule, take a look at [Configurable Backups](./configurable-backups.md). | ||||||
|
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.
Restoring incremental backups are slightly slower