Common Backup Failures

Common Backup Failures

Photo by Markus Spiske on Pexels

Having a backup system in place doesn't mean your backups actually work. In fact, the most dangerous situation in IT is believing your backups are fine when they're silently failing. Let's examine the most common ways backups fail — and how to prevent each one.

1. Silent Corruption (Bit Rot)

Backup files can become corrupted over time due to disk errors, controller faults, or bit-level degradation. The worst part? You won't know until you try to restore. Prevention:

• Use backup tools with built-in checksums (BorgBackup, Duplicati, Restic all do this automatically).
• Periodically verify backup integrity: borg check, duplicati verify, or restic check.
• Store backups on filesystems with data integrity checking like ZFS or Btrfs.

2. Running Out of Space

Backups grow. Without retention policies, your backup drive fills up, and new backups silently fail. This is one of the most common failures. Prevention:

• Set retention policies: keep 7 daily, 4 weekly, 12 monthly backups.
• Use deduplicating tools (Borg, Restic, Duplicati) to reduce storage by 80–90%.
• Monitor disk space with alerts (Nagios, Zabbix, or even a simple cron job checking df -h).

3. Backups That Can't Restore

A backup you can't restore is not a backup — it's a false sense of security. Common causes:

• Incomplete backups: The backup job was interrupted and never completed, but you didn't notice because there was no error notification.
• Wrong data: You backed up the wrong directory or excluded critical files.
• Format incompatibility: The backup software was upgraded and the new version can't read old archives.
• Missing credentials: The encryption key was stored on the same server that failed.

4. No Testing, Ever

The single biggest backup failure is never testing restores. A Sysadmin Survey found that 34% of businesses never test their backups, and of those that do, 77% find failures. You must test. We'll cover how in the Testing section.

5. Single Point of Failure

If your backup lives on a USB drive sitting next to the server, both can be destroyed in the same fire or stolen in the same break-in. This is not a backup strategy — it's a gamble.

6. Forgotten or Misconfigured Backups

Schedules break, passwords expire, services crash. If nobody monitors the backup system, failures go unnoticed for weeks or months. Set up email notifications on both success and failure.

Key Takeaways

• Silent corruption, space exhaustion, and untested restores are the top three backup killers.
• Always use checksums and deduplication to combat corruption and storage growth.
• Monitor backup jobs and alert on failure — silence is not success.
• Never store your backup next to the original — that's a copy, not a backup.