Backup discovery
Find and browse available recovery points.
- Filter
- Sort
- History
- Verification state
Recover
Recover Hyper-V workloads onto the host you actually have.
Recover helps locate backups, verify files, diagnose compatibility problems, remediate destination-host differences and retry interrupted restore workflows.
What problem does this solve?
Practical infrastructure work, made repeatable.
Restoring a VM is rarely just a file copy. The destination host may have different switches, missing ISO paths, saved-state issues or existing VM conflicts.
VyperForge brings discovery, verification, compatibility diagnostics and remediation into one recovery workflow so the operator can see what needs to be fixed.
Typical workflow
How the workflow usually runs.
Discover backupVerify filesCheck compatibilityResolve findingsChoose import methodRestore or register VMMonitor progressRetry if required
Capabilities
What Recover covers.
Restore methods
Choose the right import path for the destination host.
- Register existing VM
- Import new VM
- Restore existing VM
File verification
Validate backup content before trusting the restore.
- Integrity checks
- Archive validation
- Password-protected archives
Resumable recovery
Avoid starting from zero after interrupted transfers.
- Resume recovery
- Retry failed steps
- Progress tracking
Compare-VM diagnostics
Surface host compatibility issues before they derail the recovery.
- Missing switches
- Missing ISOs
- Saved state detection
- Hardware differences
- Recommended actions
Switch and adapter recovery
Remediate networking differences between source and destination hosts.
- Switch recreation
- Adapter mapping
- VLAN-aware decisions
File recovery
Restore individual files where a full VM restore is unnecessary.
- Browse backup tree
- Search
- Alternate destination
Host recovery
Restore supporting configuration when the host itself has changed.
- Host configuration
- Virtual switches
- Adapter settings
Key decisions
What to decide before you run it.
Recovery target
Choose whether to restore in place, import elsewhere, recover selected files or rebuild from known-good configuration.
Compatibility
Check host, storage and switch differences before import so recovery blockers are surfaced early.
Audit trail
Keep restore decisions visible so teams know what was recovered, when it happened and which source was used.
Operational notes
How this fits real work.
Recover focuses on controlled recovery rather than panic-driven file hunting.
The practical value is in understanding the restore path before the restore begins.
Product screens
See the workflow in VyperForge.
Product screens from the current beta build show how this capability appears in the desktop app.
Why VyperForge?
Practical advantages over native tools and loose scripts.
- Compatibility diagnostics are visible before import.
- Missing virtual switches and host differences become actionable findings.
- Interrupted recovery can be retried.
- Operators can choose the import method deliberately.
- VM, file and host-configuration recovery fit one workflow.
Example scenario
A practical way to use it.
A broken lab VM can be recovered to a new host while compatibility findings highlight switch or storage differences before the import runs.
Real-world examples
Where this helps.
- Recover a VM onto replacement hardware with different virtual switches.
- Restore a lab VM after destructive testing.
- Pull a small set of files without importing the full VM.
- Retry an interrupted recovery after a storage or network interruption.
Related platform areas