Guides

Backup & Recovery

What If Your Website Goes Down? A Backup Plan Anyone Can Follow

Last week a small business owner I know had their website vanish. Not hacked — just an accidental delete during a routine update. Two years of content, product pages, and customer reviews. Gone. They had no backup. This guide is what I wish they'd read the day before it happened.

Published 26 June 2026 · Practical guide

The 3-2-1 rule — the only backup rule you need to know

Every backup plan starts and ends with one principle. It's called the 3-2-1 rule, and if you remember nothing else from this guide, remember this:

  • 3 copies of your data — the live one plus two backups
  • 2 different types of storage — so one type of failure doesn't wipe everything (think: hard drive failure shouldn't also kill your backup drive)
  • 1 copy off-site — physically somewhere else. If your office floods, your backup drive on the same desk goes under too.

For a small business website, that usually means: the live site on your web host, a recent backup on a different machine (your office NAS or a spare computer), and an automated off-site copy in cloud storage or a remote server. Three copies, two media types, one off-site.

It sounds simple because it is. The hard part isn't understanding it — it's actually doing it.

What actually needs backing up

A website isn't one file. It's three things, and you need all three:

1. The database

Every WordPress site, online shop, or web app stores its content in a database. Your pages, posts, products, orders, settings — all of it lives in the database, not in files. Lose the database and you lose everything you ever wrote or sold. The database is a single file when exported (a .sql dump), typically 5–100 MB for a small business site. Back it up daily.

2. The files

This is your wp-content folder: every image you've uploaded, every plugin, every theme file, every PDF. It's usually much larger than the database — anywhere from 100 MB to several GB if you have lots of product images. Files change less often than the database (you upload a new image once, not daily), so weekly file backups are usually enough.

3. The configuration

The wp-config.php file, your .htaccess, any custom nginx or Apache settings. These are tiny — a few kilobytes — but they're the glue that connects your site to its database. Without them your backup is a pile of files and a database that don't know how to talk to each other. Back them up whenever they change (which is almost never after initial setup).

Option 1: Plugin backup — simplest, good enough for most

If you run WordPress and you just want something that works, start here. Install a backup plugin, set it to run automatically, and connect it to an off-site destination.

UpdraftPlus is the most popular for a reason. The free version backs up your database, plugins, themes, and uploads, and sends them to Google Drive, Dropbox, or a dozen other cloud destinations. Set it to run daily, point it at your Google Drive, and you've got 3-2-1 coverage in about ten minutes of setup.

All-in-One WP Migration is another good option, especially for full-site exports. It bundles everything — database, files, config — into a single .wpress file you can import on any fresh WordPress install. Useful for migrations, but also works as a periodic safety net.

The plugin approach covers 90% of small business websites. It's set-and-forget, runs automatically, and costs nothing. The only real risk is that you're relying on a plugin to keep working — if the plugin breaks during a WordPress update and you don't notice, you're backing up nothing for months. Which brings us to testing (see below).

Option 2: Host backups — what your hosting company actually does

Most shared hosts and managed WordPress hosts advertise "daily backups included." Here's what that usually means in practice:

  • They back up the whole server, not your individual site. Restoring is an all-or-nothing affair — they roll back the entire server to the backup snapshot, affecting every site on that machine.
  • Backups are on the same infrastructure. If the hosting company has a catastrophic failure (fire, ransomware, bankruptcy), your "backup" dies with your site.
  • Restores cost money or take days. Some hosts charge for restores. Most take 24–48 hours. When your site is down and customers can't reach you, that's an eternity.

Host backups are better than nothing. They'll save you from a plugin update gone wrong. But they are not a proper backup strategy — they're a safety net with holes in it. Treat them as one of your three copies, not all of them.

Option 3: The professional way — you control everything

If your website is your business (an online shop, a booking system, a membership site), you want more control than a plugin or a host provides. Here's what a professional backup setup looks like:

The database: mysqldump

mysqldump is a command-line tool that exports your entire database to a single .sql file. It runs on any Linux server, takes seconds for most small sites, and produces a file you can restore anywhere:

mysqldump -u username -p database_name > backup_$(date +%Y%m%d).sql

Run this daily via a cron job, compress the output with gzip, and you've got a tiny, portable, complete database snapshot.

The files: tar

tar bundles your entire wp-content folder into one archive:

tar -czf files_$(date +%Y%m%d).tar.gz /path/to/wp-content/

This gives you a compressed archive of every image, theme, and plugin. Run it weekly, or daily if content changes often.

Off-site: pull, don't push

Here's the pattern that changes everything: pull your backups from the outside, don't push them from the inside. If your web server is compromised, a hacker can delete your pushed backups. But they can't touch a separate machine that reaches in and pulls the data.

This is called the DMZ pull model: a separate server (like a NAS on your office network, or a cheap Linux VPS) connects to your web server, downloads the latest backup files, and stores them locally. The web server never initiates the connection — it just holds the files and waits to be asked.

Once the backups are on your office machine, that machine backs itself up to something off-site — cloud storage, a remote server, or even an external hard drive you swap weekly and keep at home. Now you've got 3-2-1 fully covered, and no single point of failure can wipe everything.

Off-site storage — why "not on the same computer" matters

I use TrueNAS for this — a dedicated storage server that holds snapshots of everything. Snapshots are point-in-time copies: they capture the exact state of every file at a specific moment, and they take almost no extra space because they only store what changed since the last snapshot.

The snapshot schedule that works well for a small business:

  • Hourly snapshots kept for 24 hours — catch the "I accidentally deleted a page an hour ago" problem
  • Daily snapshots kept for 2 weeks — catch the "that plugin update broke everything three days ago" problem
  • Weekly snapshots kept for 2 months — catch the "we only just noticed that bug from last month" problem

You don't need TrueNAS specifically. An external hard drive with Time Machine or Windows File History, a Synology NAS, Backblaze, or even a second web hosting account used purely for backup storage — anything that isn't on the same physical machine as your live site qualifies as off-site.

Testing your backup — the step everyone skips

A backup you haven't tested is a backup you don't have. I've seen it too many times: someone has been running daily backups for two years, their site goes down, and the backup file turns out to be corrupted, incomplete, or pointing at a database that was deleted six months ago.

Test your backup at least once every three months. Here's what a basic test looks like:

  1. Take your most recent backup file
  2. Restore it to a temporary location — a subdomain like test.yoursite.co.uk or a local WordPress install on your computer
  3. Open the restored site and check: do the pages load? Are the images there? Can you log in?
  4. If yes: your backup works. If no: fix whatever's broken before you need it for real.

This takes 30 minutes, four times a year. That's two hours annually to know — not hope, know — that you can recover your business website.

The recovery plan — when it actually goes down

When your site goes down, panic is the enemy. Have a written recovery plan — even a one-page document — that tells you (or whoever is holding the phone) exactly what to do:

  1. Don't touch anything on the live server. If it's hacked, you might overwrite forensic evidence. If it's a server fault, you might make it worse.
  2. Get your most recent verified backup. The one you tested last quarter and know works.
  3. Set up a fresh WordPress install on a new server or a clean subdomain. Don't try to fix the broken one — start clean.
  4. Import the database with mysql -u user -p dbname < backup.sql
  5. Restore the files — extract your wp-content archive into the new install
  6. Copy your config — wp-config.php with the correct database credentials
  7. Test everything. Homepage, contact form, checkout. Log in to the admin panel.
  8. Update DNS to point your domain at the new server. Propagation takes minutes to hours.

The whole process should take under 30 minutes if your backups are current and you've practised it before. The goal isn't zero downtime — that costs real money — it's predictable downtime. You know exactly how long recovery takes because you've timed it.

What Vengera does — our actual backup stack

This isn't theory. Here's the backup setup that protects this very website:

Layer 1: Daily automated WordPress backups

Every 24 hours, a full site export runs automatically — all files, database, and configuration, compressed into a single archive.

Layer 2: Pulled to a separate machine

A monitoring server on a completely different network reaches in and downloads the latest backup. The web server never pushes anything outbound — even if the site is fully compromised, the attacker can't reach the backup machine.

Layer 3: TrueNAS with snapshot rotation

The pulled backups land on a TrueNAS storage server with hourly, daily, and weekly snapshots. Snapshots are immutable: once taken, they can't be modified by anything short of physical access to the machine. Ransomware that encrypts the live files can't touch the snapshots.

Layer 4: Off-site replication

Critical snapshots are replicated off-site. Even if the office burns down, the website can be restored from the off-site copy.

Verification

Every backup is checked for integrity — if the archive is corrupted or incomplete, the monitoring system alerts within minutes. A full restore drill is run quarterly.

This is the setup behind a site that scores Lighthouse 100/100/100/100 and handles every visitor enquiry. The performance and the backup discipline are two sides of the same coin: both come from treating the website as business infrastructure, not a hobby project.

Want your website backed up properly?

I can set up automated backups for your WordPress site, WooCommerce shop, or custom web app — with off-site storage, snapshot rotation, and verified restores. One-off setup or ongoing management, explained in plain English.

Get a free backup check Back to guides