Backup & Restore
Database backup approach, recovery targets, and restore testing.
Last updated: June 23, 2026
1. What we back up
- Primary database (Cloudflare D1) — All tenant inventory, hierarchy, users, roles, audit trail, and configuration
- Object storage (Cloudflare R2) — Customer-uploaded images (item photos, avatars)
- Not backed up by Inventifornia — Client-side offline outbox (IndexedDB) and browser localStorage cache; Customers should sync before device loss
2. Backup method
Production D1 databases are backed up using Cloudflare D1's backup API (wrangler d1 backup create). Backups are encrypted at rest within Cloudflare's infrastructure. Backup frequency:
- Automated: Daily snapshots retained on a 30-day rolling schedule
- On-demand: Before major schema migrations and production promotions
3. Recovery targets
| Metric | Target |
|---|---|
| Recovery Point Objective (RPO) | ≤ 24 hours (daily backup cadence) |
| Recovery Time Objective (RTO) | ≤ 4 hours for full database restore to alternate D1 instance |
Targets are objectives, not guarantees. Actual recovery time depends on incident scope and Cloudflare platform status.
4. Restore testing
Inventifornia performs restore validation on non-production environments before major releases. Production restore drills are conducted when infrastructure changes warrant verification.
Last successful restore test
June 16, 2026
Dev environment D1 backup restored and validated against migration smoke tests (June 2026 security audit cycle).
5. Customer export (recommended)
Customers should not rely solely on Inventifornia backups for records retention. Export audit trails and inventory via AdminCP CSV export (permission-gated) for agency records systems. See Data Retention.
Trust CenterTerms & ConditionsPrivacy PolicyCookie PolicyAcceptable Use PolicyOperational Data BoundaryData Processing Addendum