Websites

Website backups: what to save and how to plan a safe restore

Know what a usable backup includes, where it is held and who can restore it when an update or outage goes wrong.

By Graphic Core   /   Published
Monthly guide series: October 2020

Two external drives beside a padlock and a cream folder.

A backup is a route to recovery

A website backup is a copy of information needed to restore the site after an error, compromise or other loss. A message saying “backup completed” is reassuring, but it does not by itself prove the right files were saved or that anyone can restore them. Agree what the business needs to recover and who is responsible for doing it.

The right plan depends on how the site works. A small static website, a WordPress installation and a shop with frequent orders can have different components and recovery needs. Start by identifying the services involved rather than assuming that one hosting snapshot covers every part of the customer journey.

List the components you need to recover

A typical WordPress site includes files such as themes, plugins and uploaded media as well as a database containing page content and settings. Both are commonly needed for a complete restoration. A static site may instead depend on source files, a build process and deployed assets. Ask the developer what applies to your actual platform.

Check where form submissions, booking information, shop orders and email are held. They may be in a separate service and outside the website host’s backup. A backup of the website does not automatically protect an email inbox or an external customer database. Include each system in the broader business recovery plan where appropriate.

Choose frequency and retention deliberately

The backup frequency should reflect how often important information changes and how much recent work the business could reasonably recreate. A site edited several times a day may need a different arrangement from one updated occasionally. Back up before significant updates or migrations as well as on the normal schedule.

Ask how long copies are retained, whether older versions are available and what happens if a problem is discovered after several days. A single copy can contain the same error or unwanted change as the live site. Balance retention with security, storage and applicable data-handling obligations; agree the actual schedule with the responsible provider.

AT A GLANCE

From backup to recovery

  1. IdentifyList files, data and other services
  2. CopyUse an agreed frequency and location
  3. ProtectRestrict access to backup data
  4. TestPractise a safe restore and check it
A backup plan includes the ability to restore the information the business actually needs.

Store and protect copies appropriately

A backup held only alongside the live site may be affected by the same account loss or technical incident. Consider a protected copy in a separate location, with access restricted to people who need it. The National Cyber Security Centre recommends planning backups and checking that they can be restored.

Backups can contain confidential information and configuration details. Secure the storage account, use strong unique credentials and additional sign-in protection where supported, and follow the business’s data retention rules. Do not send full backup archives through ordinary email or place them in a publicly accessible folder for convenience.

Practise the restore before an emergency

Agree who can request and perform a restore, how long the process is expected to take and what checks follow it. Where practical, test in a safe non-public environment rather than overwriting a working live site. Confirm that the test includes important pages, images, account access and the appropriate version of the database or content.

A restore may replace newer work or data, so establish the scope and obtain the necessary authorisation before acting. For a shop or booking system, coordinate with the provider on transactions that occurred after the backup. A technically restored homepage is not enough if orders, forms or permissions are still missing.

An illustrative recovery exercise

Imagine a Hertfordshire service business whose website displays an error after an extension update. The owner records when the problem began and contacts the agreed support person. Before changing more settings, they confirm whether a recent backup exists and whether its files and database belong to the same usable backup set.

In this hypothetical scenario the supplier tests recovery on a non-public copy, checks the service pages and form configuration, then agrees the live action with the owner. The business records the cause and result. This example describes a cautious process; it is not a promise that every incident can be solved with a restore.

Record the decisions your team needs

Keep the provider, backup location, frequency, retention period, last successful test, responsible person and recovery contact in a protected handover record. Document where access can be recovered without recording passwords in plain text. If a supplier changes, confirm that the business can still obtain a copy and request a restore.

Note any exclusions, such as third-party booking data or email. If the website changes platform or begins taking orders, review the plan. A backup arrangement that suited a simple brochure site may be inadequate once the business depends on more frequent transactions or important uploaded content.

A short backup review

Ask what is saved, how often, where the copy is held, who can access it and whether a restore has been tested. Check that the relevant website files and database are included where applicable. Confirm the separate treatment of email, forms, bookings and payments. Record the next review and the person who owns it.

Before a major update or move, verify a current usable backup and agree a recovery route. After a test restore, inspect a representative customer journey, including links and contact options. These checks cannot eliminate every disruption, but they make the business better prepared to identify and respond to one.

Set recovery expectations in plain language

Ask the business owner two practical questions: how much recent work could be lost without serious disruption, and how long could the important customer journey remain unavailable? Those answers can help the provider propose a backup frequency and recovery arrangement. They are planning targets, not guarantees; the actual outcome depends on the incident and the available backup.

Use a short test record with the backup date, test environment, person responsible, components restored and checks completed. Include a representative page, an image and any relevant configuration, while protecting private data in the test environment. If a test fails, record the gap and agree a correction date. Recheck the plan after introducing transactions, bookings or another system that stores important information outside the website. Ask the relevant provider how its own records can be recovered and how the restored website will reconnect to that service.

YOUR NEXT MOVE / 01

Ready to make
more of your business?

Tell us about your website, your services and where you want to grow.

START A CONVERSATION