The 3-2-1 Backup Rule for Websites (and How to Test a Restore)
Backups you have never restored are not backups. A pragmatic backup policy for WordPress, WHMCS and custom applications.

Every serious outage we have handled had the same root cause pattern: the backup existed, but nobody had ever restored it.
The rule
3 copies of your data, on 2 different media or platforms, with 1 copy off-site. For a website that usually means the live server, the host's automated snapshot, and a remote copy in object storage you control.
What to back up
- Application files and uploads
- The database β dumped consistently, not copied while writing
- Email mailboxes (often forgotten) β see email migration & backup
- DNS zone exports and SSL private keys
Retention
Daily for 14 days, weekly for 8 weeks, monthly for a year. Ransomware and defacements are often discovered weeks later, so a single overnight copy is not enough.
Test the restore
Quarterly, restore to a staging subdomain and actually click through checkout or login. Time it, and write the recovery time down β that number is your real RTO. Our cPanel plans include JetBackup restores you can run yourself.
Harden alongside
Backups do not replace patching, 2FA and least-privilege accounts. The OWASP Top 10 remains the best checklist for application risk, and TLS everywhere is table stakes.
Need managed backups with off-site retention? Talk to us about managed VPS.
Share this article
Was this article helpful?
Your vote helps us write better guides.
