-
Notifications
You must be signed in to change notification settings - Fork 16
Backup and restore documentation #336
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
Conversation
… in the lifecycle maintenance guide.
…iderations" and clarify backup requirements for PowerSync self-hosted deployments. Add link to "Restoring Your Source Database."
…ion by linking to the consistency section.
|
|
||
| - PowerSync's replication state may become invalid | ||
| - The PowerSync Service will need to reprocess data from the restored database | ||
| - The reprocessing happens automatically |
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.
I'm not sure if this reprocessing will actually happen automatically in all cases - we need to test this for each one.
| - PowerSync's replication state may become invalid | ||
| - The PowerSync Service will need to reprocess data from the restored database | ||
| - The reprocessing happens automatically | ||
| - Clients can continue syncing during reprocessing, though they may experience temporary delays |
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.
Specifically note that clients will continue syncing the old data during reprocessing - no new changes will be synced here until reprocessing completed.
…ion: specify that reprocessing may require manual triggering and that new changes won't sync until completion, while existing data can continue syncing.
|
New PR: #348 |
Added documentation explaining what happens when a source database is restored and how that impacts PowerSync
usage/lifecycle-maintenance/restoring-source-database) covering restores, reprocessing, and re-sync expectations"self-hosting/lifecycle-maintenance/backup-and-recovery") for backup and recovery considerations specifically with regards to self-hosting