What?

While evaluating the Grandfather-Father-Son (GFS) backup system, I learned how it reduces storage needs by rotating daily, weekly, and monthly backups. However, one detail stood out: if even one daily (incremental) backup in the chain is corrupted, the entire restoration process can fail. That risk made me look at backup strategies in a new light.

So what?

I’ve always seen backing up as a safety net—something you do to avoid problems if data is lost. But I hadn’t seriously considered what happens if the backup itself is faulty. I now realise that the process of backing up requires just as much care and planning as any other part of the data pipeline. It’s not enough to just “have a backup”; the method, integrity, and recovery process all matter. Backup isn’t a simple checkbox, it’s a critical design decision that needs thoughtful execution.

Now what?

In my role, I’m often responsible for setting up basic data infrastructure. Until now, I treated backups as a side task—simple file copies or snapshots. Going forward, I’ll approach backup planning as a core part of data architecture. I’ll explore different backup strategies, including rotation systems like GFS, and evaluate them based on not just storage efficiency, but recoverability, resilience, and long-term reliability.

References

• Gibraltar Solutions. (2023). Mastering the Art of Modern Data Backup Strategies. Available at: https://gibraltarsolutions.com/blog/mastering-the-art-of-modern-data-backup-strategies/
• Rolfe, G., Freshwater, D., & Jasper, M. (2001). Critical reflection for nursing and the helping professions: a user’s guide. Basingstoke: Palgrave Macmillan.