Managello takes a fresh backup before every update — a database dump plus a snapshot of your uploaded files — and the update path is built around that safety net. Recovery is a one-click rollback, not a manual restore command.
Where backups live
They're written on the server, inside the app's storage volume, under storage/app/backups/ — a PostgreSQL dump (db-*.sql) and a copy of your private attachments. They ride on the same persistent volume as the rest of your data.
How recovery works
If an update's post-migration health check fails, the updater rolls back automatically — it restores the previous image and the pre-update database backup. You don't run anything.
If you need to roll back a completed update yourself, use one-click rollback in Settings → Updates. It restores the previous image plus the database backup taken before that update.
There is deliberately no "manually restore this tar file" command. Restore always goes through the updater so the image, database, and files move back together as one consistent set — the failure mode of hand-restoring a mismatched database is exactly what this design avoids.
What comes back
- Your database (projects, clients, requests, invoices — everything)
- Your uploaded files (logos, attachments, proofs)
- Your settings and branding
It's a complete point-in-time recovery to just before the update.
Before you rely on it
Open System Health and confirm the backup and storage indicators are green, and that you have free disk headroom — the updater refuses to run (and therefore can't back up) if the disk is too full.