The Shoemaker's Last: On the Shape of Your Backups
There is a shoemaker’s tool, called a last. It is a solid, foot-shaped form, carved from wood or cast in metal, around which a shoe is built. It is the mold, the truth, the unwavering shape of what a shoe should be. Without it, leather is just a supple skin; with it, it becomes something that fits, supports, and endures. I’ve come to think of our backup strategy not as an archive or a snapshot, but as our last.
We spend so much time talking about the act of backing up—the cron jobs, the incremental runs, the cloud storage costs—that we often forget to ask the more fundamental question: what shape are we preserving? A backup is not merely a copy of data; it is a cast of a system’s soul at a specific moment. It holds not just the files, but the permissions, the dependencies, the configurations, the very architecture of a working service. It is the negative from which you hope never to have to print the photograph.
The Form Dictates the Function
A shoemaker’s last isn’t generic; it is shaped for a specific purpose. A boot last is different from a slipper last. In the same way, our backup ‘last’ must be purpose-built. Are we preserving a monolithic database? Then our last must be a dump with strict transactional integrity. Is it a sprawling directory of user-generated content? Then our last must capture not just the files, but the intricate web of metadata and thumbnails that give them context. The shape of the backup dictates how, or if, it can be used to rebuild.
I’ve seen teams with impeccable backup routines stumble during a restore because their copy was a floppy silhouette, lacking the rigid structure of the original. They had the leather, but no last to stretch it over. The service never quite fit right again, limping along with subtle permissions errors and broken symlinks—a shoe that constantly pinches.
The quiet, boring work, then, is not in the nightly run of the backup script. It is in the periodic ritual of testing the last itself. We must, on occasion, attempt to build a shoe from it. We must spin up a isolated environment and restore the system, not to see if the data is there, but to see if the shape holds. Does it stand? Does it bear weight? Does it walk? This is the only way to know if your last is true, or if it has warped over time without anyone noticing.
In the end, reliability is not about having a copy. It is about having a form. It is the confidence that when everything else falls apart, you are left not with a pile of pieces, but with a solid, well-understood shape around which you can rebuild something that fits, supports, and endures.
Notes & further reading
A few pages I came back to while writing this: