Do You Actually Have a Backup? (Most Business Owners Don't Know)

Most small business owners assume their website is being backed up somewhere. Many are wrong. Here's how to find out — and what to do about it before something goes wrong.

Here's a question worth sitting with for a moment: if your website disappeared completely right now — every page, every image, every product listing, every contact form submission — how long would it take you to get it back?

Most small business owners assume the answer is "not long, my hosting company backs things up." Some of those people are right. A lot of them are not, and they find out the hard way.

The Difference Between Having a Backup and Having a Useful Backup

There's a gap between "my host takes backups" and "I can actually restore my site from a backup." That gap has caught a lot of business owners off guard.

Hosting company backups, when they exist at all, vary wildly. Some hosts keep daily backups for 30 days and let you restore with one click. Others keep weekly snapshots for seven days. Some keep backups but charge a significant fee to restore from them. Some include backups only on higher-tier plans and you're on a basic plan you set up three years ago. A few hosts advertise backups in their marketing and deliver something that turns out to be unreliable or difficult to actually use.

The only way to know which situation you're in is to check — not assume.

What a Backup Actually Needs to Include

A complete website backup has two parts, and you need both:

  • The files — all of your website's code, themes, plugins, uploaded images, and documents. This is what lives on your web server.
  • The database — where your actual content lives. Every page, every blog post, every product, every form submission, every customer record. For most websites, especially WordPress sites, the database is the irreplaceable part.

A backup that only includes files but not the database would restore your site's structure but leave it empty. A backup that only includes the database but not the files might not be usable at all without the correct version of the software to go with it. You need both.

Three Questions to Ask Right Now

You don't need to be a technical person to get clear answers on your backup situation. These are reasonable questions to ask your hosting company or your web developer:

  1. Are automatic backups included in my current plan? Not a plan I could upgrade to — the one I'm on now.
  2. How often are backups taken, and how far back do they go? Daily backups kept for 30 days is a reasonable baseline. Weekly backups kept for one week is much less useful.
  3. If I needed to restore my site to yesterday's version, what would that process look like and what would it cost? The answer should be simple. If it isn't, that's useful information.

Why "Yesterday" Matters More Than You Think

Backups aren't just for catastrophic failures. They're also your safety net when:

  • A plugin update breaks your site in a way you can't easily undo
  • Someone with admin access accidentally deletes content
  • Your site gets infected with malware and you need a clean version to restore from
  • A bad database migration wipes or corrupts your data

In the case of malware, this last point matters especially: if your most recent backup is also infected, restoring from it just puts you back where you started. You want enough backup history to go back to before the infection happened — which is another reason daily backups kept for at least two weeks are worth having.

What to Do If You Don't Have a Solid Backup

The good news is that this is a solvable problem. Most WordPress sites can be set up with reliable automated backups — files and database, daily, stored somewhere separate from your server — without a lot of effort or expense. The important thing is getting it done before you need it. Backups you set up after a crisis don't help you with the crisis you're already in.

If you're not sure what your current backup situation looks like, we're happy to check and let you know what we find.