Backups Are a Hosting Feature, Not an Afterthought
The difference between a good host and a risky one often appears when you need to restore. Here's how to evaluate backup quality before you need it.
Backups Decide How Bad a Bad Day Gets
Every site eventually has a bad day: a plugin update fails, a developer deletes the wrong file, malware changes content, a database table corrupts, or a migration goes sideways.
The question is not whether problems happen. The question is how quickly you can restore.
Included Does Not Mean Useful
Some hosts advertise backups but make restores slow, limited, or ticket-only. Others keep backups on the same server, which is better than nothing but weak against server-level failure.
A useful backup system is automatic, frequent, restorable by the customer (not by support ticket), and separate enough from the live site to survive common incidents.
When we review hosts, we check:
- Frequency: Daily? Hourly? On-demand?
- Retention: How many restore points are kept?
- Restore process: Self-service or ticket-only?
- Storage location: Same server, same datacenter, or off-site?
- Included or add-on: Does the headline price include backups?
[Hostwinds](/reviews/hostwinds) includes nightly backups at no extra cost — genuine value. [Cloudways](/reviews/cloudways) includes automated backups with configurable frequency. [SiteGround](/reviews/siteground) includes daily backups with 30-day retention. Budget hosts often charge extra or offer minimal backup coverage.
Restore Testing
A backup that has never been restored is a hope, not a guarantee. Good hosts make restore testing safe and simple, ideally into staging rather than production.
For business sites, test restores periodically — at least quarterly. You don't want the first restore attempt to happen during an outage at 2am. See our [Backup Strategies guide](/guides/backup-strategies) for detailed testing workflows.
Retention Depends on the Site
Retention matters. Daily backups kept for two days may not help if malware went unnoticed for a week. Monthly backups may miss recent orders or content changes.
The right retention depends on the site:
- Brochure sites: 7 daily backups, 1-2 monthly archives
- E-commerce: 30 daily backups, 12 monthly archives
- Content/editorial: 14 daily backups, weekly archives for 3 months
Off-Host Copies
For important sites, keep at least one backup outside the hosting provider. Provider-level outages, billing mistakes, account compromise, and control panel failures can all make internal backups unavailable.
Options:
- R2/S3 automated sync — Scripted backup pushes to object storage
- WordPress backup plugins to remote — UpdraftPlus to Google Drive, BackWPup to S3
- Server-level rsync/rclone — Push
/var/backups/to a separate provider's storage
Off-host backups are cheap compared with rebuilding a site from scratch. The [OVHcloud Strasbourg fire in 2021](/reviews/ovhcloud) was a brutal reminder: customers with off-site backups recovered in hours. Customers relying on same-datacenter backups lost everything.
Verdict
Judge hosts partly by restore quality. Backups are not a checkbox; they're the recovery plan. A host with self-service restores, adequate retention, and off-server storage is worth more than a host with faster CPUs and weak backup coverage.
For specific recommendations, see our [Backup Strategies guide](/guides/backup-strategies) and [Hosting Speed Testing guide](/guides/hosting-speed-testing) for how we test restore performance.