Division of responsibilities

Who does what between the backup solution, the client, and RestorSignal.

A RestorSignal verification always involves three distinct actors, each with a precise scope of responsibility. Conflating these scopes is the most common source of misunderstanding about what the service actually does.

Backup solution

The client's backup solution — Veeam, Proxmox Backup Server, Synology Hyper Backup, a SQL dump script, or whatever other tool is already in place — remains solely responsible for producing backups: reading source data, transferring it, writing it to the destination medium, and managing the retention and rotation policy for restore points. RestorSignal never intervenes in this process at any point, never modifies any backup configuration, and never replaces any of its functions. The artifact this solution produces is the starting point of RestorSignal's work, never its scope.

Client / IT department / MSP

The client, its IT department, or the MSP supporting it retains full control over what gets tested. It is the one that selects the artifact or restore point to verify, that triggers the test's execution — manually or through a schedule it defines itself — and that ultimately decides what gets submitted to RestorSignal. This decision can be made case by case or governed by a recurring policy, but it always remains, in every case, a client-side decision.

RestorSignal

RestorSignal restores the artifact designated by the client inside a dedicated test environment (a local runner or a disposable environment), observes what genuinely happens during that restore, applies the control criteria defined for the scenario, and documents the resulting outcome — whether that is a PASS, a FAIL, or an ERROR. This work produces a traceable evidence package: the components used, the criteria applied, the facts observed, and the explicit limits of what was covered.

RestorSignal never chooses the backup to test. This principle holds true even when triggering the test is automated on the client side, for instance through a scheduled cron job that regularly submits an artifact for verification. Automating the trigger does not change who decides: the automation rule itself — which artifact, at what frequency, under what criteria — is defined by the client, not by RestorSignal. RestorSignal runs the test on what is submitted to it; it never browses a backup console, a PBS datastore, a NAS, or a Proxmox interface to pick an artifact to verify on its own.