Backup restore test: a worksheet that protects the originals

Published 14 October 2026 · Independent editorial guide

A backup restore test answers a practical question: can you get a useful file back from the copy you intend to rely on? A successful backup notification does not answer that question on its own. Start with harmless test files and a separate destination, so a rehearsal cannot overwrite the work you need to protect.

This worksheet is for a small home, office or volunteer-group rehearsal. It tests a selected sample, not every file or a whole computer. If access ownership is unclear, start with the existing accounts and backups for a small volunteer group guide and identify the person authorized to carry out the check.

Define what this backup restore test will cover

Write down the backup service or tool, the copy's date and the files you expect to recover. Choose a sample that represents the work: perhaps a text note, a small spreadsheet and an image. Use files you created for the rehearsal, or copies you are authorized to handle. Leave personal, medical and confidential records out of an initial demonstration.

Next, define success before starting. For a document, this might mean opening the recovered copy in the relevant application and finding the expected content. A folder appearing in the right place is not enough if its files are empty, damaged or from the wrong date. Note any application or encryption access that the recovery needs, without putting passwords in the worksheet.

Restore into an empty, separate folder

Confirm which operation restores a copy and which replaces an existing file. If the wording is unclear, stop and consult the tool's own instructions. Choose an empty folder created for the test, rather than the working folder. Check the destination again before confirming the operation.

Keep the original files and the selected backup unchanged while you rehearse. Do not disconnect shared systems or start a full-device recovery just to test three files. A team that needs a full recovery exercise should plan its downtime, permissions and rollback separately.

CISA's StopRansomware Guide recommends offline, encrypted backups of critical data and regular checks of their availability and integrity. Our small exercise applies the testing principle; it does not prove that a particular backup product or disaster-recovery plan is adequate.

Compare the recovered copy with the expected sample

Open each restored file and check its contents. Record which backup version it came from, whether the application can use it and whether anything expected is missing. An old file may restore perfectly while still being the wrong version for your task.

For an unchanged digital file, a matching checksum is an additional way to compare its bytes. It does not replace an application check or prove that the right records were selected. A document changed during conversion may also have different bytes even when it opens correctly; describe what you checked instead of forcing every result into a single pass label.

A worked example using synthetic files

For this guide, a local rehearsal created three harmless files: a plain-text note, a CSV task list and a note containing non-ASCII characters. The script copied them into a ZIP archive, restored the archive into a new empty folder and compared the restored files with the original sample using SHA-256. All three comparisons matched, and the original sample remained unchanged.

That result shows that this particular sample survived this particular archive-and-extract operation. It does not test a cloud account, encryption-key recovery, a database, permissions or the recovery of an entire computer. The example is a repeatable demonstration, not a claim that your existing backup has passed.

Fill in the recovery worksheet

Record these fields for your own authorized rehearsal:

• Scope: the selected files, backup tool and version of the backup.
• Destination: the separate folder used for the recovered copies.
• Checks: which files opened, which contents or checksums were compared, and any limitations.
• Outcome: matched, different, missing or not checked, with an explanation.
• Follow-up: the responsible person, the next action and the next check date.

Keep the worksheet beside the group's recovery instructions. If a file fails, preserve the error message and investigate without replacing the original. Finally, decide what the next rehearsal should cover. A useful backup restore test produces a specific record of what worked and what remains untested.