メインコンテンツへスキップ
EnglishEN EspañolES FrançaisFR DeutschDE ItalianoIT PortuguêsPT 中文ZH 日本語JA 한국어KO РусскийRU NederlandsNL
← Back to all articles

この記事は現在、英語版のみです。

Website Backups: What to Back Up, How Often, and Where to Keep It

Most small business owners assume their website is backed up. Often it is, in a way: the host takes a snapshot, a plugin runs on a schedule, or the developer kept a copy from launch day. The trouble is that nobody has checked whether that copy is complete, recent, stored somewhere safe, or restorable. You usually find out on the worst possible day, after a bad update, a hacked plugin, an expired hosting account or an accidental delete.

This guide sets out a simple backup plan based on official guidance from WordPress, the MySQL documentation and the US Cybersecurity and Infrastructure Security Agency (CISA). It covers what to back up, how often, where the copies should live and, most importantly, how to test that you can get your site back.

Key facts

  • 2 parts — A complete site backup: the files and the database, which WordPress stores separately
  • 3-2-1 — CISA's rule: 3 copies, on 2 types of storage, with 1 copy off-site
  • Weekly / daily — WordPress's suggested backup frequency for small sites and busy sites
  • 7 days — How far back CISA says you should be able to roll back data

What a Complete Website Backup Includes

A website is usually two things stored in two places. WordPress's own documentation puts it simply: there are two parts to backing up a site, the database and the files. Downloading the website folder does not copy the database, and exporting the database does not copy your images.

The files

  • Your own content and customisations. On WordPress this is the wp-content folder: uploaded images and documents, themes (especially edited ones) and plugins.
  • Configuration files. wp-config.php holds the database connection details, and .htaccess holds redirects and server rules. On a custom PHP site, include config files, environment files and anything outside the web root that the site depends on.
  • Custom code. Templates, scripts and stylesheets that are not available as a fresh download anywhere else.

Core WordPress files can be downloaded again, so they matter less, but backing up the whole site folder is the simplest way to be sure nothing is missed.

The database

Posts, pages, settings, users, form entries and orders live in the database (usually MySQL or MariaDB). A database backup is normally an export file, often a .sql file, that has to be imported back into the database server to restore it.

The things people forget

  • DNS records and domain registrar details. Write them down or export them, because restoring a site does not restore its DNS.
  • Email settings, SSL setup notes and any third-party accounts (payments, forms, analytics) the site connects to.
  • Logins for the host, registrar and backup storage, kept in a password manager rather than in the backup itself.

How Often to Back Up

The right frequency depends on how much work you can afford to lose. WordPress's backup guide suggests weekly backups for smaller sites with fewer posts and daily backups for busier ones, and says to always back up before an upgrade.

  • Brochure site that rarely changes: a weekly backup, plus one before any update or redesign.
  • Site that collects leads, bookings or comments: daily database backups, because new entries arrive every day even if the pages don't change.
  • Online shop: at least daily, and more often if orders come in all day. Some hosts and tools offer hourly or near-continuous database backups for this.
  • Before every change: plugin, theme and core updates, PHP version changes, migrations and design changes. This is the backup you are most likely to need.

For larger databases, the MySQL manual describes incremental backups using the binary log, which record changes made since the last full backup and allow point-in-time recovery. Most small sites don't need this, but it is worth knowing it exists if your host offers point-in-time restore.

How long to keep them

Keep more than one. WordPress recommends keeping several recent backups in different locations, and CISA advises being able to roll data back at least seven days. That matters because problems such as malware or a broken plugin are often noticed days later, by which time the newest backup may already contain the problem.

Where to Keep Your Backups: The 3-2-1 Rule

A backup stored on the same server as the website is convenient, but it fails in exactly the situations you need it most: the server dies, the account is suspended, or an attacker gets in. CISA describes the 3-2-1 rule as a trusted guideline:

  • 3 copies of your important data (the live site counts as one);
  • on 2 different types of storage;
  • with 1 copy off-site.

For a small business website, that might look like this:

  1. The live site on your host.
  2. Your host's automatic backups, which are quick to restore from.
  3. A copy in separate cloud storage that you control, under an account that is not your hosting login.

Many owners also keep a periodic copy on a local computer or drive. WordPress suggests storing copies in different places and on different media for the same reason.

Protect the backups themselves

CISA's ransomware guidance recommends offline, encrypted backups of critical data and, where storage supports it, delete protection or object lock so backups cannot be quietly wiped. For a small site, the practical version is:

  • use a separate account with a strong, unique password and two-factor authentication for backup storage;
  • don't give the website itself permission to delete old backups if you can avoid it;
  • encrypt backups that contain customer data, since a database export can include names, emails and order details.

Host Backups, Plugins or Manual Copies?

There are three common ways to make backups, and most sites benefit from combining two of them.

  • Host backups. Many hosting plans include automatic backups. They are easy to restore from the control panel, but check how often they run, how long they are kept, whether they include the database, and whether a restore costs extra. They also live with the same company as your site, so they don't count as your off-site copy.
  • Backup plugins or services. These schedule backups and can send them to cloud storage. WordPress's guide notes that automatic backups are useful, and also advises taking a manual backup once in a while to make sure the process is working.
  • Manual or scripted backups. Download the files over SFTP or SSH and export the database. On MySQL, the manual notes that mysqldump with the --single-transaction option can take an online backup of InnoDB tables without locking them, which avoids taking the site offline.

Whichever method you choose, back up the database and files together and keep them in the same dated folder or archive. WordPress suggests backing up the database first, then the files, so the two stay consistent.

Test the Restore, Not Just the Backup

A backup you have never restored is a hope, not a plan. CISA's guidance is to run scheduled recovery tests to verify backup integrity, and to confirm you can restore both a full site and individual pieces of data. Its ransomware guide also says to regularly test the availability and integrity of backups.

A simple restore test for a small business site:

  1. Pick a recent backup from your off-site copy, not the host's panel, so you test the copy you would rely on in a real emergency.
  2. Restore it somewhere safe: a staging site, a subdomain or a local test environment. Never test by overwriting the live site.
  3. Restore the files first, then import the database, which is the order WordPress recommends. If the database name or password is different, update wp-config.php or your site's config file to match.
  4. Check that it works: the homepage loads, images appear, you can log in, forms submit and recent posts or orders are present.
  5. Write down how long it took and anything that went wrong. That note becomes your recovery checklist.

Doing this once or twice a year, and after any change to your hosting or backup setup, catches the common failures: backups that silently stopped, archives that are missing the database, or files too large to download in a hurry.

A One-Page Backup Plan You Can Copy

  • What: all site files plus a database export, together in one dated archive. DNS records and account details noted separately.
  • How often: weekly for a site that rarely changes, daily if it takes leads or orders, and always before updates.
  • How many: keep at least a week of daily backups or several weekly ones.
  • Where: host backups plus one copy in storage you control under a separate account (3-2-1).
  • Protection: unique password and two-factor authentication on backup storage, encryption for anything containing customer data.
  • Testing: a test restore to staging at least twice a year, with written notes.
  • Owner: one named person who checks the backup reports and knows where the restore checklist lives.

Backups pair naturally with the rest of routine maintenance: updates, uptime checks, security headers and form testing. If you do the backup first, every other change becomes a lot less risky.

Sources

Related reading

Frequently asked questions

Are my host's automatic backups enough?

They are a good start and the quickest way to restore, but they live with the same company as your site. If the account is suspended, hacked or closed, those backups can go with it. Keep at least one more copy in storage you control under a separate account, which is the off-site copy in CISA's 3-2-1 rule.

How often should a small business website be backed up?

WordPress suggests weekly backups for smaller sites and daily backups for busier ones, plus a backup before every update. If your site collects leads, bookings or orders, back up the database at least daily, because new data arrives even when the pages don't change.

What is the 3-2-1 backup rule?

It means keeping three copies of your data, on two different types of storage, with one copy off-site. CISA describes it as a trusted guideline. For a website, that is usually the live site, your host's backups, and a separate cloud copy you control.

Want a site that is easy to back up and restore?

BuiltToWinWeb builds custom small business websites and can explain exactly what to back up for yours. Get a free quote.

Get a free quote