πŸ“„
Webhosting

Testing backups: are you sure restoration works?

πŸ“… 5 November 2026 ✏️ 5 November 2026 ⏱ 4 min leestijd

Having a backup isn’t enough. Read how to check whether your website backup actually works when you need it.

Many website administrators assume their backup is fine, until it turns out that restoration fails at the moment it’s really needed. Testing a backup means periodically checking whether the file is complete, readable, and actually restorable. You do this by creating a test environment, restoring the backup there, and checking whether the website, database, and email work correctly.

Why an untested backup is risky

A backup sitting on a disk or in the cloud somewhere gives a false sense of security if you’ve never checked whether it works. Common problems that only surface during restoration: an incomplete database dump, a corrupted archive, missing files from the upload folder, or a backup that gets created but never completes successfully. If you discover this only when your website has been hacked or an update goes wrong, it’s too late.

πŸ’‘ Tip: Schedule a fixed reminder, for example every quarter, to test a backup. That way it becomes a routine instead of something you forget.

What exactly to check

Testing is more than just checking whether the file can be unpacked. Check at least the following items after a restore:

  • Files: are all page files, images, and uploads present?
  • Database: does the website load without error messages, and is all data (products, posts, settings) still there?
  • User accounts: can you still log in to the CMS with existing usernames?
  • Forms and plugins: do important functions such as contact forms or a webshop checkout still work?
  • Email configuration: if you also back up email settings, check whether DNS records such as MX still point correctly.

Testing a backup in a staging environment

The best way to test without risk to your live website is to restore the backup to a separate staging environment or subdomain. This way you can calmly go through everything without visitors noticing anything.

1

Set up a test environment

Set up a separate folder or subdomain, apart from your live website, to restore the backup into.

2

Restore the files

Unpack the backup archive and place all files in the test environment, including upload folders.

3

Import the database

Create a new database and import the database dump from the backup. Adjust the connection details in your configuration file.

4

Go through the website

Visit the front end and the admin area, test logging in, forms, and important pages.

5

Clean up the test environment

Remove the test environment afterward, so no outdated copy of your website remains online.

If you use Plesk, you can easily select a restore point via the backup section and restore it to a separate domain or subdomain without affecting your live environment.

How often to test and what to record

How often you should test depends on how often your website changes. For a webshop with daily orders, testing monthly is wise; for a simple brochure website, a few times a year is often sufficient. After each test, briefly record: date, which backup you tested, what you checked, and whether everything worked properly. This way you build up a history and can quickly spot structural problems.

πŸ’‘ Tip: Keep not only the most recent backup but also a few older versions. If a problem only becomes apparent after a while, you’ll still have a usable restore point.

If you’re unsure whether your current hosting package offers sufficient backup options, check out the options at webhosting with daily backups included. If you’re considering switching because your current provider doesn’t offer reliable backups or restoration options, read more about switching to Tandata.

Frequently Asked Questions

Can I test a backup without affecting my live website?

Yes, you can do this by restoring the backup to a separate test environment or subdomain, so your live website remains untouched.

What if restoring my backup fails?

First check whether the file is complete and not corrupted. If it still doesn’t work, contact your hosting provider for support with the restoration process.

Should I also include email in a backup test?

If you have email accounts with the same provider as your website, it’s wise to also check whether mailboxes and settings are restored correctly, see also business email.

Conclusion

A backup is only valuable if you know that restoration actually works. Test regularly in a separate environment, check files, database, and functionality, and record the results. This way you avoid surprises at the moment you need the backup most.

View webhosting β†’

Was dit artikel nuttig?