8.5 Backup, restore and disaster recovery
You have restored from a backup at least once, so you know the backup works.
Before:03. Storage & DatabasesUnlocks:10. Architecture & Migration11. Projects, Certification & Portfolio
A backup that has never been restored is a hope, not a backup, and this topic's demand is the drill: run a restore, time it, write down the number. RPO and RTO frame the design — how much you can lose, how long you can be down — and retention, immutability against ransomware, and the multi-zone-versus-multi-region price complete it. It closes the observability module because recovery is reliability's last line. The confusion it removes is equating replication with backup; replication faithfully copies your mistake to every zone at once.
Work through these
RPO and RPO: what you can lose and how long you can be down
Two numbers define recovery: how much recent data you can afford to lose, and how long you can afford to be down. Everything else in this item is a consequence of those two.
Backup strategies, retention and immutability against ransomware
How long backups are kept, and whether they can be altered once written, decide whether they survive an attacker who reaches your account. Immutability is what makes a backup ransomware-resistant.
Multi-zone vs multi-region recovery, and their price
Recovering within a region and recovering to another are different problems with different price tags. Choosing between them is a business decision that should be made explicitly.
A restore drill: run it, time it, write down the number
A restore you have performed and timed is a capability; one you have only configured is a hope. Writing the measured time down is what turns the drill into a plan.
Sign in to keep your progress.
Free resources
We haven't checked most of these for screen reader use yet.
Links last checked 29 Aug 2026.
Stuck here?
Ask a mentor. A real person answers, and they can see exactly which topic you're on. Usually within a couple of working days.
Checking your session…
Topics shown in module order.