Skip to content

Conversation

@bean1352
Copy link
Contributor

Added documentation explaining what happens when a source database is restored and how that impacts PowerSync

  • Separated general restore behavior from self-hosted backup and recovery guidance
  • Added a new page (usage/lifecycle-maintenance/restoring-source-database) covering restores, reprocessing, and re-sync expectations
  • Added a new page ("self-hosting/lifecycle-maintenance/backup-and-recovery") for backup and recovery considerations specifically with regards to self-hosting

…iderations" and clarify backup requirements for PowerSync self-hosted deployments. Add link to "Restoring Your Source Database."
@bean1352 bean1352 requested a review from rkistner January 14, 2026 10:39

- PowerSync's replication state may become invalid
- The PowerSync Service will need to reprocess data from the restored database
- The reprocessing happens automatically
Copy link
Contributor

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
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants