"I have a backup" and "my backup works" are not the same statement. Most companies that lose data did have a backup — it simply would not open. A corrupted archive, an incomplete dump, a file that never arrived at the destination: all of these can display as "successful". That is why verification is a separate step.
No credit card required · 14-day free trial
One check is never enough; each layer catches a different kind of failure.
A SHA-256 digest is computed and stored for every backup, revealing any corruption.
The archive is checked for a clean close and readability, catching half-finished packaging.
We confirm the file genuinely exists in the storage target — the "recorded but missing" case is flagged.
Sample restores are attempted periodically so problems surface before the bad day does.
Every one of these can hide behind a "successful backup" label.
If an expected component comes back empty the backup is not marked successful. "0 files backed up" is a warning, not a success.
When the server runs out of space, packaging is cut short — and that is reported separately.
If the dump could not be taken, the backup is incomplete; a files-only backup is not silently substituted.
If IMAP connected but returned zero messages you are told, rather than losing data quietly.
If a scheduled run did not happen an alert is raised, so you are not left unprotected for weeks.
If writing to the destination did not complete, the backup is not counted as finished.
The most insidious bug in backup software is a check that reports success while doing nothing. Such a check gives you confidence without protection — and delays the moment you notice a real problem.
So our principle is this: "0 problems found" and "0 records scanned" are never the same thing. If a check could not verify anything, it does not report success; it marks the state as unknown.
Integrity, presence and drill checks are enabled on every plan. 14 days free.
Create Free Account