Can you recover what your business needs?
Your hosting provider says it makes backups and its dashboard shows a completed job. That is a useful starting point, but one question remains: can you use a backup to recover the website and its important functions?
You need to know what was saved, when it was saved and how it can be restored. INCIBE’s backup policy guide includes checking that backups can be restored. A saved file or completed scheduled job is not enough.
If your website receives orders, bookings or enquiries, identify which recent information you would need to preserve too. Recovering a version that opens correctly may still leave out important business changes.
Establish what the backup includes and excludes
Start with a clear description of its contents. A website may need files, a database, settings and connections to other services. Business email, the domain or an external booking tool may not be covered by the same backup.
In WordPress, files include items such as images and components; the database holds content and records used by the website. The official backup documentation explains why both are needed for a typical recovery. A content export should not be assumed to be a complete backup.
Ask whether the chosen files and data represent the same point in time or whether differences need resolving. Identify who holds the licences, documentation and access needed to reconnect services. Keep references to those items without putting passwords in a shared worksheet.
Check its date and whether it would be available during a problem
Backup frequency should reflect changes to your website and information your business could afford to reconstruct. A rarely changed information website and a shop taking continuous orders need different assessments. There is no single frequency suitable for every business.
Record which versions are retained, where they are stored and who can obtain them. If the only access depends on a service that is also unavailable or an account nobody controls, that dependency needs reviewing. Discussing it with your provider allows alternatives to be prepared without copying sensitive files around informally.
Restrict access to backups and apply the protections their contents require. A backup may hold the same personal or confidential information as the original website.
Complete a recovery worksheet with your team
| Item | Establish | Useful evidence |
|---|---|---|
| Contents | Included and excluded files, data and services. | Description of the chosen backup set. |
| Point in time | Backup date and relevant later changes. | Identifier and covered period. |
| Availability | Where it can be obtained and who is authorised. | Responsible person and checked access. |
| Restoration | Procedure and environment for the test. | Documented steps and dependencies. |
| Functions | What should work after recovery. | Agreed journeys and their test results. |
| Outstanding checks | What could not be recovered or verified. | Limitation, responsible person and next step. |
The worksheet brings answers together; it does not certify business continuity. Mark anything that has not been tested so a specific check can be arranged.
Test restoration in a separate environment
Agree the test with the people administering the website and backups. Use an environment separate from the service customers use, restricting access and protecting any data it contains.
Review connections before activating the restored copy. A duplicate could send email, run scheduled tasks or contact live payment, booking and stock systems. The team should isolate those functions or use their test modes. Do not place real orders to test a restoration.
Then compare the expected content and agreed journeys: an authorised login, reading information, searching or completing a test enquiry without passing it to live systems. Record what was recovered, what was missing and which conditions differ from the public website.
An example: the shop opens, but recent orders are missing
Fictional example. No restoration has been performed and no client information is described.
A shop tests an earlier backup and recovers its pages and products. However, new orders arrived after that backup was made. A working homepage does not establish what would happen to those orders if the live website were restored.
The exercise leaves an outstanding decision: how that recent information would be preserved and reconciled, and who would coordinate it. The answer depends on the system and incident. Restoring first and checking the losses afterwards does not resolve it.
Review the procedure when the website changes
An earlier test provides evidence about that backup and that environment. If hosting changes, an important tool is added or data moves, review whether the procedure remains suitable.
Include backups and recovery when preparing a provider handover. Establish who makes the backups, who verifies recovery and who authorises a live restoration. Our comparison of maintenance and technical review helps clarify these responsibilities.
What you should have ready afterwards
You should know what could be recovered, from which point in time, using which access and what has actually been tested. That is more useful than a general assurance that “we have backups” and makes outstanding improvements easier to plan.
Nodo91 can assess which website security checks you need. Internal backup checks or a test restoration require access, authorisation and an agreed scope; they are not automatically included in an external assessment.