← Back to Concept Contrast

Concept Contrast Fable

Disaster recovery and business continuity: one keeps machines alive, the other keeps the business from stopping

Conclusion first:Project plans often put these two terms on the same page as if they mean the same thing. Disaster recovery is responsible for getting crashed systems and data running again; business continuity is responsible for keeping orders, customer service, contracts, and payments supported by alternatives during an interruption. Compress the latter into one table from the former, and when something goes wrong you discover that an entire half is missing.

Project plans often put these two terms on the same page as if they mean the same thing. Disaster recovery is responsible for getting crashed systems and data running again; business continuity is responsible for keeping orders, customer service, contracts, and payments supported by alternatives during an interruption. Compress the latter into one table from the former, and when something goes wrong you discover that an entire half is missing.

Fable

The same rainstorm, two completely different loss statements

The paper mill in the south of the city feared fire: it had to protect its account books and also keep the academy that ordered paper supplied without interruption. The mill manager ran two seemingly similar matters: one was restoring the ledgers, printing plates and warehouse after a fire; the other was keeping business running at a bare minimum during and after a fire. A new clerk, finding it troublesome, merged the two books into one, thinking both were about success or failure anyway.

At first no one objected. The manager wrote both matters into a "fire prevention charter," bought only new water vats and a backup account box, and when the shopkeeper saw that the page count was lower, he even praised them for saving trouble. But once peak season arrived, the old accounts suddenly could not be explained clearly: no one could say whether the previous stall had not finished or the next stall had not held the line.

They first added more seals and slogans and required everyone to write in more detail. As a result, the booklet grew thicker and disputes increased. When something went wrong, everyone could find a sentence to excuse themselves, but no one knew which end to save first.

The old steward called everyone into the courtyard and had them retrace the actual course of events. Whatever concerned the immediate action went into the first book; whatever concerned subsequent responsibility went into the second. The two books referenced each other, but were no longer mixed onto the same page.

After a small fire, the account books were recovered, but no one arranged the paper delivery cart, the temporary work shed, or customer notification. Once separated, many old conclusions changed: some work looked busy but did not actually block trouble; some arrangements were unremarkable in normal times yet preserved the whole in disaster.

To prevent newcomers from mixing things up again, the old steward had them each handle a small case. Only when the two ledgers could each answer their own questions and also connect with each other at the boundary would the small case pass. If someone still wrote the two matters on one page, they had to return to the scene and look again at who acted first and who was ultimately responsible; when it was unclear, it was better to ask once more than let a muddled account stay overnight; because on the day something truly went wrong, one missing line of distinction would make an extra team work in vain.

The abbot prepared two sets of contingency plans: one for how goods would be recovered, and one for how people, customers, money and delivery would be maintained. Later, when newcomers joined the trade, the old steward had them remember just one line: being able to save the assets is one thing, being able to keep the business from stalling is another.

Disaster recovery

The ability to restore IT infrastructure and data after a system outage, with core metrics being recovery time objective and recovery point objective.

Business continuity

A management system that ensures critical business functions continue during disruptions or recover as quickly as possible, covering people, processes, suppliers and communications, not just IT.

Story Mapping

  • Building A's backup machine room and off-site backup: disaster recovery, IT-level system and data recovery
  • Manual operating procedures, customer contact lists, backup channels: business continuity, covering non-IT business processes
  • After Building B's systems were restored, business was still in chaos: there was DR but no BC, and machine room tenants could not operate normally
  • Two independent documents each rehearsed separately: DR and BC planned separately, tested separately, and held accountable separately

Applying it to Andy Ren Xu's project

When making proposals for clients, the disaster recovery section lists system recovery metrics, while the business continuity section lists the recovery priorities and alternative processes for key business functions. The two types of documents are signed separately; do not write BC as a subordinate chapter of DR. Whether business can continue running after an agent system goes down affects client renewals more than how long it takes the server room to recover.

京ICP备2026014272号