---
title: "Comment by Azhar Abbas on \"Backups aren't simple\" | Hashnode"
description: "The distinction between mirroring and keeping recoverable history is especially useful. I would add a recovery-time objective alongside RPO: a weekly copy may m"
url: "https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c/comment/6af70fdbcc91786c56693160"
---

[Discussion](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c)

Comment [Backups aren't simple](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c)

[Azhar Abbas](https://hashnode.com/@azharabbas)

[8h ago](https://hashnode.com/posts/backups-arent-simple/6af6d3f1856174f724934b0c/comment/6af70fdbcc91786c56693160)

The distinction between mirroring and keeping recoverable history is especially useful. I would add a recovery-time objective alongside RPO: a weekly copy may meet the data-loss target but still take days to download and restore. A practical drill is to restore a small service onto a clean machine using only the offsite copy and the documented recovery steps, then time it and check that the application actually works. That also exposes missing encryption keys or credentials that were stored only on the failed machine. Backup-success logs and repository checks are valuable, but neither alone proves that recovery is possible.