Rather than define terms first, let us follow one event from the first minute. The company is invented: Shree Textiles, a garment exporter in Tiruppur with 400 staff, a small server room in the basement, and an order-management system that every department depends on. At 2 a.m. during a heavy monsoon, water enters the basement and the server room loses power.
Minute zero to hour one: who decides?
The security guard calls the facilities manager, who calls the IT head. Already we are inside a plan, or inside the absence of one. A business continuity plan (BCP) begins here: who is the incident lead, who can declare a disaster, who contacts whom, and by what channel if the company email is down. Shree’s plan says the operations director declares, and a call tree lists mobile numbers. This is not technology. It is a list on paper, and it is what makes the next hours orderly.
Business continuity is the broad discipline of keeping critical business functions running, or restoring them quickly, during and after a disruption. The disruption could be flood, fire, a ransomware attack, a strike, a key supplier collapsing or a pandemic. Technology is only one dependency.
Hour one to day one: the business keeps moving
Shipments due that day still have to leave. Here the BCP matters more than any server. During its planning, Shree ran a business impact analysis (BIA): for each process, what is the maximum tolerable downtime, and what is lost per hour? Dispatch of export consignments turned out to be critical, because a missed vessel cut-off means penalties and a week’s delay. Payroll, on the other hand, could survive three days.
So the continuity measures were manual workarounds. Pre-printed dispatch forms, a printed weekly list of open orders kept in the warehouse office, and a standing arrangement to run shipping documentation from a freight forwarder’s office. People worked on paper for two days. Nobody enjoyed it, but containers shipped.
Meanwhile: the disaster recovery plan
In parallel, the IT team follows the disaster recovery (DR) plan, which is a subset of continuity concerned with restoring systems, data and infrastructure. Two numbers drive it:
- RTO, recovery time objective: how long the system may be down before the damage becomes unacceptable.
- RPO, recovery point objective: how much recent data you can afford to lose, measured as time. Backups taken every 24 hours imply an RPO of up to 24 hours.
The BIA gave the order system an RTO of eight hours and an RPO of one hour. Nightly backups to a drive in the same basement would have failed both targets spectacularly. Shree’s actual setup copies the database to a cloud region every hour and keeps a virtual-machine template ready to launch there. At 9 a.m. the team starts the replacement servers in the cloud, restores the latest copy (taken at 1 a.m., so about an hour of orders must be re-entered from emails and paper), repoints users and tests. By late afternoon, about 14 hours in, the system is up. That misses the eight-hour RTO. The post-incident review notes why: DNS changes took longer than planned, and one engineer had the only copy of the restore steps in his head.
What the walkthrough shows
Look at what each plan contributed. The BCP covered people, communication, manual workarounds, supplier arrangements, customer messaging and alternate premises. The DR plan covered servers, data, networks and the order of restoration. If only DR existed, Shree would have had a server team working beautifully while dispatch stood still. If only BCP existed, the paper workarounds would have been sustainable for two days but not two weeks.
Notice too that neither plan stops the flood. Prevention (raising the server room above ground level, in this case) is a separate, cheaper conversation. Continuity and recovery assume prevention failed.
Making the plans real
A plan that has never been exercised is a hope. Typical exercises, from cheap to expensive:
- A walkthrough, where owners read the plan aloud and spot gaps.
- A tabletop exercise, where a facilitator presents a scenario and the team talks through decisions.
- A technical restore test, actually recovering a system into an isolated environment and timing it.
- A full failover, switching live operations to the alternate site. Few organisations do this often, because it carries risk of its own.
Keep the plan accessible when systems are down: a printed copy, a copy on staff phones, a copy outside the building. Update it when people leave, which is the step most often forgotten. ISO 22301 is the international standard for business continuity management, and ISO 27001 includes continuity of information security as a control area, so auditors may ask to see test evidence.
Figures and names in the examples are illustrative.
Leave a Reply