Sample: A boring backup is a good backup

Sample content: commands and hostnames below are illustrative placeholders.

The useful backup is not the one with the cleverest storage graph. It is the one that runs on schedule, reports failure clearly, and has survived a restore rehearsal.

The routine

The sample setup treats each service as three things: configuration, mutable data, and a short restore note. A scheduled job creates the snapshot; a separate check verifies age and size; an off-site copy receives only encrypted data.

service/
├── compose.yml
├── data/
└── RESTORE.md

The status page does not announce success every night. It stays quiet unless the newest verified snapshot is older than the agreed window.

Rehearsal

A backup without a restore test is a hopeful file collection. The rehearsal uses a disposable host, follows only RESTORE.md, and records any unstated dependency discovered along the way.

The result should be boring: a known command, a visible check, and no archaeology during an outage.