Website Backups Done Right: The 3-2-1 Rule for Businesses

By · 10 November 2026 · 4 min read

Illustration of three copies of website data: the main server, a second storage system and an offsite copy

Almost every hosting provider says your website is "backed up". But the more important questions rarely get asked: where is that backup kept, who can delete it, and when was it last actually restored?

You only feel the value of a backup when something goes wrong: the website is hacked, data is deleted by accident or a server fails. That is when many companies find out their backup went down with everything else, stopped running long ago, or can't be used. This article explains the 3-2-1 rule, how to apply it to a company website, and how to make sure your backups can really be relied on.

What is the 3-2-1 rule?

The 3-2-1 rule is a backup guideline described by CISA, the US cybersecurity agency, in its paper on data backup options:

  • 3 copies of any important data: one primary and two backups.
  • 2 different types of storage media, so one kind of failure can't wipe out everything.
  • 1 copy stored offsite, for example outside your office or business premises.

The rule was first written for files on office computers and servers. But the logic is exactly the same for a website: never let a single event wipe out the primary data and all its backups at once.

What needs backing up on a website?

A website is more than the pages visitors see. WordPress's documentation, for example, splits a site into two parts that both need backing up:

  • Files: the CMS, plugins, themes, uploaded images and documents, and other code and settings files.
  • Database: page content, articles, product data, user accounts and messages sent through forms.

A backup with files but no database, or the other way round, isn't enough to bring the website back as it was. Make sure both are on the schedule, whatever platform your website runs on.

Applying 3-2-1 to a company website

  1. The first copy is the live website.
  2. The second copy can be the host's automatic backup. It is the quickest to use for small mistakes.
  3. The third copy is kept away from your hosting provider, for example in a separate cloud storage service or on storage media your office owns.

For a website, "two different media" is best read as two separate storage systems, not two folders on the same server. WordPress's documentation gives a similar example: one copy on the hosting server, one in cloud storage and one on a local computer.

If your hosting or website provider handles backups, ask them these four questions:

  • Do the backups include both files and the database?
  • Where are the copies stored, and is any of them away from the website's server?
  • How many versions are kept, and how far back do they go?
  • If we ask for the website to be restored, how long does it take and who does it?

Why backups on the same server aren't enough

If every backup sits on the same server or hosting account, one problem can wipe them all out: the hosting account is broken into, a late invoice gets the service suspended, or the server fails.

Attacks often go after backups too. CISA's #StopRansomware Guide notes that many ransomware variants try to find and then delete or encrypt any backups they can reach. That is why CISA recommends keeping offline, encrypted backups of critical data. For cloud backups, CISA also recommends delete protection and keeping multiple versions.

How often, and for how long?

It depends on how often the website's content changes. A company profile website that rarely changes may be fine with weekly backups. A website that takes orders or form submissions every day needs more frequent backups, especially of the database.

A simple rule of thumb: if the website had to go back to the last backup, how much data could you afford to lose? If the answer is "not a single one of today's orders", a daily backup may not be enough.

What often gets forgotten is how long backups are kept. A hack is sometimes only discovered weeks later. If you only keep the last three days of backups, they may all contain the malicious code. WordPress's documentation recommends keeping several recent backups in different places, and it is worth keeping some older versions too.

A backup that has never been tested may not work

CISA recommends regularly testing the availability and integrity of backups in a disaster recovery scenario. In practice, that means:

  • Every so often, restore a backup to a test environment, not the live website, and check that pages, images and forms work.
  • Note how long the restore takes, so you know how long the website could be down in an emergency.
  • Write down the restore steps, so more than one person knows how to do it.

Things that often get forgotten

  • Backups in a public folder. ZIP files or database copies kept in the website's folder can be downloaded by anyone. We cover this kind of leak in our article on exposed .env files and .git folders.
  • Access to backups. The backup storage account should be in the company's name, not a staff member's or vendor's personal account, and protected with two-step verification.
  • Sensitive data without encryption. A website database can hold customer data. CISA recommends encrypting sensitive data and keeping storage media physically secure.
  • Nobody checking. Automatic backups can quietly stop. Add a backup check to your monthly security checklist.

A good backup isn't the one made most often, but the one kept separately and proven to restore.

Want to make sure your company website has a proper safety net? Read also the basics of company website security, or get in touch to talk it through.