The Librarian's Fire Drill: What Emergency Preparedness Teaches Us About Data Integrity
We spend a lot of time in the digital preservation field talking about bit rot, format obsolescence, and the slow, silent decay of data. These are our chronic illnesses, the long-term ailments we must manage. But we speak less often of the acute trauma: the fire, the flood, the catastrophic server failure. For that, we might look to an unexpected mentor: the emergency preparedness planner.
In a physical library or archive, disaster planning is a tangible, almost theatrical practice. Staff run drills. They know the exact location of the fire exits, the pull stations, and the collection priorities—which items get saved first if time is limited. This isn't abstract; it's a rehearsed physical response to a clear and present danger. This mindset, of practiced readiness for the worst-case scenario, is what our digital archives desperately need to borrow.
Our digital preservation plans often live in documents titled "Preservation Policy.pdf," buried on a shared drive. They are static, consulted only during audits. But an emergency plan is a living script. It asks not just "what could go wrong?" but "what do we do the second it does?" Who is the first person called when the storage array reports a critical failure at 2 AM? What is the verbal script for that call? Where is the physical, printed copy of the contact list and recovery procedure when the network is down?
This borrowed philosophy shifts our focus from purely technical safeguards to human-centric protocols. It forces us to acknowledge that during a crisis, people don't think clearly. They react. And the best reactions are those that have been practiced. We fire-drill our data recovery. We tabletop a ransomware attack, walking through each step of the response with the entire team, from systems admin to communications officer. This unites the technical response with the human one, ensuring everyone knows their role in the chaos.
The goal is to make the response to a digital emergency as instinctual as a librarian guiding patrons to an exit during a fire alarm. It’s about building muscle memory for the entire institution. By adopting the emergency planner's mindset, we stop seeing our backups and redundant systems as just technical solutions. They become the equivalent of fire extinguishers and emergency exits—critical tools in a rehearsed plan for survival. Because in the end, the best-preserved data is the data that survives the disaster we’ve already practiced for.
Notes & further reading
A few pages I came back to while writing this: