RestorSignal — Documentation

Independent restore verification for backups: methodology, evidence, security.

RestorSignal verifies that a backup can actually be restored. It is not a backup solution, and it never replaces whatever backup tool a client already runs — Veeam, Proxmox Backup Server, Synology Hyper Backup, a scheduled SQL dump, or any other mechanism specific to that client. RestorSignal steps in afterward, on an artifact that already exists, to establish what can genuinely be recovered from it.

One principle shapes everything else in this documentation: it is always the client, the IT department, or the MSP who chooses which artifact to test and who triggers the test — even when that trigger is automated on the client side, such as a scheduled cron job. RestorSignal never connects to a backup console to pick "the latest backup" itself, and it never decides on its own which restore point is representative. That choice always remains the client's.

RestorSignal then acts as an independent verification layer: the system that restores, observes, and qualifies the result is separate from the system that produced the backup, and separate from whatever declared the backup successful in the first place. A "backup successful" status reported by backup software is not, on its own, proof of restorability — see Why test restores.

Two execution modes exist depending on the client's context: a local runner, executed inside the client's own environment, and a disposable environment, provisioned temporarily for the duration of the test and then destroyed. Both are covered in detail in the methodology section.

Finally, the outcome of a RestorSignal verification is never reduced to a bare PASS/FAIL flag shown without context. Every run is recorded individually, and RestorSignal seals a documented evidence package at most once per context and per calendar day, consolidating that day's runs: the components used, the criteria applied, the facts observed, and the limits of what was actually verified. That reproducible, traceable package is what the service delivers — not a generic statement of trust.

Where to start

• Why test restores — what "backup successful" does not prove, and what independent verification changes.
• The verification cycle — the concrete steps of a RestorSignal run, from selection to the resulting evidence package.
• Data transfers — what RestorSignal receives, what it does not, and how that stays under the client's control.