Designing a Backup & DR Strategy: RTO, RPO, and Testing

Designing a Backup & DR Strategy

A backup strategy without defined RTO/RPO targets is just hope. This guide builds a measurable, testable DR strategy.

Define RTO and RPO First

Term	Definition	Question
RPO	Recovery Point Objective	How much data can we afford to lose?
RTO	Recovery Time Objective	How long can we be down?

Example targets by system tier:

Tier	System	RPO	RTO
Tier 1	Core infrastructure (AD, DNS)	1 hour	4 hours
Tier 2	Business applications	4 hours	8 hours
Tier 3	Development/Test	24 hours	48 hours

The 3-2-1 Rule

3 copies of data
2 different media types
1 offsite copy

Extended 3-2-1-1-0:

1 air-gapped or immutable copy
0 errors on verified restores

Backup Tiers Implementation

TEXT

Production VM
    │
    ├── Tier 1: Snapshots (every 4h, retain 48h)
    │         └── Proxmox/VMware native snapshots
    │
    ├── Tier 2: Daily incremental (retain 30 days)
    │         └── Veeam/PBS to on-site backup server
    │
    ├── Tier 3: Weekly full (retain 13 weeks)
    │         └── Veeam to off-site backup
    │
    └── Tier 4: Monthly archive (retain 7 years)
              └── Cloud storage (S3/Glacier)

Veeam Backup Configuration

POWERSHELL

# Create backup job
Add-VBRViBackupJob -Name "Tier2-Daily" -Server "vcenter.corp.local"   -Entities "VM Folder Production"   -BackupRepository "OnSite-Backup"   -BackupType Incremental   -RetainBackups 30   -RunAfterThisJob "Tier1-Snapshots"

# Enable application-aware processing
Set-VBRJobAdvancedViOptions -Job "Tier2-Daily" -EnableVSSQuiescence $true

DR Testing Schedule

Frequency	Test Type	Duration
Monthly	Single VM restore test	2 hours
Quarterly	Full application stack restore	1 day
Annually	Full DR failover simulation	2 days

DR Runbook Template

MARKDOWN

# DR Runbook: [System Name]

## Contact List
- Primary: [Name] — [Phone]
- Secondary: [Name] — [Phone]
- Vendor: [Company] — [Support number]

## RTO: 4 hours | RPO: 1 hour

## Step 1: Assess Impact (30 min)
- [ ] Identify affected systems
- [ ] Determine failure cause
- [ ] Escalate if needed

## Step 2: Activate DR (1 hour)
- [ ] Access backup site
- [ ] Start restore from [backup location]
- [ ] Verify data integrity

## Step 3: Validation (1 hour)
- [ ] Test application functionality
- [ ] Notify stakeholders

Document, test, and update runbooks after every DR event.