t.TERABYTE
COMPUTER
Storage & backup

Testing a backup by restoring a real file

Opening a restored file tells you more than a green status message.

External drives beside a laptop

The copy needs to work again

The backup application reports success, the external drive is disconnected, and the job is finished. One useful step is missing: bringing a file back from that backup. You do not need to lose anything deliberately. A harmless example can establish whether the storage location, access method and restore process fit together.

Choose a file whose contents you know, such as a document you wrote. Add a photograph and, where relevant, a file from an application you use regularly. Restoring a text document does not establish that a specialist project file is complete or can still be opened in the software it requires.

Restore into a separate test folder

Create an empty folder first. Use the backup program’s restore function and select that folder as the destination, where a different destination is supported. Do not overwrite the original. You can then compare the two copies without making an unnecessary change to the working files you depend on.

Actually open the copy. Check several pages of a document, view a photograph at full size, or inspect a project’s linked resources. A plausible filename and file size are not enough. The main project file might be present while a linked picture or a separate working folder is missing.

If the backup keeps earlier versions, test that feature too. Back up a disposable document, change it, then run another backup. Find the earlier version through the restore interface. Pay attention to the displayed date: the backup timestamp and the file’s modification time need not be identical.

Consider access without the original machine

A backup is less useful if its only password is on the laptop that has failed. Check which credentials, recovery keys and applications the restore process requires. Keep the necessary information somewhere accessible without that computer. Sensitive keys should not be left openly beside the screen.

For an encrypted backup, unlocking it is part of the test. For a cloud backup, account access needs to work. You do not have to reinstall a whole computer to begin checking. Start with a single restore and note where you unexpectedly need to search for instructions or obtain additional information.

Check again after changes

Record the date, backup checked, file types and outcome. If something is missing, adjust the included folders and repeat the affected step. Files on a second drive are not automatically protected merely because the standard Documents folder is included in the backup.

Repeat the exercise after changing software, replacing a backup drive or moving to another computer. There is no need for an arbitrary weekly ritual. The important thing is knowing the route back to your files and supplementing the reassuring green status message with a copy that you have actually used.

Try more than one kind of file

At the next test, deliberately choose different material: a text document, a photograph and a file from an application you use regularly. A picture may open on its own while a project needs linked media or a separate catalogue. For those projects, inspect the referenced material as well as the first file. An apparently empty project can indicate missing links even when the project file itself was copied completely.

Versioned backups deserve another trial. Put a recognisable sentence in a disposable document, back it up and change the sentence later. Then restore the older version to a separate location. This shows whether an earlier state can actually be selected or whether you are only retrieving the most recently saved copy. Keep important originals out of the experiment.

Think about access to the backup as well. If its password or key exists only on the failed computer, an intact encrypted copy is not enough. Establish beforehand where the required access information is independently available. Do not write secrets into a public test record; simply note that the intended recovery access was checked.

A different computer can provide another useful test where the backup software supports it. It reveals whether recovery depends on a particular installation or an account saved on the original device. Record which software and access were needed. That information belongs in recovery planning alongside the date of the last successful backup.

Sources and documentation

Microsoft: Backup, restore and recovery ↗
← Back to section