Rehearse a three-layer restore

Context and provenance

Keep a complete application ZIP so the built-in texts, images and original source archives remain available. Export Data studio's complete browser backup to preserve reading notes, collections, content packs and saved studio/publishing drafts. Use the server backup command for contributor accounts, review decisions, the ledger and editorial records. None of these three files substitutes for the others.

Rehearse in a fresh browser profile and a separate server database path. Extract the application, restore the browser backup and open several known notes and drafts. Start the server against a copy of its checked backup. Confirm a contributor, a reviewed record and an audit event. Avoid testing a restore by overwriting your only working copy.

Record what was checked and when. An archive that opens is only one part of success: relationships, permissions and recent changes must also survive. SQLite's backup interface supports consistent database snapshots; the included command uses it and runs an integrity check. A successful snapshot still needs a practical restore rehearsal at the application level.

Sources and evidence

1. SQLite: Online Backup API