Backups
Beginner
Backup best practices for web hosting
How often to back up, what to include, where to store copies, and how to test restores. The 3-2-1 backup rule applied to web hosting.
UnderHost NOC
Network Operations
On this page
A good backup strategy follows the 3-2-1 rule: 3 copies of your data, on 2 different media, with 1 copy off-site. Applied to web hosting, this means: the live server, a local computer backup, and a cloud storage copy.
The 3-2-1 rule for web hosting
| Copy | Where | Example |
|---|---|---|
| 1st (live) | Your hosting server | cPanel / VPS files and databases |
| 2nd | Local computer or NAS | Downloaded cPanel backup or rsync copy |
| 3rd (off-site) | Cloud storage | Backblaze B2, Amazon S3, Google Drive |
How often to back up
| Site type | Recommended frequency |
|---|---|
| Static / rarely updated | Monthly or after each update |
| Blog or informational site | Weekly |
| WordPress with regular posts/comments | Daily |
| E-commerce / orders placed daily | Multiple times per day (database at least hourly) |
What to include
- All website files-public_html and any application files
- All databases-especially critical for WordPress, WooCommerce, or any CMS
- Email-if you store important business email on the server
- DNS zones-useful if you ever need to migrate servers
- SSL certificates-only if using custom/paid certs; Let's Encrypt certs are auto-renewed
Test your restores
A backup you've never tested is an unknown. Periodically (at least quarterly):
- Take a fresh backup
- Restore it to a staging environment or test subdomain
- Verify the site works correctly from the restored copy
This confirms the backup is complete and uncorrupted, and that you know the restore process before an emergency.
Always back up before major changes
Before any of the following, take a fresh backup:
- WordPress core, plugin, or theme updates
- PHP version changes
- Site s or DNS changes
- Custom code deployments
- Database schema changes
Was this article helpful?
Implement backup strategy now
Don't wait for a disaster. Set up automated backups following the 3-2-1 rule.
