Website backups: how to protect your site with the 3-2-1 rule

What a reliable website backup looks like, how often to back up, where to store copies and why testing restores matters most.

By the UK Technology Hub teamPublished 4 minute read

The short answer

A reliable backup strategy keeps at least three copies of your website, on two different types of storage, with one copy off-site, which is the 3-2-1 rule. Back up both files and database, as often as your site changes, keep several older versions, and regularly test that backups can actually be restored. An untested backup is a hope, not a plan.

Websites break for many reasons: a failed update, a hacked plugin, a hosting problem, an accidental deletion or a mistake by a well-meaning team member. When it happens, a good backup turns a disaster into a minor inconvenience. Without one, you may have to rebuild from scratch.

What needs backing up?

Most websites have two parts:

  • Files: the platform, theme, plugins, uploaded images and documents.
  • Database: pages, posts, products, orders, customers, settings and form entries.

Both are needed to restore a working site. A backup of only the files, or only the database, may not be enough.

For hosted platforms like Shopify or Webflow, the platform handles infrastructure backups, but you may still want copies of your own content, such as product exports or page backups, and some platforms offer apps or features for this.

The 3-2-1 rule

This widely used principle keeps you safe from most scenarios:

  • 3 copies of your data: the live site and at least two backups.
  • 2 different types of storage, such as your host's backups and a separate cloud storage service.
  • 1 copy off-site, stored with a different provider from your hosting.

Why off-site? If your hosting account is compromised, suspended or suffers a major failure, backups stored in the same place may be lost too.

How often to back up

Match frequency to how often your site changes:

Type of siteSuggested frequency
Brochure site updated occasionallyDaily, plus before any changes
Blog or news siteDaily
Online shop or booking siteSeveral times a day, or real-time for the database
Web apps with constant user activityContinuous or very frequent database backups

Always take a fresh backup before updates, redesigns or major content changes.

How long to keep backups

Keep several versions going back in time, such as daily backups for a few weeks and monthly backups for longer. Some problems, like a hidden malware infection, aren't discovered immediately. If you only keep yesterday's backup, it may already contain the problem.

Balance this with data protection: backups containing personal data are covered by UK GDPR, so set sensible retention periods and protect backups as carefully as the live site.

Test your restores

This is the most overlooked step. Many businesses discover their backups are incomplete, corrupted or impossible to restore only when they need them. At least every few months:

  1. Restore a backup to a staging environment.
  2. Check that pages, images, forms and key features work.
  3. Note how long the restore took.
  4. Fix any problems with the backup process.

Secure your backups

  • Encrypt backups, especially if they contain customer data.
  • Restrict who can access backup storage.
  • Use two-factor authentication on backup and storage accounts.
  • Make sure backups can't be deleted by someone who compromises your website, for example by using separate credentials.

Backups and ransomware

Ransomware attacks encrypt or delete data and demand payment. Off-site, protected backups with several historic versions mean you can restore without paying. The National Cyber Security Centre publishes guidance on backups as part of its advice for small businesses.

What to do when you need to restore

  1. Stay calm and stop changes to the site.
  2. Work out what went wrong, if possible, so you don't restore the same problem.
  3. Choose the right backup, from before the problem started.
  4. Restore to staging first if time allows.
  5. Restore the live site and test thoroughly.
  6. Fix the root cause, such as updating a vulnerable plugin or changing passwords. Our website security checklist lists what to check.
  7. Check for lost data, such as orders or form entries received since the backup.

Online shops need extra care

For online shops, restoring an older database could lose recent orders and customer accounts. Frequent database backups and a plan for reconciling orders are essential. Our e-commerce builds include backup planning suited to order volumes.

Who should manage backups?

Backups should be someone's clear responsibility, with monitoring that alerts if a backup fails. Hosting providers often include backups, but check what's covered, how long they're kept and how restores work. Our guide to WordPress maintenance shows where backups fit into a wider routine.

How we can help

Our maintenance and support plans include automatic off-site backups, monitoring, retention and restore testing. Sites built through our web development service come with backup arrangements agreed before launch.

Frequently asked questions

Does my hosting company back up my website?

Many do, but check how often, how long backups are kept and whether you can restore them easily. Keep your own off-site copy too.

How long does it take to restore a website?

From minutes to a few hours, depending on the site's size, backup method and whether issues need fixing first.

Are backups covered by GDPR?

Yes. Backups containing personal data must be protected and kept only as long as necessary.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All SEO, security & maintenance guides