Data Protection Concepts and Challenges
Domain 1 tests the vocabulary and trade-offs underneath every protection design: how much data you can lose, how long you can be down, and which copy type solves which problem. Expect questions that contrast backup, replication, and archive, and that test whether you can turn business requirements into RPO/RTO targets.
Core rules and concepts
- RPO is the maximum acceptable data loss, expressed as time. RTO is the maximum acceptable time to restore service. They are business decisions; a product feature only satisfies them.
- Backup creates a point-in-time copy for recovery from deletion, corruption, or ransomware. Replication maintains a secondary copy for availability or DR, but it can propagate logical corruption. Archive is long-term retention for compliance or reference, not a fast recovery tier.
- 3-2-1 means three copies, on two media types, with one offsite. A modern extension adds one immutable or air-gapped copy.
- Retention is driven by regulation, legal hold, and business value. GFS is a common schedule, but retention and schedule are separate settings.
- Deduplication and compression reduce capacity and bandwidth, not the need for independent copies or restore testing.
- Cyber resilience requires immutability, isolation, anomaly detection, and a tested recovery runbook.
Worked example
A service owner states 15-minute RPO and 4-hour RTO. A nightly backup cannot meet 15 minutes. Snapshots or asynchronous replication every 15 minutes can meet the RPO, but they are not a substitute for backup because a deleted table or encrypted file replicates too. The design pairs frequent snapshots/replication for availability with daily backups to immutable protection storage for recovery. If the daily change rate is 12 TB x 4% = 480 GB and the backup window is 6 hours (21,600 seconds), the required throughput is about 22 MB/s before dedupe; at 4:1 dedupe it is about 5.6 MB/s, leaving headroom for metadata and verification.
Traps that cost marks
- Swapping RPO and RTO.
- Calling replication a backup.
- Treating RAID or snapshots as a complete recovery strategy.
- Assuming a high dedupe ratio applies to every data type.
- Setting retention without legal hold or deletion requirements.