Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,090 of 9,090 pages
About the help in other languages
All help pages

Restore drills

How to prove that your backups work by restoring one on another machine on a schedule, what to check, how to keep the copy from mailing real customers, and how to record the result as evidence.

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/businesses/reliability/restore-drills.md

On this page

Restore drills

This page is for managers who need evidence that the business can recover from a lost server, and for the operator who runs the drill. A restore drill is a planned restore of a real backup onto another machine, timed and checked. It turns "we have backups" into "we restored one last month in this many minutes". The technical procedure is Restore and restore tests.

Contents

  1. Why drill
  2. How often
  3. Before the drill
  4. The drill, step by step
  5. Checks that prove the restore
  6. Keep the copy quiet and private
  7. Record the result
  8. What a failed drill teaches

Why drill

The guides are blunt: "a backup you have never restored is a hope" (Operating a site). A drill proves three things at once:

  • The backup is complete: the database and the files are both there, from the same moment.
  • The procedure works: the people on duty can follow it, and the instructions are current.
  • The recovery time is known: "Write down how long it took; that is your recovery time" (Backups and restores).

Without the last point, any promise of how fast you recover is a guess.

How often

The sources set a minimum: restore "on another machine at least once and after every major upgrade" (Restore and restore tests), and the weekly checklist asks that a recent backup "has been restored at least once on another machine" (Operating a site, a weekly checklist). The hosting section's monthly checklist restores one site's backup per month, in rotation (Monthly operations).

Choose your own rhythm above that minimum, and put it in the calendar with a named owner.

Before the drill

  • To do: A test machine (or a temporary server) is available that is not reachable from the public internet.
  • To do: It runs the same Exponential release and the same composer.lock as the backup (Restore and restore tests).
  • To do: The person running the drill is not always the same one: rotate it, so the knowledge is shared.
  • To do: A stopwatch, or a note of start and end times.
  • To do: The restore procedure is printed or open, and you follow it exactly as written.

The drill, step by step

The steps match the restore procedure of the installation book (Restore and restore tests):

  1. Note the start time.
  2. Fetch the backup from where it is stored, as you would after losing the server.
  3. Switch maintenance on for the test copy (php bin/php/maintenance.php on --message="Restoring" --allow-root-user); under Velocity also stop the server.
  4. Restore the database with its engine's tool and unpack the files.
  5. Fix the owner and mode of the unpacked files.
  6. Clear every cache and regenerate the autoloads: php bin/php/ezcache.php --clear-all --allow-root-user and php bin/php/ezpgenerateautoloads.php -e.
  7. Under Velocity start the server and clear its response cache; switch maintenance off.
  8. Run the checks below. Note the end time.

Checks that prove the restore

From Restore and restore tests, checks after a restore and Backups and restores:

CheckGood result
The front page, a deep page, an image, a downloadThey load, images included
Sign in to the administrationThe dashboard opens
Setup > System informationThe expected release; no failed health check
php bin/php/cache.php status --allow-root-userEnds in PASS
php bin/php/audit.php verify --allow-root-userExit status 0
Publish a test itemIt appears on the test site
A form (contact, sign-up)It submits; the mail goes to the file transport, not a real address
The newest content you expectIt is there; tells you the real recovery point
tail -n 50 var/log/error.logNothing you cannot explain

For a shop, add: the newest order you expect is in the order list (Stores).

Keep the copy quiet and private

A restored copy is a full site with real accounts and real e-mail addresses. Before you start it (Restore and restore tests):

  1. Stop mail: set [MailSettings] Transport=file in the test machine's settings/override/site.ini.append.php, so every mail is written to a file instead of being sent.
  2. Do not install the crontab on the test machine, or notifications, newsletters and content jobs run against real addresses.
  3. Restrict access: the copy holds personal data; keep it off the public internet.
  4. Remove the copy when the drill is done, including its database and files.

Warning

A forgotten test copy that sends a newsletter to all members, or that stays online with real customer data, turns a drill into an incident. Steps 1 to 4 are not optional.

Record the result

"Record each test in one line: date, site, backup used, time to restore, result, who ran it" (Restore and restore tests). A table like this is enough:

DateBackup usedWhoMinutes to restoreNewest content foundResultFollow-up
(fill in)

This line is the evidence a manager, an auditor or a customer asks for. Keep the history; a rising restore time is an early warning that the site has grown and the plan needs to change.

What a failed drill teaches

A drill that fails is a success: you found the problem on a quiet day. Common findings (Restore and restore tests, what goes wrong):

FindingUsual cause
Images missing, pages fineThe files half was not backed up, or is from another moment
Errors about missing tables or columnsThe backup is from another release; apply the upgrade steps
The site shows old contentCaches were not cleared after the restore
Class ... not foundAutoloads or vendor/ do not match
The web server cannot write var/Owner or mode wrong after unpacking
The restore takes far longer than expectedThe site has grown; review your recovery time promise

Fix the cause, update the written procedure, and run the drill again.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x