MSK · UTC+3 · 18 Nov 2026note

← all notes

A backup you have not restored is a rumour

backups30 Oct 2026 · 5 min read

Every backup story starts the same way: the job is green, the log says “completed”, and nobody has tried to get the data back. The first restore is where the real configuration lives, and it is usually wrong.

The drill

Once a month, on a machine that is not the production host, restore the latest snapshot of one dataset and check three things: the file count, the total size, and one file that changed yesterday. The last check is the important one — it catches snapshots that are complete but a week old.

host restic repo second provider drill nightly, 02:10 weekly, 7 daily · 4 weekly · 6 monthly monthly
Two copies in two providers, and a drill on a machine that is not production. The drill is the part that fails.

What the drill found

None of this was visible from the backup logs. All three were visible within twenty minutes of a real restore.

The rule

If a restore has not been done, the backup is a hypothesis. Write the drill into the calendar, do it on a machine that is not production, and delete the copy afterwards — otherwise you will find it in six months and wonder what it is.