From RPO/RTO to backup policy
Each application tier has different RPO/RTO. ERP and databases are usually Tier 0–1 with frequent backup and replication; non-critical shares may be daily only.
Document schedules, retention, repository locations, encryption, and application owners who sign off on restore tests.
3-2-1-1-0 in practice
Three copies, two media, one offsite/offline, one immutable copy, zero failed restore tests. Immutability may use hardened Linux repos, WORM object storage, or air-gapped tape.
Separate backup admin accounts from production AD; network segmentation to repositories is mandatory modern hardening.
Operations and audit
Track job success, alert on failures, and archive restore drill reports for audits. Automation does not replace monthly human review.
Intilogy runs tiering workshops, repository design, Veeam implementation, and first restore drills with your team.
Frequently asked questions
How is backup strategy different from DR?
Backup focuses on copies and data restore; DR includes infrastructure failover, runbooks, and full business continuity. Both complement each other.
