Free tools Windows power users keep installed
One-click scans. No signup required.
Do not delete your only report. To find out whether an automated backup can actually protect you, preserve the original, create a disposable test copy, and restore that copy to a separate location. A successful backup notification proves that a job ran; it does not prove that the right version can be recovered, that the recovered file opens, or that its contents are usable.
A controlled restore test gives you that evidence without risking production data. It also tells you how much information you could lose and how long recovery would take, so you can choose an automation schedule that matches the report’s value.
As an Amazon Associate I earn from qualifying purchases.
Why a completed backup is not proof of recovery
Backup systems can report success after copying files, yet recovery can still fail. The selected version might be older than expected, the backup repository might be unavailable, credentials may no longer work, or the restored file may be damaged or incomplete. A job log usually answers only one question: did the process run? A restore test answers the question that matters after a mistake, hardware failure, or ransomware incident: can the report be returned in a usable form?
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →CISA’s #StopRansomware Guide says to “Test backup procedures on a regular basis.” Its guidance also calls for testing backup availability and integrity in a disaster-recovery scenario. That distinction is important: availability means you can reach the copy, while integrity means the data is intact enough to use.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
What the test must prove
A useful test has a defined target and observable pass conditions. Before touching any copy, write down:
- Recovery point: the exact report version or date you expect to restore.
- Recovery time: the longest acceptable interval from starting recovery to having a usable report.
- Expected content: a few known figures, sections, attachments, or other details that should be present.
- Restore destination: a separate folder, drive, or account that cannot overwrite the working report.
The restored file should be present at the destination, have the intended version, open in the application normally used for it, and contain the expected information. If the report relies on linked files or attachments, check those dependencies as part of the test rather than assuming they were included.
RPO and RTO turn “good enough” into a decision
NIST’s National Cybersecurity Center of Excellence describes two planning measures: the recovery point objective (RPO) is the maximum acceptable amount of data loss, measured backward from the incident; the recovery time objective (RTO) is the maximum acceptable time before the report is usable again. They determine how often automation should run and how recovery should be organized.
For example, if losing more than one day’s edits would be unacceptable, a weekly job cannot meet that RPO. If the report must be available within two hours, a process that requires finding a disconnected disk, downloading a large archive, and manually rebuilding links may not meet the RTO. Measure the real restore time during the test instead of relying on a provider’s job duration.
How to perform a safe restore test
- Choose a meaningful report and target version. Pick a report whose loss would cause real disruption. Record its current name, location, version or date, and the information you will use to verify the result. Decide the acceptable RPO and RTO before starting.
- Protect the original. Keep the live report untouched. Make a duplicate in a clearly labelled test location, or use a non-production copy supplied for testing. Confirm that the original can still be opened and that the test copy is the one you intend to remove or alter. Never simulate deletion by deleting the only copy.
- Run the proposed backup or select the version automation will use. If automation has not been enabled, execute the same backup process manually or use its test mode. If it is already running, note the backup timestamp and select the recovery point that should satisfy your target RPO.
- Simulate loss only on the disposable copy. Remove or rename the test copy if deletion is part of the scenario. A rename can be safer for a first test because it is reversible and still shows whether the backup is independent of the original path. Do not remove the source report or any other production data.
- Restore to a separate destination. Use a new folder, drive, or account. Do not restore over the live report, because an incorrect version could overwrite good data and make the test ambiguous. Record when the restore starts.
- Verify the result. Confirm that the file appears at the destination, has the expected name and version, opens without an error, and contains the known figures or sections you recorded. Check the file’s date or revision information where the format provides it. If the report uses attachments, verify that the required attachments are available too. Record when the file becomes usable.
- Document and correct. Save the backup version, destination, start and finish times, checks performed, and any errors. If any check fails, stop treating the automation as reliable. Correct the schedule, permissions, retention, storage, or restore procedure, then repeat the test from a clean disposable copy.
- Schedule the next test. Set a recurring restore exercise and run another one whenever the report format, storage location, backup software, account, permissions, or automation schedule changes materially.
Use a pass/fail checklist, not a green status icon
| Check | Pass evidence | If it fails |
|---|---|---|
| Backup point | The selected timestamp or version matches the recovery point you planned. | Review scheduling, time zones, retention, and version selection. |
| Availability | You can authenticate and reach the backup location without an unavailable device or expired credential. | Repair access, document recovery credentials, and test again. |
| File presence | The restored report exists at the separate destination and has the expected filename or identifier. | Check selection filters, paths, and whether the backup included the report. |
| Openability | The normal application opens the restored file without an error or repair prompt. | Investigate corruption, incomplete transfers, encryption keys, and application compatibility. |
| Content integrity | Known figures, sections, and required related files are present and readable. | Review whether the backup captured dependencies and whether the chosen version is correct. |
| Timing | Measured restore time is within the RTO you set. | Change the storage or process, reduce the recovery set, or revise the RTO with an explicit business decision. |
Local external drive or cloud copy?
CISA identifies a secure external hard drive and a properly vetted cloud service as valid backup destinations. The key difference is not the label “local” or “cloud”; it is whether a usable copy remains protected from the same event that affects the live system, and whether you can still access the credentials needed to restore it.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
| Consideration | External drive | Vetted cloud service |
|---|---|---|
| Exposure to a compromised computer | Can be reached while connected. Disconnect it when it is not actively backing up. | Protected by the service’s account, network, and security controls; a compromised account can still expose it. |
| Offline protection | A disconnected drive can provide an offline copy. | Offline status depends on the service’s architecture and your account settings; verify rather than assume. |
| Access requirements | Requires the drive and any encryption key or password. | Requires the account, authentication method, and any recovery key or password. |
| Restore time | Depends on finding the drive and reading it; measure it during your test. | Depends on account access, network bandwidth, and the amount of data; measure it during your test. |
| Operational duty | Connect only for the backup or restore, store it safely, and protect encryption keys. | Review account security, retention, export or restore options, and recovery credentials. |
CISA specifically warns not to leave an external drive connected when it is not actively backing up: ransomware that reaches the computer may also delete or corrupt a continuously connected backup. Store encryption recovery keys and passwords safely; an inaccessible encrypted backup is not a practical recovery copy.
Build resilience with the 3-2-1 pattern
NIST’s NCCoE guide, Protecting Data from Ransomware and Other Data Loss Events (April 2020), describes the 3-2-1 approach:
- 3 copies of important files: one primary copy and two backups.
- 2 different media types, so one failure mode does not remove every copy.
- 1 off-site copy, separated from the location where the report is normally used.
This is a resilience design, not a substitute for a restore test. Three unreadable copies are still a recovery failure. Test at least one copy from each backup path that you would rely on during an incident, and make sure the off-site copy is actually reachable with the credentials and keys available to the people responsible for recovery.
How often should you test?
There is no single interval that fits every report. Base the cadence on the report’s value, how often it changes, the acceptable RPO and RTO, and the likelihood that storage or permissions will change.
New Zealand’s National Cyber Security Centre gives practical example intervals: test restoring a single file at least once a quarter and test a full restoration at least once a year. Those are the NCSC’s examples, not a universal legal requirement. A frequently changing financial or operational report may justify more frequent checks, while a rarely changed archive may need a different schedule. Run an additional restore after a major migration, account change, backup-software update, retention-policy change, or report-format change.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Common failure modes and the fix
The backup job is green, but the report is missing
Check whether the report’s folder was excluded, renamed, moved, or outside the selected scope. Confirm that the backup timestamp was after the last expected edit and that retention has not removed the required version. Correct the selection or schedule, then create a new recovery point and test it.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsThe restored file opens, but it is the wrong version
Compare the restored timestamp or revision with the target you recorded. A successful restore of an older version is not a successful test of your chosen RPO. Review time zones, snapshot labels, retention rules, and version-selection defaults.
The file is present but will not open
Do not overwrite the original while troubleshooting. Test the same recovery point in a separate location, verify that decryption keys are available, and check whether the application version can read the file format. If repeated restores fail, treat the backup as unusable until a new backup path passes the openability check.
The report opens but information is incomplete
Identify which content is absent: embedded objects, linked files, attachments, or the latest edits. Determine whether those items live outside the report’s backed-up path. Expand the backup scope or include the dependent data, then repeat the complete verification.
You cannot access the backup during the exercise
Record whether the problem is a disconnected device, unavailable network, expired account, missing encryption key, or insufficient permission. Recovery credentials and keys should be stored securely before an emergency. Fix access controls and run the restore again; do not mark the process successful because the backup exists somewhere.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
The restore takes longer than allowed
Compare the measured duration with the RTO. You may need a different storage arrangement, a smaller recovery set, a more accessible copy, or a formally approved change to the RTO. Make the decision explicit rather than silently accepting an outage longer than the business can tolerate.
Keep backups outside the threat’s reach
Ransomware may search for backups that are reachable from the infected system and delete or encrypt them. CISA therefore recommends offline, encrypted backups of critical data and regular tests of availability and integrity. A disconnected local drive is one way to create separation; a properly vetted cloud service can be another, provided its account and recovery controls are protected. Use more than one location when the report is important, keep encryption keys available to authorized recovery staff, and test the exact copies you expect to use.
When industrial systems need extra controls
For operational technology, the safety and availability consequences of a restore can be more severe than for an office report. NIST’s OT Backup Quick Start Guide (June 17, 2026) states: “Effective backup management in an OT environment involves integrating backups into the change management process, creating them regularly, testing them, and reviewing them during recovery exercises.” Apply the same preserve-test-verify principle, but coordinate with safety, maintenance, and change-control procedures before altering an operational system. Do not perform a live deletion simulation where it could affect a process or create a safety hazard; use an approved test environment or recovery exercise instead.
What to record after every exercise
- The report identifier, source location, and expected recovery point.
- The backup set or timestamp used.
- The person or role that performed the restore.
- The destination and whether the original remained untouched.
- Availability, opening, content, dependency, and timing results.
- Errors, corrective actions, owners, and the date of the next test.
These records make a failure actionable and reveal drift over time. If a restore succeeds only when one person remembers an undocumented step, the process is not yet dependable.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11The practical answer to “Should I delete the report first?”
Delete only a disposable test copy, and only after the original and an independent backup are protected. The meaningful test is not the deletion itself; it is whether the chosen backup can be found, restored somewhere safe, opened, and verified against the version and content you expected. Run that exercise before trusting automation, repeat it at a risk-appropriate interval, and change the workflow whenever the evidence shows that recovery would miss your RPO or RTO.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
