Case 19 · Backup & recovery
Is Your Website Backup Actually Working? Verifying Backup Reliability
Short answer
A backup only counts if it can be restored. To verify WordPress backups, confirm they run on schedule, include both the database and all files, are stored off-site, are kept long enough, and, most importantly, restore successfully to a test site. Check this regularly, not just once.
The challenge
This is a typical scenario based on the kinds of challenges WordPress site owners bring to us. Names and details are illustrative.
A consultancy has used the same backup plugin for three years, and the dashboard shows a green “Last backup: successful” every day. When a faulty update corrupts the site and a restore is needed, the newest backup archive is only 40 MB, for a site with several gigabytes of PDFs and images.
The backups had been running successfully, but months earlier, the plugin’s settings were changed to exclude the uploads folder because backups kept timing out. Every backup since then contained the database and code, but none of the files.
Warning signs to look for
- The backup plugin shows a success message, but nobody has ever restored a backup.
- Backup files are unusually small compared with the size of the site.
- The last successful backup is older than expected.
- Backup emails or notifications stopped arriving.
- Backups are stored only on the same server as the site.
Common causes
- Silent failures
- Backups time out or run out of disk space on large sites, but the failure is only shown in a log nobody reads.
- Incomplete backups
- Some plugins back up only the database, or exclude the uploads folder to save space, so images are missing.
- Storage problems
- Cloud storage connections expire, quotas fill up or access keys change, and new backups stop being saved.
- Never tested
- Backup archives can be corrupted or incompatible with the current server, which only shows up during a restore.
What it costs your business
A failed backup is discovered at the worst possible moment: during an emergency. The business then faces the full cost of downtime and rebuilding, despite believing it was protected.
Our approach
- 1
Check the schedule and history
We review backup logs to confirm backups run on time and look for gaps or failures.
- 2
Check completeness
We confirm each backup contains the database and all files, including uploads, themes, plugins and configuration, and compare sizes with the live site.
- 3
Check storage and retention
We confirm backups reach off-site storage, that the connection is healthy, and that enough history is kept.
- 4
Run a test restore
We restore a recent backup to a staging environment and click through key pages, forms and admin functions.
- 5
Fix and document
Any problems are fixed, and the result of the test restore is recorded, so you know how long a real recovery would take.
Services delivered
WordPress Maintenance
- Backup success is checked regularly, not assumed.
- Failed backups are investigated and fixed promptly.
- Periodic test restores confirm backups actually work.
- Backup health is part of the monthly report.
The outcome
The database restore works, and most files are recovered from an older archive and the hosting snapshot. But the team learns the key lesson: a green tick is not proof. The site now has complete off-site backups, alerts for failures, and a scheduled test restore every quarter.
How to prevent it happening again
- Make test restores a routine, at least every few months.
- Get alerts for failed backups, not only successful ones.
- Store backups in two places, one of them off-site.
- Recheck the backup setup after hosting moves or large site changes.