Course contentsShow
← System Design
Lesson 1431 of 1,91935. Backup and Disaster RecoveryFree lesson

Backup Retention Policies

Implementing grandfather-father-son or similar schemes to retain historical backups while managing storage costs.

Backup Retention Policies

What you'll learn: How to implement structured retention schemes like grandfather-father-son to balance historical data availability with storage costs.

The Challenge of Keeping Everything

Once you've established backup strategies (full, incremental, differential), you face a practical question: how long should you keep each backup? Keeping every backup forever provides maximum recovery options but becomes prohibitively expensive. Deleting too aggressively saves money but risks losing the ability to recover from older corruption or meet compliance requirements.

The Grandfather-Father-Son Scheme

The grandfather-father-son (GFS) retention policy is a classic approach that balances granularity with storage efficiency:

  • Son (daily backups): Keep the most recent 7 daily backups. These provide fine-grained, recent recovery points.
  • Father (weekly backups): Keep 4-5 weekly backups (typically the last backup from each week). These provide monthly coverage.
  • Grandfather (monthly backups): Keep 12 monthly backups. These provide annual historical coverage.

Think of it like organizing family photos: you keep every photo from this week (sons), one representative photo per week for the past month (fathers), and one special photo per month for the past year (grandfathers).

Beyond GFS

Modern variations include Tower of Hanoi schemes or custom policies like:

  • Keep dailies for 7 days
  • Keep weeklies for 1 month
  • Keep monthlies for 1 year
  • Keep yearly backups indefinitely (for compliance)

These policies automatically age out older backups, with retention windows expanding as data ages—high frequency for recent data, lower frequency for historical data.

Key Takeaway: Backup retention policies like grandfather-father-son provide structured rules for keeping recent backups at high granularity while retaining older backups at lower frequency, optimizing the tradeoff between recovery flexibility and storage costs.