Backup and restore
Backups are only useful when the restore path is known.
A small production server needs more than a folder named backup. It needs a runbook that says what is backed up, where it lives, how long it is retained, how to restore it, and who owns the test.
DataDatabase and uploads
ConfigServer state
RestoreProof
Linux server backup planning often starts too late, usually after a deployment mistake, disk issue, deleted upload folder, or database problem. A practical backup runbook does not need to be complex. It needs to be explicit about what matters and how to recover it.
Official source note: PostgreSQL documents backup and restore approaches including SQL dumps, file-system backup, and continuous archiving concepts: PostgreSQL backup and restore documentation.
Backup runbook path
01List data, configs, uploads, env files, and provider snapshots02Define schedule, storage, retention, and restore command03Test recovery and hand over ownership
