What to back up
- The complete
/app_data volume
- The external database when
DATABASE_URL is configured
- Deployment configuration without exposing secrets in an unsafe location
- The exact Presenton image tag or digest used by the backup
/app_data may contain presentations, uploads, generated assets, exports, templates, settings, authentication state, the default SQLite database, and local presentation memory.
Recovery procedure
- Stop writes to the affected deployment.
- Create a safety copy of the current data before restoring anything.
- Restore
/app_data and any external database from matching backups.
- Start the same Presenton version used when the backup was created.
- Verify sign-in, presentations, uploads, providers, editing, export, API, and MCP as applicable.
- Upgrade only after the restored deployment is healthy.
A backup is not complete until it has been restored successfully in a separate test environment.
