Glossary

Restore test

Backup restore test Test restoration

Definition

A controlled exercise that checks whether backed-up data or systems can be recovered and used.

A restore test recovers a backup in a controlled setting and checks the result. It can expose missing files, unusable applications and unrealistic recovery times.

A customer may include “Restore test” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

A restore test checks that a backup can become working data again. It involves retrieving a chosen copy, restoring it into a suitable environment and confirming that the result can be used. Reading a green status on the backup dashboard is a different check.

Imagine a small agency restores last week's project folder into a separate location. Its designer opens several files and checks linked assets. A wider exercise might restore the project-management database and confirm that the application starts with the correct permissions. The scope determines what the result proves.

Record the recovery point used, elapsed time, checks performed and any problems. A file-level test may show that files can be retrieved without showing that a whole business service can restart. Where the service depends on accounts, encryption keys or another database, those dependencies need attention too.

Use a controlled environment so restored data does not overwrite current records or reconnect an infected system. Restore representative files and applications into a safe environment, then verify they open and the business process works. Record duration, missing dependencies and corrective actions; a successful backup job is not a restore test. Frequency should reflect how quickly systems change and how costly failed recovery would be, rather than an arbitrary calendar rule.

Sources

AWS Backup: restore testing

NCSC: backing up your data