A backup only matters if it restores.

Inventory what must be rebuilt

Files alone are not always enough. Include databases, configuration, recovery secrets, encryption keys and deployment procedures. Define acceptable loss, retention and recovery time for each dataset.

Separate protection mechanisms

A snapshot enables point-in-time rollback but may share storage and credentials with the source. Replication speeds recovery but can propagate deletion or corruption. Backups preserve independent recovery points according to a retention policy.

• The 3-2-1 rule suggests three copies across two distinct media or systems, with one off-site.
• An immutable or offline copy reduces some malicious deletion risks.
• Separate administrative identities limit the impact of compromise.

Check consistency and capacity

An active database needs an engine-aware backup mechanism: export, native backup or application coordination. Size storage, networking and backup windows, but also the capacity required for full recovery. Protect keys without making them inaccessible during a crisis.

Restore regularly

A successful backup job is an initial signal, not proof of recoverability. Restore into an isolated environment, check data and business workflows, and measure elapsed time. Test historical recovery points: late-discovered corruption may already affect recent copies.