Business continuity is the discipline of ensuring that an organisation’s critical functions can continue, or be rapidly restored, during and after a disruptive event such as an outage, disaster, or cyber-incident. It combines planning, redundancy, recovery procedures, and testing to limit downtime and data loss against defined objectives. In technical infrastructure it is realised through high availability, disaster recovery, fault tolerance, and resilient architecture, and is closely coupled with risk management.
Overview
- Disruptions span hardware failure, natural disaster, cyber-attack, and supply interruption.
- A business continuity plan identifies critical processes, dependencies, and acceptable downtime.
- Recovery objectives are defined as RTO (time to restore) and RPO (tolerable data loss).
- Effective continuity requires both technical safeguards and rehearsed organisational procedures.
Mechanisms
- Redundant, geographically distributed infrastructure to remove single points of failure.
- Regular backups and tested restore procedures via Disaster Recovery.
- Automated failover and Fault Tolerance to absorb component loss.
- Continuity testing, tabletop exercises, and Incident Response runbooks.
Key aspects
- RTO and RPO: quantified targets governing recovery design.
- Criticality analysis: prioritising functions by business impact.
- Dependency mapping: understanding upstream and downstream couplings.
- Governance: ownership, communication, and regulatory compliance.
Applications
- Financial services and healthcare where downtime is intolerable.
- Cloud and data-centre architectures using multi-region redundancy.
- Critical national infrastructure and emergency services.
- SLA commitments codified in a Service Level Agreement.