Backup
A copy of the data, to restore from when it is lost or damaged.
disaster recovery
It is not a matter of if it will happen, but when. A good disaster recovery plan does not prevent the problem: it tells you what to do and how long it will take.
Disaster Recovery (DR) is the set of plans, tools and procedures to restore systems and data after a serious event: the failure of a whole cloud region, a human error, a ransomware attack, data loss.
It is part of a wider topic, Business Continuity, which is about how the company keeps working during and after a crisis, with people and processes, not only systems.
High availability protects against small failures, disaster recovery against big ones. You need both.
A copy of the data, to restore from when it is lost or damaged.
Redundancy to survive a failure with no interruption, for example across several zones.
Recovery after a serious event, often in another place or region.
Keeping the whole business going, people and processes included.
The lower the numbers, the more the solution costs. That is why not every system has the same targets.
These are the four strategies also described in AWS guidance. Times are indicative and depend on the system.
| Strategy | How it works | Recovery | Cost |
|---|---|---|---|
| Backup and restore | You keep copies of the data and, if needed, rebuild everything from there. | Hours | Low |
| Pilot light | A minimal core, for example the replicated database, always runs on the other site. The rest is switched on when needed. | Tens of minutes or hours | Medium-low |
| Warm standby | A scaled-down but working version of the system is always on and ready to grow. | Minutes | Medium-high |
| Multi-site active/active | Several sites serve traffic together: if one fails, the others keep going. | Almost none | High |
List the services and assess what stopping them costs: this is the business impact analysis.
For each service, together with the people accountable for the business, not alone.
Look for the balance between targets and cost, service by service.
Infrastructure as code to recreate environments, and automatic backups that you check.
Who does what, and in which order. One copy must be reachable even when the systems are down.
Run restore tests, simulations and failover drills at regular intervals.
This is an introductory guide, written the way I understood things while working in the field. Every company organizes itself differently: take it as a starting point, not as a manual.