What is a restore test?
A restore test is a scheduled exercise that restores data or a whole system from backup to prove it can be recovered and used. It checks that the copy is complete, that it opens, and how long the restore takes. A backup job reporting success is not the same proof.
Full guide: Restore test checklist: is the recovered work usable Service: Disaster Recovery
A restore test answers the only question that matters about a backup: can we get the data back, in a usable state, in the time we planned for? Backup software reports whether a job ran. It does not report whether the database inside the backup opens, whether the right folders were selected, or whether anyone still has the encryption key. Those failures stay hidden until a restore is attempted, and the worst time to attempt the first one is during an incident.
Tests come in sizes. A file-level test restores a sample of documents and opens them. An application test restores a mailbox, a database or a SharePoint site and checks that it works. A full-system test restores or boots an entire server, usually in an isolated environment so it cannot collide with the live one. Each test should record what was restored, from which copy and date, how long it took, what failed and who checked the result. The measured time is the evidence for the recovery time objective; the age of the restored data is the evidence for the recovery point objective.
Federal guidance treats testing as part of having a backup at all. NIST's contingency planning guide says backup tapes should be tested regularly to ensure that data is being stored correctly and that files can be retrieved without errors or lost data. CISA's ransomware guide tells organizations to regularly test the availability and integrity of backups in a disaster recovery scenario. A dated test record is also a far better answer to an insurer or auditor than a screenshot of green check marks.
Reviewed by Joel Baum, Founder. Our editorial standards.
Why it matters for a small business
Backups fail quietly. A job can report success for months while skipping the one folder that matters, writing to a full disk or encrypting with a key nobody kept. Businesses discover this on the day they need the data. A restore test moves that discovery to an ordinary Tuesday, when it costs an hour instead of the company. If your provider has never shown you a dated restore result, with the time it took, you do not yet know whether you have backups.
How NetSys runs restore tests
NetSys runs the backup jobs for managed clients, checks them daily and tests restores on a schedule for each system, with the date, scope and result recorded. For Microsoft 365, each quarter we restore a sample of mailboxes, files and a full site to a test location and write down the result. Failover exercises for Tier 1 systems record the measured recovery time.
The same rule governs a change of provider. When a business moves to NetSys, our backup runs alongside the outgoing provider's and no cutover date is set until a real restore has passed: a file and a full system. Our disaster recovery service quotes recovery times as tested numbers, not vendor specifications.
Sources
Checked on November 22, 2026.
- NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems, National Institute of Standards and Technology (NIST)
- #StopRansomware Guide, Cybersecurity and Infrastructure Security Agency (CISA)
- NIST SP 800-84, Guide to Test, Training, and Exercise Programs for IT Plans and Capabilities, National Institute of Standards and Technology (NIST)
- Protecting Data from Ransomware and Other Data Loss Events: A Guide for Managed Service Providers to Conduct, Maintain, and Test Backup Files, National Institute of Standards and Technology (NIST)
Restore Test: FAQs
How often should backups be restore tested?
On a schedule set by how critical each system is, and again after any major change such as a new server or a migration. A workable pattern is a sample of files and mailboxes every quarter and a full-system restore at least once a year for the systems the business cannot run without. Write the interval into the recovery plan and keep the dated results.
What is the difference between a backup verification and a restore test?
Verification is an automated check by the backup software that the backup file was written and is readable. A restore test goes further: data is recovered to a real or isolated system and a person confirms it opens and works. Verification catches a corrupt file; only a restore test catches a backup that is intact but useless.
What should a restore test record?
The date, the system and data restored, which backup copy and restore point were used, where it was restored to, how long it took, what went wrong and who confirmed the result. Those records are the evidence an insurer or auditor will ask for, and the time taken is your measured recovery time.
Does a restore test disrupt the business?
It should not. Files are restored to a separate location and full systems to an isolated network or a virtual machine, so nothing touches production. The only disruption worth planning for is the time of the person who checks that the restored data is right.
More terms
Discuss disaster recovery for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.
