Drupal backups need restore tests
Many websites have backups. Fewer have tested whether those backups can actually bring the site back.
Backup is not the same as restore
A backup is necessary, but it is not enough on its own. The real question is: can the site be restored so that pages, files, forms and administration work?
A Drupal site usually has at least three important parts:
- database;
- uploaded files;
- code and configuration.
If one of these is missing or from the wrong point in time, restore may fail. The database may exist but files may be missing. Or code may be newer than the database and the site may not boot.
When restore testing matters
A restore test does not have to run every day. It makes sense when the site is business-critical or before a larger change.
Good times for a restore test include:
- before a major Drupal update;
- before changing PHP version;
- before moving hosting;
- before a new development partner starts work;
- after changing the backup system.
If restore has not been tested for a long time, nobody knows how long real recovery would take.
What a restore test checks
A restore test does not usually mean stopping the live site. It is normally done in a separate environment.
The check should confirm whether:
- the database restores without errors;
- files exist and have the right permissions;
- Drupal starts;
- login works;
- forms and email work;
- main pages open;
- logs do not show critical errors.
Drupal's official update documentation also stresses preparation and backups before updates: Updating Drupal.
Recovery time is a business question
A restore test gives one more important answer: how long recovery actually takes.
If the site is small, restore may be fast. If the site has many files, a large database or complex hosting, recovery may take hours. This should be known before there is an incident.
Drupal maintenance should include a clear understanding of backups and restore. If that is missing, a technical audit can help locate the risk.
A good restore test ends with a written result
The result should be short and understandable. It should say:
- which backup was used;
- where the site was restored;
- what worked;
- what did not work;
- how long restore took;
- what needs to be fixed.
This is not bureaucracy. It is confidence that the team will not have to invent the process during a crisis.
Kaido Toomingas
WebPro Company OÜ
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.