The data survived. The systems did not
A backup can preserve data, but returning to work also requires working applications. The British Library incident and lessons for recovery.
Access disappears first. Then comes the question about backups. In October 2023 an attack encrypted or destroyed much of the British Library’s server estate. Secure copies of its digital collections existed. That did not mean services could return quickly.
Nowhere ready to return
The March 2024 report describes a lack of viable recovery infrastructure. Some older applications were unsupported or incompatible with the new environment. Infrastructure rebuilding and system modernisation were ongoing.
What are we recovering?
NetOpiekun’s lesson: a file, a database and a working service represent different levels of readiness. A restored folder does not prove that an employee can find a document, open an order and save a change.
Data can survive while the ability to work does not.
Rehearse before the outage
We recommend restoring one critical service in an isolated environment. Record application versions, configuration, dependencies, licences and a secure way to obtain access. Opening an archive is not a sufficient test.
An administrator starts the service; its user performs an agreed business task. The exercise must not send real orders or customer messages. Start timing when recovery is requested, not only when copying begins.
When can we say it works?
Record recovery time, the age of restored data and missing components. If an installer or licence prevents startup, that becomes a specific action before the next exercise.
A backup success message closes the copying task. A successfully completed user task demonstrates that the particular service is back.
About this account
Based on the public report named below. The account concerns the period covered by that report; NetOpiekun recommendations are identified separately. This is not our client work or a description of the organisation’s current systems.