Skip to main content

Guides

How Often Should a Website Be Backed Up?

The right backup frequency depends on how often your site changes and how much data you can afford to lose. Here is how to work it out and set it up properly.

Published
Updated
Reading time
7 min read
Restore test passedOff-site copy synced

"How often should we back up the website?" is one of the most common questions we are asked, and the honest answer is that it depends. A brochure site that changes once a month has very different needs from an online store taking orders every few minutes. Backing up too rarely means losing work or orders; backing up without thought to storage and retention means paying for copies you cannot actually use when you need them.

The better question is: how much data can your business afford to lose, and how quickly do you need to be back online? Once you answer that, the backup frequency more or less sets itself.

This guide explains how to work out the right backup schedule for your website, what should be included, how long to keep backups, where to store them, and why testing restores matters as much as taking the backups in the first place.

Start with two numbers: RPO and RTO

Backup planning borrows two terms from disaster recovery. They are worth understanding because they turn a vague question into a business decision.

  • Recovery Point Objective (RPO) – the maximum amount of data, measured in time, you are prepared to lose. If your RPO is 24 hours, a daily backup is enough. If losing even an hour of orders is unacceptable, you need backups at least hourly, or continuous database replication.
  • Recovery Time Objective (RTO) – how long you can tolerate the site being unavailable while it is restored. This drives where backups are stored, how they are formatted and whether a documented, rehearsed restore process exists.

A business owner can usually answer both questions in plain language: "We could re-enter a day's blog edits, but we cannot lose orders," or "If the site is down for more than a couple of hours during the working day, it is a serious problem." Those answers translate directly into technical requirements. The technical glossary defines these and related terms if you need a refresher.

The table below gives sensible starting points. Your own RPO should always take priority over a generic recommendation.

Website typeHow often content changesSuggested database backupsSuggested file backups
Brochure siteOccasionally (weekly or monthly)DailyDaily or weekly, plus before every change
Blog or content siteSeveral times a weekDailyDaily
Lead generation site with forms stored in the databaseDailyDaily, or several times a day if leads are stored only on siteDaily
Online storeContinuously (orders, stock, customers)Hourly or more frequent, or continuous replicationDaily
Membership site or web applicationContinuously (user data, transactions)Hourly or continuous, depending on RPODaily, plus before every deployment

Two points are worth emphasising. First, the database usually changes far more often than the files, so it is common to back them up on different schedules. Second, every site should be backed up immediately before any update, deployment or significant content change, regardless of the regular schedule.

What a complete website backup includes

A backup that only contains part of the site may not be restorable. A complete backup set normally covers:

  • The database – posts, pages, products, orders, customers, users and settings.
  • Application files – CMS core, plugins, themes, custom code.
  • Uploaded media – images, PDFs and other files added through the CMS.
  • Configuration – files such as wp-config.php or environment files, web server configuration (for example .htaccess or Nginx rules) and cron job definitions.
  • Supporting information – DNS records, SSL setup notes, PHP version and extensions in use, and any third-party integration settings that live outside the site.

The last category is often forgotten. A perfect copy of the files and database is much less useful if nobody knows which PHP version the site needs or how the DNS was configured.

Retention: how long to keep backups

Frequency answers "how much could I lose?" Retention answers "how far back can I go?" Retention matters because many problems are not discovered immediately. A malware infection may sit unnoticed for weeks, and a content mistake might only be spotted months later. If you keep only seven days of backups, every copy you hold may already contain the problem.

A common retention pattern, sometimes called grandfather-father-son, looks like this:

  1. Keep daily backups for two to four weeks.
  2. Keep weekly backups for two to three months.
  3. Keep monthly backups for a year or longer, depending on business and legal requirements.

Retention also has data protection implications. Backups that contain personal data are subject to the same rules as the live data, so retention periods should align with your privacy policy and any obligations under GDPR or similar frameworks. SupportSafe can help implement the technical controls, but your legal or compliance advisers should confirm the retention periods that apply to you.

Where backups should be stored

Backups stored on the same server as the website protect you against very little. If the server fails, is compromised or the hosting account is suspended, the backups go with it. The well-established 3-2-1 rule is a good baseline:

  • Keep at least 3 copies of your data (the live site plus two backups).
  • Store them on at least 2 different types of storage or systems.
  • Keep at least 1 copy off-site, with a separate provider or account.

For websites, that typically means the host's own snapshots plus an independent copy in separate cloud object storage, with credentials that are not stored on the web server. Encrypting backups at rest and restricting who can delete them helps protect against ransomware and against an attacker who gains access to the site and tries to destroy the backups too.

Testing restores: the step most businesses skip

A backup is only useful if it can be restored. Backups fail more often than people expect – jobs time out on large databases, storage quotas fill up, credentials expire, files are silently excluded or archives become corrupted. We cover the most common causes in why website backups often fail.

The only way to know a backup works is to restore it. A practical restore testing routine includes:

  • Checking every day that scheduled backup jobs completed and that file sizes look reasonable.
  • Restoring a recent backup to a staging environment at least quarterly, and after any significant change to hosting or site structure.
  • Verifying that the restored site loads, that logins work and that recent content and orders are present.
  • Timing the restore, so you know whether you can meet your RTO.
  • Documenting the restore steps so that someone other than the original developer can follow them under pressure.

Our backup restore test checklist provides a step-by-step version of this process.

Common backup mistakes

  • Relying solely on the host. Many hosting backups have short retention, are stored on the same infrastructure or are not guaranteed. Check your hosting terms carefully.
  • Backing up only files or only the database. Both are needed for a full restore.
  • No backup before updates. The moment you are most likely to need a rollback is straight after a change.
  • Ignoring backup failure alerts. Notifications that go to an unmonitored inbox are no protection.
  • Never testing a restore. Untested backups are assumptions.

Setting up a sensible schedule

To bring this together, a typical small business website might use the following approach:

  1. Automated daily database and file backups, stored off-site, with 30 days of daily retention plus weekly and monthly copies.
  2. An on-demand backup before every update or deployment.
  3. Alerts if any backup job fails or produces an unusually small file.
  4. A documented, quarterly restore test to staging.

An online store would add hourly or continuous database backups, and an application with strict RPO requirements might add database replication to a standby server alongside conventional backups.

Conclusion

There is no single right answer to how often a website should be backed up, but there is a right process for deciding: define how much data you can afford to lose and how quickly you need to recover, then set frequency, retention, storage and testing to match. The most important step is the one most often skipped – proving that your backups can actually be restored.

SupportSafe's website backup and recovery service is designed around tested, off-site backups with documented restore procedures, and backups are included in all of our maintenance plans. If you are not sure whether your current backups would hold up in a real incident, request a free website health check.

Frequently asked questions

Are my hosting provider's backups enough?
Usually not on their own. Host backups are often short-term, stored on the same infrastructure and sometimes not guaranteed. Treat them as one layer and keep an independent off-site copy you control.
How long should website backups be kept?
A common pattern is daily backups for two to four weeks, weekly for two to three months and monthly for a year or more. Align retention with your privacy policy and any legal obligations for personal data.
Do I need to back up the files and the database separately?
They can be backed up together or separately, but both are needed for a full restore. Because the database usually changes more often, it is common to back it up more frequently than the files.
How often should backup restores be tested?
At least quarterly for most business sites, and after any significant hosting or structural change. Daily automated checks that backup jobs completed successfully are also recommended.

SupportSafe Engineering Team

Maintenance, infrastructure and security engineers

Articles are written and technically reviewed by the SupportSafe engineers who carry out website, application and server maintenance for our clients. Each article is reviewed for accuracy before publication and updated when practices change.

Let's take responsibility for your technology.

Tell us what you run and what keeps you up at night. We'll assess it and recommend a maintenance plan that fits – with no obligation.