Restore verification

Measure whether the recovery plan survives a real restore.

Time a representative restore from the independent recovery path, record the age of the recovered point, and verify that credentials, retained versions, integrity, and dependencies work together. Save each completed run locally as dated evidence.

Measured restore record

Replace a planned recovery window with evidence from a timed restore.

Record the amount restored, elapsed time, recovery-point age, and the checks that proved the data was actually usable. The result projects the measured rate across the priority restore set.

View assumptions and sources →

The values below are editable planning baselines. Change the few inputs you know; open Advanced assumptions only when they change your decision.

Measured throughput——

Projected priority restore——

Achieved recovery point——

Projected recovery time——

Evidence completed——

Verification state——

Usability evidence

A completed transfer is not yet a completed recovery.

Check each item only after the restore path has demonstrated it. The saved record preserves these states on this device through the shared plan-history system.

Recovery credentials were independently availableThe restore did not depend on credentials stored only inside the failed primary system.Representative files opened successfullyUse more than a file listing: open the restored formats that matter.An older retained version was restoredConfirm that version history can produce the recovery point the plan promises.The restored sample passed its usability checkUse an integrity check, application-open check, or both as appropriate for the data.Application and encryption dependencies were checkedInclude databases, keys, service order, and mark genuinely irrelevant dependencies as checked.The measured procedure and missing pieces were recordedKeep the steps with the recovery path so the result can be repeated under pressure.

First verification gap

—

Measured recovery record

Save the evidence, not a promise.

The record contains only objective sizes, timing, target comparison, and completed check states—no filenames, credentials, or free-form notes.

Next decision

Review the restore test steps Return to recovery planning

Plan tools

Keep this useful version close, shareable, and easy to revisit.

Reset inputs

Measured rate

The test converts restored decimal TB and elapsed minutes into observed MB/s, then projects that rate across the full priority restore set.

Objective proof

Recovery-point age is compared with RPO; projected full restore time is compared with RTO. Neither receives a pass before a timed test exists.

Local record

Explicit saves reuse the site-wide local plan history. The URL stores numeric results and check states, without filenames, credentials, or notes.