Backups
Backup retention policy: how many restore points do you need?
Backup retention decides how long historical recovery points remain available. Keeping only the newest copy can fail when a problem started days or weeks before anyone noticed, while retaining everything forever can create unnecessary cost, privacy, and management burden.
Estimate how long failures can remain hidden
Immediate hardware failures are obvious, but corrupted data, deleted records, compromised files, or bad automation can go unnoticed. Retention should extend far enough to reach a known-good state from before the likely detection window.
Use different frequencies for different ages when appropriate
A common pattern keeps frequent recent restore points and fewer older points. The correct schedule depends on recovery objectives and the backup product; the goal is useful history without storing redundant copies that provide little additional recovery value.
Include growth and change rate in capacity planning
Retention cost depends on how much data changes between backups, compression or deduplication, database churn, large binary files, and how full backups are constructed. Measure real backup-set growth instead of multiplying live storage by a fixed number.
Document deletion and compliance requirements too
Some data should not be retained indefinitely. Align backups with contractual, privacy, legal, and business requirements, and understand how deletion requests interact with protected historical copies and expiry schedules.