Hardware fails, people delete things by mistake, and ransomware encrypts everything it can reach. The question is not whether you will need a backup, but whether it will work when you do.
The 3-2-1 rule
- 3 copies of your data
- on 2 different types of storage
- with 1 copy off-site
Many organisations now add a copy that is immutable or offline, so ransomware cannot alter it.
Define your targets
| Term | Question it answers |
|---|---|
| RPO (recovery point objective) | How much data can we afford to lose? One hour? One day? |
| RTO (recovery time objective) | How long can we be down before it seriously hurts? |
What to back up
- Databases (with consistent snapshots)
- File stores and attachments
- Configuration, custom code and infrastructure definitions
- Credentials, stored securely and separately
Test the restore
Schedule restore drills. Restore to a separate environment, check the application works and the data is complete, and time how long it took. Fix what you find.