B5What the client asks
“Is any of this backed up?”
Asked once, answered with a yes, and verified by nobody until the morning it matters.
What actually goes wrong
A backup that has never been restored is a file, not a backup. The first restore attempt is not the moment to discover it is missing the uploads, or the schema, or three hours.
The half nobody budgets is the restore: the command, the practice, and the knowledge of exactly what is lost between the last backup and the failure.
What Grit does about it
- Backup and restore are both commands, in every project, including the uploads and not only the database.
- The admin has a data page that shows what exists and when it was taken.
- Restoring into a scratch environment is the documented habit, not an emergency procedure.
The commands
grit backup
The half that counts
grit restore backup-2026-10-22.zip
What it does not do
Where the archives live and how long they are kept is yours. A backup on the same disk as the database is a copy, not a backup.