Build a Robust Disaster Recovery Strategy
Company Name: _________________________________
Primary IT Contact: _________________________________
Last Updated: _________________________________
| System/Application | Data Size (GB) | Update Frequency | Business Priority (1-5) |
|---|---|---|---|
| Email Server | ___ | ☐ Real-time ☐ Hourly ☐ Daily | ☐ 5 ☐ 4 ☐ 3 ☐ 2 ☐ 1 |
| File Server | ___ | ☐ Real-time ☐ Hourly ☐ Daily | ☐ 5 ☐ 4 ☐ 3 ☐ 2 ☐ 1 |
| Customer Database | ___ | ☐ Real-time ☐ Hourly ☐ Daily | ☐ 5 ☐ 4 ☐ 3 ☐ 2 ☐ 1 |
| Accounting System | ___ | ☐ Real-time ☐ Hourly ☐ Daily | ☐ 5 ☐ 4 ☐ 3 ☐ 2 ☐ 1 |
| ________________ | ___ | ☐ Real-time ☐ Hourly ☐ Daily | ☐ 5 ☐ 4 ☐ 3 ☐ 2 ☐ 1 |
| ________________ | ___ | ☐ Real-time ☐ Hourly ☐ Daily | ☐ 5 ☐ 4 ☐ 3 ☐ 2 ☐ 1 |
RTO = Maximum acceptable downtime before business is severely impacted
| System | Target RTO | Current Capability | Gap? |
|---|---|---|---|
| ☐ 1hr ☐ 4hr ☐ 24hr ☐ 3 days | ☐ 1hr ☐ 4hr ☐ 24hr ☐ 3 days | ☐ Yes ☐ No | |
| File Server | ☐ 1hr ☐ 4hr ☐ 24hr ☐ 3 days | ☐ 1hr ☐ 4hr ☐ 24hr ☐ 3 days | ☐ Yes ☐ No |
| Database | ☐ 1hr ☐ 4hr ☐ 24hr ☐ 3 days | ☐ 1hr ☐ 4hr ☐ 24hr ☐ 3 days | ☐ Yes ☐ No |
RPO = Maximum acceptable data loss measured in time
| System | Target RPO | Backup Frequency | Meets Target? |
|---|---|---|---|
| ☐ 0 (no loss) ☐ 1hr ☐ 4hr ☐ 24hr | ☐ Continuous ☐ Hourly ☐ Daily | ☐ Yes ☐ No | |
| File Server | ☐ 0 (no loss) ☐ 1hr ☐ 4hr ☐ 24hr | ☐ Continuous ☐ Hourly ☐ Daily | ☐ Yes ☐ No |
| Database | ☐ 0 (no loss) ☐ 1hr ☐ 4hr ☐ 24hr | ☐ Continuous ☐ Hourly ☐ Daily | ☐ Yes ☐ No |
Current Backup Architecture:
Primary Storage: _________________________________
Backup Copy 1 (Local): _________________________________
Backup Copy 2 (Offsite): _________________________________
☐ Meets 3-2-1 rule | ☐ Needs improvement
| Test Type | Frequency | Last Tested | Result |
|---|---|---|---|
| Single file restore | Weekly | ___/___/___ | ☐ Pass ☐ Fail |
| Full system restore (test environment) | Monthly | ___/___/___ | ☐ Pass ☐ Fail |
| Disaster recovery drill (full failover) | Quarterly | ___/___/___ | ☐ Pass ☐ Fail |
| Backup integrity verification | Daily (automated) | ___/___/___ | ☐ Pass ☐ Fail |
| Factor | On-Premise | Cloud (AWS, Azure, etc.) |
|---|---|---|
| Initial Cost | High (hardware, licenses) | Low (pay-as-you-go) |
| Monthly Cost | Low (electricity, maintenance) | Varies with data size |
| Scalability | Requires hardware upgrades | Instant, unlimited |
| Offsite Protection | Manual (tape rotation) | Built-in (geographic redundancy) |
| Recovery Speed | Fast (local network) | Depends on internet speed |
| Management | In-house IT required | Managed by provider |
Scenario 1: Ransomware Attack
Scenario 2: Server Hardware Failure
Downtime Cost Calculation:
Average revenue per hour: $_______________
Number of affected employees: _______________
Average hourly wage: $_______________
Total cost per hour of downtime: $_______________
If RTO is 24 hours, potential loss: $_______________
If RTO is 4 hours, potential loss: $_______________
ROI of improved backup/DR system: _______________