A green “backup complete” message proves that data was written somewhere. It does not prove you can get the right data back when the laptop dies, a folder is deleted, an account is locked, or malware reaches the storage you thought was safe.
The useful test is much smaller than a disaster simulation: restore one real file now, while nothing is broken. Then test a second failure mode and write down the path you used.
CISA’s ransomware guidance makes the same operational point for organisations: maintain offline, encrypted backups and regularly test their availability and integrity in a recovery scenario. The principle scales down well to a personal laptop or home office. A backup strategy is only as good as the restore path you have actually verified.
Feature check — September 6, 2026: Apple’s current Time Machine guidance supports restoring individual files and older versions, while Migration Assistant can restore a user’s files, apps and account information from a Time Machine backup. Microsoft’s current Windows documentation distinguishes Windows Backup, which uses a Microsoft account and OneDrive for supported files/settings, from File History, which can restore personal files from an external drive or network location. Exact menus and capabilities vary by OS version, account and device.
The quick answer: test four things, not every byte
You do not need to erase your computer or buy another machine to learn whether your backup plan is credible.
A useful 30-minute drill checks four questions:
- Can I restore a file I just deleted?
- Can I recover an older version after I accidentally overwrite something?
- Do I have at least one useful copy that is not continuously exposed to the same computer?
- Could I follow the recovery steps if this computer were unavailable?
Those four tests cover more real-world failure than staring at a backup dashboard that has never been challenged.
Why “the backup ran” and “I can recover” are different claims
Backups fail in boring ways.
The disk can be connected but not receiving the folder you care about. A cloud account can be full. A backup job can exclude a new project directory. Encryption can work perfectly while the recovery password is missing. A file can exist in the backup but be corrupt. A synced deletion can remove the copy you expected to find later. A replacement computer can boot fine while the one software licence or project file you actually need is nowhere obvious.
The most dangerous failure is not always “no backup.” It is false confidence.
A restore drill converts that confidence into evidence.
Step 1: restore one ordinary file on purpose
Time: about 7 minutes
Create a small test file in a folder that should be protected. Put a distinctive line inside it, for example:
Recovery drill — 2026-09-06 — version A
Let your normal backup system capture it. Then delete the local file and restore it using the official recovery path for that backup system.
On a Mac with Time Machine
Apple’s current instructions let you open the relevant Finder location, browse Time Machine backups, select the item and choose Restore. The recovered item returns to its original location.
That is a better test than merely opening the backup disk in Finder. You are validating the supported restore workflow, not just proving that the drive contains files.
On Windows with File History
Microsoft documents File History as a way to save copies of personal files to an external drive or network location and restore previous versions later. Connect the backup storage and use the File History restore interface to recover the test file.
If you mainly use cloud storage
Use the provider’s own deleted-file or version-history recovery path rather than simply downloading the current synced copy. The goal is to test what happens after a mistake, not whether a healthy file is visible on two devices.
After the restore, open the file and check the distinctive line. Do not count a filename appearing in a list as a successful recovery.
Step 2: test the failure people forget — overwriting the right file
Time: about 6 minutes
Deletion is obvious. Accidental replacement is sneakier.
Take the same test file and change its content to:
Recovery drill — 2026-09-06 — version B
Let the change be backed up. Then try to recover version A without deleting version B permanently.
This tests version history rather than simple file recovery.
Why it matters: many real losses are not “the file disappeared.” They are “I saved over the good spreadsheet,” “the document was corrupted,” or “a sync conflict replaced the version I wanted.”
A system that can restore deleted files but cannot take you back to an older usable state may still leave a large recovery gap.
Step 3: identify which copies share the same failure
Time: about 7 minutes
Now draw a tiny map of where the important data exists.
| Copy | Where it lives | Continuously connected? | Same account? | What failure can remove it? |
|---|---|---|---|---|
| Working copy | Laptop SSD | Yes | — | device loss, disk failure, malware |
| Cloud copy | Sync provider | Yes | Usually | account loss, sync mistake, retention limits |
| Local backup | External drive | Maybe | No | disk failure, theft, malware if mounted |
| Offline/off-site copy | Disconnected drive or other protected location | No | Depends | separate physical/account risks |
The point is independence.
Two copies are much less useful if the same event can destroy both. A backup disk that stays mounted all day can be exposed to malware or destructive mistakes affecting accessible storage. CISA specifically recommends offline backups for critical data because ransomware often attempts to delete or encrypt backups it can reach.
For a personal setup, “offline” can be simple: an external drive that is connected for backups and then disconnected, or another protected copy that is not permanently writable from the main computer.
You do not need every file in three expensive systems. Prioritise the material that would be painful or impossible to recreate: family photos, tax records, active work, source files, important exports, encryption recovery material and documents that exist nowhere else.
Step 4: write the recovery card you would need without your laptop
Time: about 10 minutes
Imagine the current computer is physically unavailable.
Could you answer these questions from memory?
- Which backup system contains the latest useful copy?
- What account or password is required?
- Where is the recovery key for encrypted storage?
- Which folders are intentionally not backed up?
- How do you restore one file?
- How do you restore the full user account or move to a replacement machine?
- Which applications must be downloaded again rather than restored?
- Where are licences, receipts or installation details stored?
Write a short recovery card and keep a protected copy somewhere that does not depend entirely on the computer being recovered.
Do not put plaintext passwords, private recovery codes or encryption keys into a casual note merely for convenience. The card can say where protected recovery material is stored without reproducing the secret itself.
Mac users: test file recovery and know the full-machine path
Apple currently documents two different recovery scopes that are easy to blur together.
One file or an older version
Use Time Machine to browse and restore the specific item. This is the low-risk test to run regularly.
Rebuilding or moving to another Mac
Apple says Migration Assistant can transfer information from a Time Machine backup, including personal files, apps and user-account information. If macOS itself needs reinstalling, Apple’s recovery guidance treats that as a separate step before migration.
You do not need to perform a full migration every month. But knowing that file restore and machine migration are separate workflows prevents panic later.
A useful annual test for especially valuable data is to attach the backup drive, confirm it is readable, browse several older dates, and restore a small sample into a safe location.
Windows users: know which “backup” you are actually using
Windows currently has several recovery features with different jobs.
Windows Backup
Microsoft’s current Windows Backup app can protect supported folders through OneDrive and save supported settings, preferences and information about installed apps to the Microsoft account. During setup of a replacement or reinstalled PC, Windows can offer a saved backup associated with that account.
This is useful for migration, but it should not be mistaken for a full image of every application and every local file. Microsoft notes that some apps are represented by pins and may need to be downloaded again.
File History
File History is the clearer tool for testing restoration of personal files and older versions from an external drive or network location.
If you depend on it, recover a sample file now. A drive that has been silently disconnected for six months is not a useful backup simply because File History is still visible in Control Panel.
System recovery is a different problem
Windows also provides system-recovery mechanisms for OS, settings and recent system state. Those tools are not substitutes for keeping independent copies of personal data.
The recovery question should always be: what exact thing am I trying to get back — one file, an old version, my personal data, or the operating system?
Cloud sync is useful, but test the provider’s recovery behaviour
Cloud sync can be an excellent layer. It gives you another location, makes device replacement easier and often includes deleted-file or version-history recovery.
But “it is in the cloud” is too vague to be a plan.
Check:
- which folders are actually syncing;
- whether large or unusual files are excluded;
- how deleted-file recovery works;
- whether version history exists for the file types you care about;
- what happens when storage quota is full;
- whether you can access the account if the primary phone or laptop is lost.
Different services have different retention rules and account-recovery processes, so verify the provider you actually use rather than assuming all cloud storage behaves the same way.
A simple recovery scorecard
Give each important data set one point for each test it passes:
| Test | Point |
|---|---|
| A current copy exists outside the working device | 1 |
| You successfully restored a deleted sample file | 1 |
| You successfully recovered an older version | 1 |
| At least one useful copy is not continuously writable from the main device | 1 |
| Recovery instructions are available without the main device | 1 |
0–2: you have copies, but recovery is still mostly an assumption.
3–4: useful protection with one or two clear gaps.
5: you have evidence for the common failure modes this drill checks.
This is a practical checklist, not an industry certification. It does not prove resilience against every disaster, theft scenario, cloud outage or sophisticated attack.
What not to do during a practice drill
Do not create a real disaster just to prove you can recover from one.
Avoid:
- wiping the only working computer;
- deleting the only known-good backup;
- removing the last account-recovery method;
- disconnecting an encrypted drive without knowing the recovery key;
- testing ransomware or destructive malware on real data;
- moving irreplaceable files solely for the experiment.
Use a disposable test file and reversible actions. The point is to expose weak recovery paths safely.
Make it a quarterly 10-minute habit after the first drill
The first run takes about 30 minutes because you are learning the restore path.
Later checks can be much shorter:
- restore one recent file;
- restore one older version;
- confirm the offline/off-site copy is current enough;
- check that the recovery card still matches reality.
Run it again after a major change: new laptop, new cloud provider, new external drive, account migration, encryption change, or a large reorganisation of folders.
Backups drift as your digital life changes. Recovery tests catch that drift.
Conclusion
The useful question is not “Do I have a backup?”
It is “What can I restore, from where, and how do I know?”
A 30-minute drill gives you a much better answer. Recover one deleted file, recover one older version, identify whether your copies share the same failure, and keep a short recovery card somewhere you can reach without the main computer.
The boring moment when a test file successfully comes back is exactly what you want. It means the first time you learn the restore process is not the day the important file is gone.
Sources
Checked September 6, 2026:
- CISA — #StopRansomware Guide: maintain offline backups and regularly test backup availability and integrity
- Apple Support — Restore items backed up with Time Machine on Mac
- Apple Support — Restore your Mac from a backup
- Microsoft Support — Backup and restore with File History
- Microsoft Support — Back up and restore with Windows Backup
- Microsoft Support — Backup, restore and recovery in Windows