The Cobbler and the Archivist: On Two Kinds of Backup Maintenance
There is a special tension that arrives with the morning coffee when you know a backup restore is on the docket. It’s a feeling familiar to anyone who tends to small services: a mix of procedural calm and the quiet dread of the unknown. Over the years, I’ve come to recognize two distinct species of this ritual, separated not by their technical mechanics but by their philosophy, their rhythm, and their very soul. I think of them as the Cobbler and the Archivist.
The Cobbler’s approach is immediate, practical, and tactile. Like a shoemaker repairing a sole, the Cobbler’s backups are frequent, granular, and meant for active use. They are the snapshots taken before a risky deployment, the database dumps made before a schema migration. The Cobbler knows the exact feel of the leather and the strength of the thread. They test their backups not with a formal schedule, but by using them, constantly. A failed patch is reverted in minutes using yesterday’s image; a corrupted user file is plucked from the hourly sync. The Cobbler’s work is one of iteration and immediate utility. Their confidence comes from the leather apron, the worn tools, and the knowledge that their hands are always in the work. The backup is not a historical record; it is a spare part, kept oiled and ready on the shelf.
The Cold Vault of History
The Archivist operates on a different plane. For them, a backup is not a spare part but a historical document. The Archivist’s process is slower, more ceremonial. They are not preparing for a stumble tomorrow, but for a cataclysm in a decade. Their backups are full-system images, meticulously documented and stored in cold, encrypted vaults—sometimes literally on tapes shipped to a mountain facility. The Archivist’s test is not a quick restore, but a carefully orchestrated drill performed once a year, a kind of fire alarm practice for the entire digital estate.
Where the Cobbler finds confidence in familiarity, the Archivist finds it in procedure. The integrity of the data is paramount; the speed of its return, secondary. Theirs is a faith in the checklist, the chain of custody, the unbroken sequence of hashes that proves the artifact is pristine and unchanged. The Archivist’s dread is not a failed deployment, but a silent, creeping bit-rot discovered years later, or a legal discovery request that demands proof of a system’s state from an era long past.
Most of us who run services are a blend of both, but we lean heavily one way. The Cobbler sleeps soundly knowing they can fix today’s breakage. The Archivist sleeps soundly knowing they can rebuild from the ashes. The danger lies in becoming exclusively one or the other. The pure Cobbler, for all their skill, may find their workshop has burnt down with all their spares inside. The pure Archivist, when faced with a minor but urgent crisis, will fumble with the combination to a vault while the service bleeds users.
The true art, then, is not in choosing a side but in knowing which role the moment demands. We must be quick-fingered cobblers for the daily wear and tear, and sober archivists for the long, silent weight of history. One keeps the service alive today; the other ensures its story can be told tomorrow.
Notes & further reading
A few pages I came back to while writing this: