Website essentials

Website backups: a simple recovery plan for a small business

Decide what your website backup must include, who can restore it and how to test recovery before a real problem.

THE KEY IDEA

A backup is useful when an authorized person can restore the right content. Define the recovery steps and test them in a safe place.

List what the website needs to work

Start with an inventory. A simple static website may need its published pages, images, styles and source files. A content-managed site may also depend on a database, uploaded media and configuration. A working copy of the front page alone may not recreate the whole service.

Ask the maintainer to explain each dependency in plain language. Domain registration, DNS, hosting, email and external forms may use separate accounts. Record where each service is managed and who is authorized to change it. Keep credentials out of the general inventory.

Agree what would be acceptable to lose

Imagine a failed update today. How much new content could you afford to recreate, and how long could the website be unavailable? A brochure site updated monthly has different needs from a site taking enquiries or orders throughout the day.

Use those answers to choose backup frequency and retention with the maintainer. State how many older versions remain available, where copies live and who checks failed backup jobs. Do not assume the word “backup” in a hosting plan answers all those questions.

Ask the hosting provider specific questions

  • Which files, databases and uploaded assets are included?
  • How often are copies made, and how long are they retained?
  • Can an accidental deletion overwrite or remove the only copy?
  • Can we download or export a usable copy?
  • Who can request a restore, and is there an additional charge?
  • What happens to stored copies after cancellation or account closure?

Read the answers alongside the actual plan terms. Keep an appropriate independent copy where your business can access it. The UK National Cyber Security Centre’s small-organisation guidance explains why identifying and copying essential business data matters.

Test a restore without replacing the live website

Arrange a test on a separate location controlled by your maintainer. Use a known backup and check whether the pages, images and navigation return correctly. For a database-backed website, include a suitable database recovery check rather than testing only static pages.

Prevent the test site from sending real customer messages, accepting live payments or exposing private data. Ask the maintainer how these functions will be disabled or isolated before the test begins. Keep the live site serving visitors while the recovery exercise runs.

Record the backup date, who performed the test, what worked, what failed and how long it took. The NCSC recommends testing restored data; a successful export alone does not demonstrate that the site can be recovered.

Keep a short recovery runbook

  1. Identify the problem and stop unnecessary changes.
  2. Contact the authorized maintainer through a recorded route.
  3. Select an appropriate known-good backup and review what would be lost.
  4. Restore using the agreed process and check important visitor journeys.
  5. Record the cause and improve the backup or publishing process.

After a suspected account compromise, involve a qualified maintainer before restoring into the same environment. A copy of the content is only one part of recovery; account access and the cause of the incident also need attention.

Review this plan when you change hosting, add a database or hand the site to a new collaborator. Compare the questions above with our hosting overview, then use the launch checklist to review the recovered site.

Sources & further reading

Primary references checked 9 November 2026. The checklists and examples are BizGuide’s planning guidance; confirm account-specific instructions with your provider.

General educational information. This checklist does not replace a technical assessment of your own website or provider terms.

Useful? Pass it on.Share by email ↗Follow via RSS ↗
← Back to the journal