Backups are your last line of defense. Make sure you can rely on your backup when you need it most.
Backups can be corrupted over time due to storage failure or they can be the target of malicious actors. This is why cyber insurance providers require that you regularly test your backups. With the Test Restore feature, you can fully automate regular testing of your backups and obtain a simple report of the test outcome.
Test Restore
BackupAssist Classic provides onsite, offsite, online and offline backups including Windows system drive images, and application & file backups. This gives you multiple recovery options when you need them the most. Back up to USB disk, NAS, iSCSI, cloud - it's easy to be cyber-resilient and never pay a ransom!
BackupAssist Classic Test Restore
- Your backups might be corrupted and you wouldn’t know
- Testing your backups regularly involves costly manual labor
- Organizations can grind to a halt and be at the mercy of cyber criminals

BackupAssist Classic Test Restore
- You will know if your backups are corrupted, allowing you to take action before it's too late
- Testing of your backups is fully automated
- You will have evidence of your successful regular test restores
HOW IT WORKS
Automated Backup Testing
Schedule a weekly or daily job to test the latest available backup of a given backup job. You simply choose which days of the week you would like to run the test restore. You can optionally limit how many files to test and the time spent running the Test Restore.
This is a fully automated process that checks the files in the latest backup.
Reading and Integrity Tests
Each file is tested on two levels.
The reading test checks that files can be successfully accessed and read in full from the backup location.
The integrity test involves generating checksums that are saved with the backup, and then later using them to confirm that the files have not changed since the backup.
Simple report of results
A report is created after each test restore execution, providing evidence that testing of a particular backup has occurred, along with its results.
The report includes a simple listing of the number of files tested, how many passed and how many failed, along with the failure type.
View Test Restore Logs

Backup Engine Support Matrix
File reading test | File integrity test | |
---|---|---|
File Protection | Yes | Yes |
Cloud Protection | Yes | Yes |
Advanced System Protection (v12 and newer) | Yes | Yes |
Legacy System Protection | Yes | No |
File Archiving and Rsync | No | No |
Test Restore Backwards Compatibility Table
Backups created with v11 or earlier | Backups created with v12 or newer, using a v11 backup job | |
---|---|---|
File Protection | Supports file reading test only | File hashes will be calculated on new and changed files. These files will support integrity testing, while other files will support reading tests only. |
Cloud Protection | Supports file reading and file integrity tests | Supports File reading and integrity tests |
v12 Advanced System Protection | Not applicable | Not applicable |
Legacy System Protection | Supports file reading test only | Supports file reading test only |
File Archiving and Rsync | Not applicable | Not applicable |
Frequently Asked Questions
How often should I run Test Restore?
We recommend that you run Test Restore at least once a week, e.g. during the weekend.
Can I test existing backups created before the v12 upgrade?
Yes, you can test backups created with v11 and earlier – see Test Restore Backwards Compatibility Table.
Which backup engines support file integrity testing?
See Backup Engine Support Matrix.
Do I need a separate license to run Test Restore?
No, the Test Restore feature is included with every BackupAssist core license.
Does running Test Restore successfully mean that my backups are guaranteed to be uncorrupted?
If you run a successful full test restore, backups are guaranteed to be uncorrupted at the time the test was completed.
Does Test Restore require any additional disk space to temporarily store the files into?
No, the Test Restore feature does not need any disk space to store any temporary files.