Are Host Backups Enough?
What Host Backups Usually Cover
Are hosting backups enough? They are often a useful first layer of protection, but on their own they are rarely enough. A host backup is a copy of your account that the hosting company makes and stores as part of the service, usually covering your site's files and databases.
Host backups are usually designed around the provider's infrastructure rather than your recovery needs, so their scope, timing and retention may not match what you require. Read the provider's documentation to see exactly what is included.
The Limits of a Host Backup
- Same infrastructure. Copies may be stored on the same servers, in the same data center or within the same company as the site. A serious outage or account problem can affect the live site and its backups together.
- Short retention. Many plans keep a limited number of restore points, often covering days or weeks. If a problem is noticed late, the good copies may already have been overwritten.
- No guaranteed outcome. Terms of service often limit what the provider promises, and a restore is not always guaranteed to succeed or to finish quickly.
- Restore effort. Some restores need a support request, extra waiting time or additional fees, which matters when a site is down.
- Partial coverage. Email, custom server settings or DNS records may be excluded, so a restore can be incomplete. See what a complete backup should include.
Ask what happens to your backups if an account is suspended or closed. Those are situations where copies are often needed most, so it is worth knowing before a problem whether they are kept, for how long, and who can reach them.
Each limit is manageable on its own. Together they mean the host's backup is a convenience, not a complete plan.
A Hack Found Too Late
A small business site is hacked, and malicious code is added to its pages. The host keeps seven days of backups. The owner does not notice the changes for ten days, by which time every stored copy already contains the malicious code.
Had the owner kept a separate copy from before the attack, the site could have been restored to a clean state. The gap between the host's retention and the time the problem was found decided the outcome.
Why Owners Keep Their Own Copies
Keeping your own copy gives you control over timing, location, retention and format. You decide how often copies are made, how long they are kept and where they are stored, rather than relying on someone else's settings.
A practical approach is to use the host's backups as a quick undo and to keep a separate copy stored somewhere independent of the host, in line with the 3-2-1 rule and off-site storage. A copy you hold independently also gives you a way to rebuild the site elsewhere.
Frequently asked questions
Should I Stop Using Host Backups If I Make My Own?
No. Host backups are a useful extra layer, and they can speed up quick fixes such as undoing a bad update. Keep them alongside your own separate copy rather than in place of it.
How Can I Check What My Host's Backups Include?
Read the hosting provider's documentation or ask support in writing. Check whether files, databases, email and server settings are covered, how many restore points are kept, how far back they go, and whether you can restore yourself or must ask support.