Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Web Development

Website Backups: What Should Be Saved—and How Do You Know You Can Restore It?

Website Backups: What Should Be Saved—and How Do You Know You Can Restore It?

A useful website backup contains the information needed to recover the website, is accessible when the main service fails and has been tested through a restore. A “backup completed” notification does not establish all three.

Begin with what you need to recover. A brochure website, online store and application portal can tolerate very different amounts of missing data and interruption.

Check the contents of the backup

For a typical WordPress website, you need both the database and website files. The database holds important content and settings, while files include uploads, themes, plugins and configuration. Downloading one does not automatically capture the other.

WordPress explains this distinction in its backup guidance: https://developer.wordpress.org/advanced-administration/security/backup/.

Item Question to ask Possible gap
Database Is the relevant database included? Pages or application records missing
Files Are uploads and custom code included? Missing images or functionality
Configuration Can the restored system be configured correctly? Wrong URLs or unavailable integrations
External services Which records live outside this backup? Email or third-party data assumed to be included
Recovery access Who can retrieve and restore the backup? A usable archive nobody can access

Choose a schedule around how the website changes

A site updated once a month has different recovery needs from one receiving orders throughout the day. Discuss how much recent information the organisation could reasonably reconstruct if it had to restore an older copy.

Also consider the time needed to restore service. Retrieving an archive is only part of recovery; the team may need to configure the environment, reconnect services and check the result.

Avoid choosing a frequency because it sounds reassuring. Define the business need, then check whether the hosting and backup arrangement can meet it.

Keep recovery independent of the failure

A copy stored only inside the same hosting account may be unavailable when that account is suspended or compromised. Review where backups are held, who can access them and what happens if the primary provider is unavailable.

Protect backup access appropriately. Archives may contain private customer details, configuration and other information that should not be publicly downloadable. Encryption, access control and retention arrangements should fit the contents and recovery process.

Do not assume a hosting plan includes a complete recovery service. Ask the provider about coverage, exclusions, retention, restore assistance and any applicable charges.

Test restoration in an appropriate environment

Use a controlled test environment to check whether the backup can produce a working website. Avoid overwriting the live site merely to see whether an archive opens.

Disable or isolate live payment, email and other external actions in the test environment. A restored order system should not send old notifications or trigger real fulfilment simply because someone tests it.

  1. Record which backup set is being tested.
  2. Restore its files and database using the agreed procedure.
  3. Check pages, images and important settings.
  4. Test representative forms or workflows safely.
  5. Record problems, corrections and recovery time.
  6. Keep the restore instructions with the support record.

A hypothetical shop recovery example

Imagine a shop restores yesterday’s website after a failure. The homepage works, but orders placed this morning are absent. The team must reconcile the newer order and payment records rather than assume the restored database contains everything.

This example shows why the recovery plan needs a process for recent changes. It is not a claimed incident or measured result from a client project.

For a mostly informational website, the missing changes might be a newly edited service page. For a portal, they could include submissions that people expect the institution to retain.

Plan retention and storage deliberately

Keep enough history to support realistic recovery, including a problem discovered after several recent backups were created. Keeping many copies is not useful if they are all affected by the same unnoticed fault.

Storage also needs management. Old archives and staging copies can consume disk space and inodes. Agree how retention works and who removes superseded copies after confirming that recovery needs remain covered.

A backup should not become an unmanaged permanent archive of every person’s data. Set appropriate retention and access arrangements for the business.

Make backup ownership part of website care

Name the person who reviews failures and the supplier who can restore service. Clarify whether support includes monitoring, restore tests and incident recovery, or only installing a backup tool.

My website care service can help assess those responsibilities. If the website is being rebuilt, include recovery planning in the development brief.

Frequently asked questions

Is a website export a full backup?

Not necessarily. An export may contain selected content without the complete files, configuration or external records needed for recovery. Check its scope.

Does a successful restore test prove every future restore will work?

No. It provides evidence about that backup and procedure. Repeat suitable checks as the website and its dependencies change.

Who should hold the instructions?

The organisation and its authorised support owner should have an accessible recovery record, with credentials stored securely rather than embedded in general notes.

Discuss your next step

For help applying this to your organisation, share a short description of your situation and the decision you need to make.

  1. Start on WhatsApp
  2. Send an enquiry through the contact page
  3. Email [email protected]
  4. Call +234 703 799 7791
Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.