The method
- Select a few non-confidential test files and record what you expect from each. Identify the backup copy, its date and the destination. If you are uncertain about the destination or tool behavior, stop before any operation that might replace data.
- Recover the sample into the separate location and compare names, sizes and readable content with your references. Distinguish files merely found from files actually opened. A list of filenames does not alone describe usable content.
- Record each file as recovered, opened, incomplete or unchecked. Include difficulties and the next verification. If infection is suspected, do not run a restored program simply to see whether it works; ask an appropriate specialist to examine the situation.
Fictional worked example
In a fictional exercise, two images and one document are copied into a test folder. The images open, but the document requests a password the learner does not have. The record states two opened and one unchecked; it does not declare the entire backup restorable.
The record to keep
Keep the date, sample, tool, destination and outcome for every file. This record makes separate trials comparable and identifies what remains untested.
Your record, step by step
For your own situation, record the following information. Check a field when it is documented; missing information still needs verification. The boxes are a reminder within this page.
This checklist does not validate your project. No entries are sent or saved.
What this method can establish
A local check validates neither all data nor complete system recovery or incident resilience. Do not delete originals or other copies solely because this trial succeeded.
Supporting documentation
Documentation consulted on
An editorial method, a fictional example and references for further reading.