In short
A backup is only worth something if you can restore it. Decide what you keep (files and database), how often, for how long and where. The Dutch NCSC recommends three versions, on two kinds of media, with one in a different location. Test restoring on a fixed date, in a separate place, and write down who restores and how.
The neglect timeline
This is how it goes wrong. Not with a bang, but in steps that each look harmless on their own.
- Site goes live. Everyone happy. Backups are on, the hosting says.
- First updates postponed. Busy quarter. Next month will do.
- A plugin is abandoned. Nobody notices; it still works.
- Odd spike in traffic. Probably a bot. No time to look.
- Friday afternoon, quarter past four. Site down. Where is the backup again, and does it work?
The timeline above is an example, not a real case. It shows that none of the steps is a disaster on its own. An update left for a month, a plugin that is no longer maintained, an odd spike in traffic: each one can be defended. The disaster only happens when they come together, and when it turns out that the backup everyone relied on cannot be restored.
In this article you read what a backup and a restore test are, why backups fail without anyone noticing, what belongs in the backup for each kind of site, how often and where to keep copies, how to run a restore test step by step and what the Dutch data protection authority says about it. We rely on the Dutch National Cyber Security Centre (NCSC), its British counterpart, the Dutch data protection authority (AP) and WordPress's own handbook.
What is a backup, and what is a restore test?
A backup is a copy that lets you bring back an earlier state of your site or your data. That sounds simple, but a site rarely consists of one thing. According to WordPress's own handbook, a WordPress site has two parts: the database and the files. The database holds the posts, pages and comments; the files include the WordPress core, the themes, the plugins, the uploaded images and the configuration file. You need both to restore the site completely.
A restore test is the restore itself, in a place where it cannot break anything. You are not checking whether a copy exists, but whether you can do something with it. The Dutch NCSC distinguishes two kinds:
- A technical test. This is the minimum. The backup software reports that the backup succeeded, you run a restore and that reports success too.
- A functional test. You restore a full backup and check whether your work runs again, for example whether your office system or your site works. It takes more time but gives more certainty. The NCSC points to a second benefit: you see straight away whether you are backing up the right things and have not forgotten anything.
For a website, the functional test means: the site opens, you can log in, the latest order or enquiry is there and the forms work. Only then do you know the copy is complete.
Why does a backup fail without anyone noticing?
Because a backup is usually only used when something has gone wrong. Until that day, nobody checks whether it is right. These are ways it goes wrong:
- The job no longer runs. A password changed, the storage is full or an update wiped a setting. The warning goes to a mailbox nobody reads.
- A part is missing. The files are copied but the database is not, or the other way round. With WordPress you need both.
- The copy sits in the same place as the site. If the server or the hosting account is lost, the copy is gone too.
- The copy was encrypted as well. The British NCSC writes that ransomware incidents have also hit connected cloud storage holding backups. A copy that is always reachable can be damaged along with everything else.
- The copy does not go back far enough. An error or break-in that went unnoticed for weeks is also in the backups of those weeks. If you only keep the last few days, there is no clean version left.
- Nobody knows how to restore. The person who set up the backup has left, or the login details cannot be found.
You cannot see any of these faults in the green tick of a hosting panel. You only see them when you try to restore. That is why the restore test is not an extra, but the only proof that your backup works.
What belongs in the backup of your site?
That depends on how the site is built. A site that is generated ready-made at build time has different parts from a site that pulls every page from a database. An overview:
| Kind of site | What you need to restore it | Note |
|---|---|---|
| WordPress | The database and all files: core, themes, plugins, uploads and the configuration file | WordPress advises a backup before every update |
| Site generated ready-made at build time, for example in Astro | The source code and content it is built from, and the build instructions | Forms that store data on the server have data of their own |
| Online shop | The database with products, orders and customers, and the product photos | This is where most changes each day, so this is where losses add up fastest |
| Platform or web app | The database, the uploaded files and the server settings | Passwords and keys belong in separate, secured storage |
| Everything around it | Access to domain, DNS, hosting and email, and who holds which login | Without that access you cannot put even a good backup anywhere |
The last row is the easiest to forget. You can only restore a backup if you can get at something: a server, a hosting account, the settings of your domain. So also write down where that access is kept and who has it.
How often, how long and where do you keep the copies?
The Dutch NCSC uses two terms that translate into plain questions. The first is the Recovery Point Objective: how much work can you afford to lose in an outage? The more often you make a backup, the less that is. The second is the Recovery Time Objective: how long may it take before everything works again? That decides how quickly you must be able to restore and which system goes first.
On frequency, the NCSC writes that the safest option is to make a copy of the whole system regularly, preferably daily. WordPress's handbook advises backing up the database regularly and always before an upgrade, and keeping three to five recent backups in different places.
How far back you can go is called retention. According to the NCSC it partly decides what storage costs, and the law may set how long you keep data. Choose a period long enough to recover from an error you only discover after weeks.
For the location, the NCSC gives the 3-2-1 rule:
- 3 versions of your data: the original and two backups.
- 2 different media: for example an external hard drive and a cloud storage service.
- 1 copy in a different location: physically somewhere else, and digitally separate from the rest.
The British NCSC adds one question: is at least one backup offline at any given time? With a copy that is not connected, one incident can never hit all your backups at once. You cannot unplug cloud storage. There, the NCSC advises refusing connections while the storage is not in use, and not giving ordinary computers the right to change backups. A system that may only write new data cannot overwrite existing backups.
| Question | What you decide | Who decides |
|---|---|---|
| How much work can I lose? | How often a backup is made | The owner, with the builder or administrator |
| How long may recovery take? | Who restores, how, and which part goes first | The owner |
| How far back must I be able to go? | The retention period | The owner, taking the law into account |
| Where are the copies? | At least one copy elsewhere, and one that is not always connected | The administrator |
| Who can get at them? | Who has access to the backups | The owner |
| When do we test? | A fixed date for the restore test, and who runs it | The owner and the administrator together |
How do you run a restore test, step by step?
The NCSC gives no fixed interval for testing. Choose one that fits how often your site changes, and also test after every major change, such as a new hosting company or a rebuild of the site. This is how it goes:
- Put the date in the calendar, with a name next to it. A test that belongs to everyone is done by no one.
- Choose which backup to test. Do not always take the newest. Now and then test an older one too, to see whether the retention period holds.
- Restore it in a separate place, never on top of your live site. A test environment at your hosting company or a temporary server is enough.
- Run the technical test. Does the software report that the restore succeeded?
- Run the functional test. Open a few pages, log in, send a test form and check that the latest order, enquiry or change is there.
- Note how long it took. That is your real recovery time. If it is longer than you want, you know now and not during an outage.
- Write down what was missing, and adjust the backup. A missing folder or a forgotten database is exactly what this test is for.
- Clean up the test environment. A restored site contains real customer data. Secure the test environment as well as the real site, and delete it after the test.
The whole report fits on one page: date, which backup, who, how long, what worked and what did not. Keep that report with the restore instructions, so someone else can do it in an emergency too.
What does the GDPR say about backups?
If your site holds personal data, such as customer details, orders or enquiries, the GDPR requires you to secure it properly. The Dutch data protection authority writes that you should at least consider measures to restore the availability of and access to personal data in good time after an incident, and to test at fixed intervals whether your measures are still effective enough. As an example of such a measure, the authority names backups you can use to restore the availability of and access to the data in a timely manner.
A restore test fits that exactly: it is the regular check that you can recover. If another party works for you, such as a hosting company, the authority says you remain responsible yourself. You have to check beforehand whether that party does enough to secure the data. In other EU countries your own national authority supervises this. This is general information, not legal advice.
My hosting makes backups. Is that enough?
It is a good start, but you only know whether it is enough once you have the answers to these questions:
- How often is a backup made, and how long is it kept?
- Is the database included, and the uploaded files?
- Is the copy stored somewhere other than the server your site runs on?
- Can you restore it yourself, or do you have to file a request? How long does that take, and does it cost anything?
- Can you download a copy, so you also have one outside the hosting?
- Do you get a warning when a backup fails, and who reads it?
If your IT is outsourced, the NCSC advises discussing these points with your provider and, where possible, including them in the service level agreement. Even then, the owner should receive and check the reports. Outsourcing does not mean you no longer need to know.
With our maintenance, there is a copy of your site ready every day, and if something goes wrong we put it back. If you stop, you take the latest back-up with you. What a maintenance plan covers is set out under website maintenance services.
When this does not apply
If your site runs on a service where you cannot reach the server yourself, such as a website builder or a hosted online shop, the provider decides what you can restore. Read what that provider promises, ask, and export what you can yourself, such as products, customers and texts. A full restore test as described above is usually not possible there.
If you work in a sector with its own rules, or your organisation falls under stricter law on digital resilience, heavier requirements apply than in this article. This piece is written for the website and data of a small or medium-sized business.
What we do not know: there is no reliable figure for how often backups of small business sites fail, so we give none. Nor do we know exactly how your hosting company handles it. You have to ask, and preferably test it yourself.
Frequently asked questions
How often should I back up my website?
The Dutch NCSC calls daily the safest option. The more often you make a backup, the less work you lose in an outage. With WordPress, its own handbook also advises a backup before every update.
How often should I run a restore test?
There is no fixed interval. Choose a fixed moment that fits how often your site changes, put it in the calendar with a name next to it, and also test after every major change, such as moving to another hosting company.
My hosting says backups are included. Is that enough?
It is a start. Ask how often a backup is made, how long it is kept, whether the database is included, whether the copy is stored elsewhere and whether you can restore it yourself. And test it, because only then do you know for sure.
What is the 3-2-1 rule?
Three versions of your data, the original and two backups, on two different kinds of media, with one copy in a different location. That is how the Dutch NCSC puts it. On top of that, keep at least one copy that is not always connected.
Does the GDPR require backups?
If your site holds personal data, you have to secure it properly. The Dutch data protection authority names restoring in good time after an incident and regularly testing your measures, and gives backups as an example. This is general information, not legal advice.
Not sure when your backup was last restored? Tell us what is running and we will take a look. What well-arranged maintenance involves is described under maintenance and support. You work directly with Nawid, with a fixed team of five specialists.
Also worth reading: The quiet cost of a neglected website.
Written with the help of AI, reviewed and edited by Nawid Rasa, who is responsible for the content. Sources are listed below the article. Spotted an error? Email hi@empireyo.com.
When was your last restore tested?
If you do not know, the answer is too long ago. Tell us what is running; we show what well-arranged maintenance means for your site.
Sources
Consulted on 4 November 2026.
- NCSC (Netherlands), All about good backups
- NCSC (Netherlands), Een back-up strategie opstellen (in Dutch)
- NCSC (Netherlands), Hoe test ik een back-up? (in Dutch)
- NCSC (United Kingdom), Offline backups in an online world (13 August 2019)
- Autoriteit Persoonsgegevens, Maatregelen voor beveiliging (in Dutch)
- Autoriteit Persoonsgegevens, Examples of security measures
- WordPress.org, WordPress Backups (Advanced Administration Handbook)
- Empireyo, case Taxi Grou
- Empireyo, case Ikiz
- Empireyo, case Basestep
- Empireyo, case TaalPro
- Empireyo, case Daily Phones
- Empireyo, case snelrepareren.nl
- Empireyo, case ArtsenPool