A backup plan needs a restore step

A backup schedule can look complete while leaving an important question unanswered: can the files be recovered in a usable form? A practical home plan should describe both copying and restoration. Begin with a small, understood set of files rather than assuming a progress icon proves everything is protected.

Name the material that matters

List the folders and file types you want to recover after loss or damage. Include work that lives outside the obvious documents folder. Note which application is needed to open each important type and whether account access or an encryption key would be required to restore it.

Keep this inventory private where it reveals sensitive information. The aim is to recognise the material and its recovery requirements, not to collect passwords in a plain text document beside the backup.

Distinguish the original from the copies

CISA's published backup guidance describes the three-two-one approach: an original plus two backup copies, using two media types, with one copy offsite. Use it as a planning framework for independent copies and different failure risks, rather than as a guarantee that every chosen service or device meets your needs.

Write where each copy is held and how it is updated. A second folder on the same physical drive is not an independent physical copy. Also check the difference between a synchronised working folder and a backup with recovery history; use your service's current documentation instead of assuming they behave identically.

Test with a harmless sample

Choose a non-sensitive file that is already included in the backup. Follow the product's official restore instructions and restore it to a separate test location, without overwriting the original. Open the recovered copy with the normal application and check that it is the expected version.

NIST's user-awareness material specifically recommends trying a file or folder restoration to check that a backup functions. A successful sample test is useful evidence about that test, not proof that every file or every future restore will succeed.

Write the next action

Record the test date, source copy, recovered file and any difficulty. If recovery depended on a particular account or key, check that your established recovery arrangements cover it. Do not post those secrets in the test note or send them to an unrelated support contact.

Repeat an appropriate test after changing backup software, storage or important folders. Review failures promptly and consult the product's guidance rather than repeatedly creating new copies of an unverified arrangement. A good backup plan has a clear answer to three ordinary questions: what is protected, where separate copies exist and how you have checked that recovery is possible.

References: CISA: data backup options and NIST: backup awareness guidance.