Update overview.md #3955
Open
Update overview.md #3955
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added section to outline backup and restore duration guidance.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
|
|
||
| Restore durations are about the same as the backup durations. | ||
|
|
||
| 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.
Suggested change
| 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. | |
| We recommend testing with your own database or sample data to get better estimates as the actual duration depends on several factors as outlined 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. | ||
|
|
||
| Restore durations are about the same as the backup durations. |
|
|
||
| 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.
We should note these are VERY broad generalizations
| @@ -171,6 +171,16 @@ SYNC SETTINGS max_table_size_to_drop=2097152 -- increases the limit to 2TB | |||
| ``` | |||
| ::: | |||
|
|
|||
| ## 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. | |||
There was a problem hiding this comment.
Restoring incremental backups are slightly slower
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added section to outline backup and restore duration guidance.
Summary
Checklist