Backup & recovery guide
What is verified
The project uses managed daily database backups. Backup inventory has not been inspected: no timestamp, snapshot count or successful restore is claimed. Point-in-time recovery is not available; recovery targets daily snapshots.
Daily snapshots cover schema and data, not storage files. The full database export includes account password hashes but not storage files, secrets, sign-in provider settings or function code.
Recovery targets
Proposed RPO: up to one daily snapshot interval (approximately 24 hours), conditional on the actual snapshot timestamp. Proposed RTO: four hours for triage, export, restore and application checks. These are planning targets, not measured guarantees.
The owner must inspect the newest UTC snapshot and approve the targets. No restore drill has been performed as part of this preparation.
Preserve before restoring
Before any restore, export the current database and separately download storage files. Preserve app source, release notes and privately held integration settings.
An in-place restore permanently loses writes after the chosen snapshot and reverts schema too. The database is unavailable for a few minutes; the app may need compatibility changes afterward.
Isolated verification
Restore the exported database into a separate backend you control, reconfigure sign-in providers and keys, restore the separately saved storage files, then test password sign-in and authenticator verification.
Check company isolation, evidence reads, signed report verification, exports, audit chains and count reconciliation. Use fictional records for write checks; do not run paid detection or send emails to real people.
Application recovery
Evidence and case restoration requires the pending recovery controls to be approved. Only workspace administrators may restore records while underlying files remain. A record export is not a full backup and cannot recreate removed storage objects or authentication accounts.
After recovery, compare schema and counts, check sign-in and security screens, verify ten-minute-or-shorter download links, and record the test results. Use additive, approved database changes if app code no longer matches the restored schema.