Backup

What to Do When Your Backup Fails

A failed backup alert is stressful — but it doesn't always mean your data is at risk. Here's how to respond to a backup failure and what to check first.

Backup failure alerts are alarming — but many failures are temporary issues that resolve on their own. The key is knowing which failures need immediate action and which just need monitoring. Here's how to respond.

Common Backup Failure Causes

  • Insufficient storage space: the backup destination is full — free up space or expand storage
  • Network connectivity interruption: the backup job couldn't reach the destination — check connectivity and retry
  • Changed credentials: a password was rotated without updating the backup software
  • Open files: some backup tools can't back up files that are actively open — use a VSS-aware backup solution
  • Corrupted backup catalog: the backup index needs rebuilding — consult your backup vendor documentation
  • Destination unavailable: the NAS, external drive, or cloud account is offline or inaccessible

Immediate Response Steps

  1. Note the exact error message from the backup job log
  2. Check whether yesterday's backup completed successfully
  3. Attempt a manual backup run and observe the result
  4. Verify the backup destination has sufficient free space
  5. Check network connectivity to the backup destination
  6. Review recent changes — password rotations, server updates, storage changes
  7. If data is at risk: do not make further changes to the source until the issue is resolved

When to Call for Help

If you can't identify and resolve the backup failure within 30–60 minutes, call your IT provider. More than 24 hours of backup failure without active investigation is a serious risk — if something goes wrong with your data during that window, you may not have a valid recovery point.