Hosting · Explainer
Host Backups vs Your Own Backups: Why You Need Both
Short answer
Hosting with automatic daily backups means your host copies your WordPress files and database once a day without you doing anything. That copy is a useful safety net, but it usually stays on the host's own servers, has a short retention window, and can be hard to restore. Keep your own off-site backups too, so a host outage, a billing problem, or a bad restore never leaves you with nothing.
Key takeaways
- A host backup is a daily copy of your files and database, made by your hosting provider.
- Host backups often stay on the same servers as your live site, which limits their value in a real outage.
- WordPress.org advises keeping at least 3 to 5 recent backups in different locations.
- UpdraftPlus lets you schedule free backups every 2 hours, daily, weekly, or monthly.
- Jetpack VaultPress Backup adds real-time backups and one-click restores from the cloud.
- A backup you never test is only a guess, so restore one on a staging copy first.
What does hosting with automatic daily backups mean?
Hosting with automatic daily backups means your provider copies your site once every 24 hours without you starting the job.
The host runs the backup on its own schedule, usually overnight, and stores the copy on its systems. You do not install anything or click a button. The feature is part of the plan, and the exact details differ from host to host.
Some plans include daily backups for free, while others charge extra or back up less often. A2 Hosting's backup terms show how much the details can vary between plans, so read your own plan page before you rely on it.
What do host backups usually include?
A host backup usually includes your WordPress files and your database, which are the two parts a full restore needs.
WordPress.org's backup handbook states that a WordPress site has two parts to back up: the database and the files, and you need both to fully restore a typical site. The files hold your themes, plugins, uploads, and settings files, while the database holds your posts, pages, comments, and users.
Some hosts back up the whole server account, which also covers email and other files. Others back up only the website. Ask your host what is in the copy, because a backup that skips your uploads folder is not a full backup.
What do host backups leave out?
Host backups often leave out the things that matter most when something goes wrong.
Jetpack's VaultPress Backup page notes that host backups often run only once a day, stay on the same infrastructure as the live site, and are difficult to restore. If the server itself fails, the backup stored on that server can fail with it.
Host backups also rarely cover changes made between daily runs. A post published at noon and deleted by a bad plugin update at 3 p.m. may never appear in any host backup. That gap is why a daily copy alone is not enough for a busy site.
How long do hosts keep daily backups?
Hosts keep daily backups for a short window, often 7 to 30 days, and older copies are deleted on a rolling basis.
The exact window depends on the plan, and some hosts keep only the last few days on cheaper plans. Once a copy ages out, it is gone, so a problem you notice a month later may have no backup left to restore from.
WordPress.org's backup handbook advises keeping at least 3 to 5 recent backups, with copies stored in different locations, such as one on the hosting server, one on cloud storage, and one downloaded to your computer. A single rolling window on one server does not meet that advice.
Why is one backup copy not enough?
One backup copy is not enough because a backup can fail, get corrupted, or sit on the same server that just failed.
The classic rule is three copies, on two different kinds of storage, with one copy off-site. Your host backup can be copy one.
Your own plugin backup sent to cloud storage can be copy two. A downloaded copy on your own computer can be copy three. That spread means no single failure takes every copy at once.
This matters most when the problem is the host itself. If your account is suspended, the billing lapses, or the data center has an outage, you cannot reach a backup that only exists inside that host. An off-site copy keeps you in control.
How do you run your own WordPress backups?
You run your own WordPress backups with a backup plugin that schedules copies and sends them to storage you control.
UpdraftPlus is the most widely used free option. Its WordPress.org plugin page says it can back up on a schedule of every 2, 4, 8, or 12 hours, daily, weekly, fortnightly, or monthly.
It sends copies to Dropbox, Google Drive, Amazon S3, Rackspace, FTP, DreamObjects, OpenStack Swift, or email. It is installed on more than 3 million sites, according to the same page.
Jetpack VaultPress Backup takes a different approach. Its support docs say it makes a full backup at least once a day and adds real-time backups when you publish or update a post or page, change media, themes, plugins, settings, users, or comments.
The copies live in the Jetpack Cloud, not on your host, and you can restore with one click even if your site is offline. WooCommerce orders are stored in a way that keeps them safe even when you restore the rest of the store to an earlier point.
| Option | Frequency | Where copies live | Restore |
|---|---|---|---|
| Host daily backup | Once a day | Host's servers | Through host support or panel |
| UpdraftPlus (free) | Every 2 hours to monthly | Your cloud storage | From the WordPress dashboard |
| Jetpack VaultPress Backup | Daily plus real-time | Jetpack Cloud | One click, even if the site is down |
Pick the option that matches how often your site changes. A blog that posts weekly can live with daily backups, while a store that takes orders all day needs the real-time layer.
How often should you back up your own site?
Back up your own site as often as you can afford to lose work, and always before an update or a move.
WordPress.org's backup handbook gives a simple rule: smaller sites with few posts can back up once a week, while high-activity sites with many posts should back up daily. It also says to back up your database regularly and always before an upgrade.
In practice, that means daily database backups for most active sites and weekly file backups, since files change less often than content. The free version of UpdraftPlus covers scheduled backups, and its settings let you set separate schedules for files and database, which matches how the two parts actually change.
How do you check that a backup actually works?
You check a backup by restoring it somewhere safe and confirming the site loads and works.
A backup file that has never been restored is only a guess. Files can be incomplete, the database export can be cut off, or the storage destination can be full. None of that shows up until you try a restore.
The safe way to check is a staging copy. Restore the backup there, open the homepage and a few posts, log in to the dashboard, and submit a test form.
UpdraftPlus vs host backups compares restore paths, and the plugin route lets you restore single parts, such as only the database, without touching the live site.
What mistakes should you avoid?
The biggest mistake is assuming the host backup will save you, and never checking.
Do not store your only backup on the same server as your site. Do not set a schedule and forget the retention setting, or old copies will pile up until storage fills and new backups fail.
Do not skip the backup before a plugin update, a theme change, or a host move, because those are the moments most likely to break a site. A few minutes of backup time now can save hours of rebuilding later.
Bluehost's own migration guide makes the same point: back up your full website before migration so you have a recovery point if anything goes wrong, and keep your old hosting active until the moved site is tested. The same habit protects every other risky change too.
Frequently asked questions
Are my host's daily backups enough on their own?
Usually not. Host backups are a useful safety net, but they often stay on the host's own servers, cover only a short retention window, and can be slow or hard to restore. Keep at least one off-site copy you control, made by a backup plugin or service, so a host outage or billing problem never takes your only copy with it.
What is the difference between a host backup and a plugin backup?
A host backup is made by your hosting provider on its schedule and stored on its systems. A plugin backup is made by a tool like UpdraftPlus or Jetpack VaultPress Backup inside WordPress, on a schedule you choose, and sent to storage you control, such as Google Drive or the Jetpack Cloud. Plugin backups give you more control over timing, retention, and restores.
How many backups should I keep?
WordPress.org advises keeping at least 3 to 5 recent backups in different locations, for example one on your hosting server, one on cloud storage, and one downloaded to your computer. Keep daily copies for about two weeks, plus a weekly copy for a month, so you can reach back past a problem you notice late.
Do host backups cover my database too?
Most do, but you should confirm it. A full WordPress backup needs both the files and the database, and the database holds your posts, pages, comments, users, and settings. Ask your host whether the daily backup includes the database, how long copies are kept, and how a restore is started before you count on it.
Can I restore a backup if my host is down?
Only if a copy exists somewhere else. A backup stored on the same host is out of reach during an outage. Off-site backups, such as Jetpack VaultPress Backup copies in the Jetpack Cloud or UpdraftPlus copies on Google Drive, can be restored even when your host is down, which is the main reason to keep one.
Sources
- Backups - Advanced Administration Handbook WordPress Developer Resources
- UpdraftPlus: WP Backup & Migration Plugin WordPress.org
- Back up your site with Jetpack VaultPress Backup Jetpack
- VaultPress Backup: Real-Time WordPress Backups Jetpack
- How to Migrate a WordPress Site to Bluehost Bluehost
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
