Backup and Disaster Recovery
Last reviewed 3 Nov 2026
Backup is keeping copies of your data; disaster recovery is the plan and practice for getting systems working again after a failure, attack or mistake. For a business, the real test is not whether backups exist but whether you can restore them quickly and completely.
Key Facts
| Two key numbers | RPO: how much data you can afford to lose. RTO: how long you can afford to be down |
|---|---|
| 3-2-1 rule | Three copies, on two different types of storage, one kept off-site or in a separate account |
| Biggest threat today | Ransomware that also encrypts reachable backups |
| Most common failure | Backups never test-restored until the day they are needed |
A sensible baseline for SMEs
| Item | Baseline |
|---|---|
| Database backups | Automatic daily, with point-in-time recovery if available |
| Copies | At least one in a separate cloud account or region |
| Retention | 30 days or more |
| Restore test | Quarterly, timed and written down |
| Access | Backups not deletable from everyday admin accounts |
Ask any software vendor how backups work and request a restore demonstration. See cloud hosting and data migration.
Frequently Asked Questions
Does cloud hosting mean we are backed up?
Not automatically. Check what the provider backs up, for how long, and who can restore it.
How often should we test restores?
At least quarterly, and after any major change to the system.
Take the next step
Need help implementing this in your business?
Turbo Bytes Consulting helps businesses streamline operations and build custom software architectures that scale without chaos.