- Backup plugins can fail silently without notifying you.
- Backups should be stored away from the server they protect.
- A backup is only valid if a restore from it has actually been tested.
- G7Cloud restore-tests every backup nightly — a real restore into a sandbox, automatically.
Why Most Backup Strategies Fail
The most common WordPress backup strategy is: install a backup plugin, configure it to run daily, and forget about it. This approach has three critical problems.
First, backup plugins can fail silently. The plugin might encounter a timeout, run out of memory, or hit a file permission error — and you'd never know until you need to restore. Second, backups stored on the same server as your site are useless if the server fails. Third, most site owners never test their backups, so they have no idea whether they'll actually work when needed.
What a Reliable Backup System Looks Like
A reliable backup system has four characteristics: it runs automatically without human intervention, it keeps copies away from the server it protects, it verifies that backups can actually be restored, and it makes restoring granular and simple.
On G7Cloud, backups run on schedules you choose — daily, weekly or monthly — plus manual snapshots before risky changes. Incremental backups keep storage lean, and you can send copies to your own off-site target: an S3 bucket, Cloudflare R2, or any SFTP server you control.
Restores are granular: bring back the full site, a single file, or a single database — so recovering one corrupted upload never means rolling back a whole day of orders.
Backup Retention and Recovery Points
How far back should your backups go? For most business sites, 30 days of daily backups provides adequate coverage. This gives you enough recovery points to handle most scenarios — from accidental deletions to malware infections that went undetected for several days.
For e-commerce sites processing orders, more frequent backups and database-level restore points matter more, because rolling back a whole day means losing a whole day of orders.
Testing Your Backups
A backup you haven't tested is a backup you can't trust. The uncomfortable truth of the industry is that almost nobody — hosts included — routinely tests restores. Backup jobs report 'success' because a file was written, not because that file can actually bring a site back.
Restore-tested nightly
G7Cloud restore-tests every backup automatically, every night: a real restore into an isolated sandbox, verified. If a backup can't actually be restored, we know that night — not on the day you need it.
Whatever host you use, apply the same standard: ask not "are there backups?" but "when was the last successful test restore?" If the answer is a shrug, you don't have backups. You have hope.
About G7Cloud Engineering
Articles written by the engineers who build and run G7Cloud — UK managed hosting and the AI Website Builder. We write about what we operate every day: containers, backups, databases, and the small-business websites that run on them.
More about G7Cloud →