Plan and prepare
Choose a small, representative set of files and restore them to an empty test location. Include different formats and at least one file that is important to the project. A successful backup message is useful, but a restore rehearsal shows whether the saved material can actually return in a usable form.
Write the expected result before starting: which files should appear, which versions you need, and how you will judge them. Record the backup date and restore method. Make sure the destination is separate from the live archive so a mistaken choice does not overwrite current work.
Use a clear process
Follow the written recovery instructions as a future custodian would. Note every point where you need a password, recovery key, external service, special application, or help from one person. Keep secrets out of the test report, but record whether authorized access was available. Missing access is a real test result.
After restoring, compare the file list and checksums where available. Open samples and examine meaningful content: page counts, images, attachments, or spreadsheet sheets. Confirm that the restored version matches the intended date. A file can exist at the correct path while still being incomplete or unsuitable for the task.
Worked example
For an initial rehearsal, choose a document, a photograph, and a small catalog export from a known backup date. Write their expected filenames and versions on the test sheet. Restore them into an empty folder labeled for the exercise, then compare that folder with the expected list. Open the document, inspect the photograph at a useful size, and check whether the catalog contains the expected fields. This tests several different ways a recovery can fail while keeping the exercise small enough to finish and review.
Decisions and exceptions
Include one file from an earlier version if the backup system claims to preserve history. The task is to recover the chosen edition, not simply whatever file currently carries the same name. Ask the tester to explain how they selected the date and how they know the restored copy is the intended one. If the software makes that difficult, improve the instructions and repeat the selection. A successful retrieval by the usual expert may conceal a confusing interface or an undocumented step that will matter when someone else must perform the recovery.
Check and improve
Use the results to estimate practical recovery effort without promising that a small sample represents every file. Record setup time, transfer time, access problems, and any manual checks required. Note which parts of the wider collection remain untested and plan a proportionate next sample. Once the rehearsal is complete, handle the test copies according to their sensitivity and keep only the report needed for maintenance. Do not leave restored private records in a casually shared temporary folder. The exercise is complete when the files are usable, the procedure is clear, and discovered failures have a specific owner and retest.
Solo and community application
Working alone, record the elapsed time and any instruction you had to look up. A community team can have a second authorized person conduct the rehearsal while the usual custodian observes. Do not turn the test into a destructive simulation or disconnect essential systems simply to make it feel realistic.
Reference guidance
CISA's ransomware guidance recommends testing backup availability and integrity in recovery scenarios. This small-file rehearsal applies that advice without requiring a full system recovery. Keep a dated result, assign fixes for failures, and repeat the affected portion after changes. Expand the test only when the smaller process works reliably.