Verification
We boot your backups. So recovery day isn't a surprise.
Most backup products say "completed successfully" and stop there. We boot the actual image, capture a screenshot, log the result, and surface it in your dashboard. Real proof — not a hash. Free local Hyper-V verification on cached recovery points uses your own hardware at no extra charge; cloud-side Boot Verification — automated boot tests on AWS for cloud DR images — is available as the paid Verification Evidence Pack add-on.
How it works
How a boot test works
The same five steps every verification, whether it runs free on your local Hyper-V or as a paid cloud-side test on AWS: launch the actual image, let it boot to the login screen, capture a screenshot, log the result as evidence, then terminate so nothing lingers.
Launch → Boot → Screenshot → Log result → Terminate — real proof your backup actually boots.
Two verification surfaces
Free on your hardware. Audit-ready in the cloud.
Local verification is included; cloud-side verification is the premium audit-ready bundle. Every backup verified, every recovery point provable.
Free local Hyper-V verification
For local DR images and cached recovery points, BigMind launches the image on your machine’s Hyper-V, lets it boot to login screen, captures a screenshot, terminates. No cloud cost. Included in DR Plus, DR Pro, and the cached side of Resilience tiers. Cadence: DR Plus monthly, DR Pro every image, Resilience cached/local images per tier policy.
Paid cloud-side Verification Evidence Pack
For cloud DR images, BigMind launches the image as an EC2 instance, boots to login, captures a screenshot, terminates. Result + screenshot stored as compliance evidence with optional audit-bundle export. Available as a paid add-on. Cadence: Resilience DR-Only quarterly, Resilience Standard monthly, Resilience Pro weekly.
An actual booted screenshot from AWS. Stored as audit evidence.
For cloud DR images, the booted screenshot and result are stored as compliance evidence with optional audit-bundle export — exactly what auditors and compliance officers ask for. The Verification Evidence Pack: every backup verified, every recovery point provable.
- Booted screenshot stored as compliance evidence
- Optional audit-bundle export for SOC 2 / HIPAA
- Cadence by tier: DR-Only quarterly, Standard monthly, Pro weekly
Click to enlargeBeyond the boot test
Three more layers of proof.
Hash-based image integrity
On top of boot verification, every backup image is hash-validated end-to-end. Chunk hashes verified, manifest signatures checked, dedup chain reconstructed. If any byte is corrupt, we surface it before you need it.
Cross-region verification
On Continental Region tier (Pro+), we verify images by reading from a different AWS region than the one they were written to. Catches cross-region replication issues that single-region verification can’t.
Quarterly restore drills
Schedule a recurring restore drill — Cloud Desktop boots a representative backup, runs a checklist (logon, app open, data query), generates a screenshot + audit log, terminates. Auditors love this. You’ll love it when you don’t have to manually demo recovery for SOC 2 / HIPAA audits.
When verification fails
Surface, fallback, log.
Image flagged in Recovery Shield
A failed verification is surfaced in your dashboard the moment it happens, not on recovery day.
Email alert (Plus and above)
You’re notified directly so a bad image never sits silently in the chain.
Last-known-good fallback
The most recent verified image is surfaced as the fallback, and the chain falls back to a known-good ancestor rather than continuing forward on a corrupt base.
Audit log records the failure
Every failure is logged for compliance investigation — a paper trail, not a silent retry.
Real proof. Not a hash.
We boot every backup, capture a screenshot, and log the result — so recovery day is never a surprise.