This episode covers Veeam's strengths on the restore side: Instant Recovery (running a VM directly from backup without a full restore) and migrating back (re-host), plus granular restores such as Instant File Recovery and application items via Explorers. You will also learn automatic verification with SureBackup and Instant VM.

So far we have focused on the production side of backups: creating jobs, retention, and copies. In episode 8 we flip the perspective — restore. Because the main purpose of a backup is not storing data, but bringing it back quickly and correctly when needed.
This is exactly where Veeam excels: from running a full VM in minutes directly from backup (Instant Recovery), to recovering a single file or a single email (granular restore), plus automatic verification that backups can really be restored (SureBackup).
Instant Recovery lets you run a VM directly from the backup files (.vbk/.vib) without waiting for a full restore. Veeam publishes the VM to a hypervisor host, and each disk block is read on demand from the backup. The impact: RTO drops from hours to minutes.
When to use it:
From the console: right-click the restore point → Instant Recovery, choose the host and resources, and the VM boots immediately. The same via PowerShell:
$rp = Get-VBRRestorePoint -Name "WebServer-01" | Select-Object -First 1
Start-VBRInstantRecovery -RestorePoint $rp -Server (Get-VBRServer -Name "esxi01")Instant Recovery is only temporary — the VM runs from slow backup storage. The next step is migrating back: moving the VM back to production storage (vMotion). Veeam guides you through Instant Recovery → Migrate VM: the VM is cloned to the target storage then released from backup mode. The result is a "proper" VM running from normal storage.
Not every restore needs a full VM. Instant File Recovery browses files inside a backup (Linux or Windows) and copies the ones you need — without powering on the VM. This is the fastest way to recover a single deleted configuration file:
Start-VBRWindowsFileRestore -RestorePoint $rp
# Then in the restore session: browse + copy the target fileVeeam provides per-application Explorers for granular item restores:
In practice: open the restore point in an Explorer → select items → restore to production or export to file. We cover the details in episode 10.
Tip
Restore rule of thumb: the smaller the need, the faster the path. One file → Instant File Recovery. One email → Explorer. One database → Explorer for SQL. A whole VM → Instant Recovery. Never restore a full VM just to get a single file — you are wasting time and storage.
SureBackup answers the most important question: "can this backup actually be restored?" It powers on VMs from backup in an isolated sandbox, runs test scripts (ping, port checks, applications), then shuts the VMs down. The results are reported as a verification job.
The SureBackup flow:
Restore point ──▶ Virtual Lab (isolated) ──▶ Test script ──▶ Success/FailureFor lighter verification, Instant VM runs the VM from backup without a full Virtual Lab — a quick check that the VM boots and the disks are consistent. Suitable for daily backup verification that does not need deep application tests.
Important
A backup without verification is no guarantee. Veeam calls verified data "recoverable". Make SureBackup a routine weekly job (episode 20 links it to monitoring). Knowing a backup is broken before a disaster is one of Veeam's biggest selling points.
| Need | Method | Time |
|---|---|---|
| Full VM / disaster | Instant Recovery + migrate | Minutes |
| A single file | Instant File Recovery | Seconds-minutes |
| Application items (email, DB row) | Explorer (SQL/Exchange/AD) | Minutes |
| Routine verification | SureBackup / Instant VM | Scheduled |
After this episode, make sure:
Key takeaways:
In the next episode, episode 9, we will cover replication & failover — replicating VMs to another host for DR, Failover Plans (failover, failback, test failover), Continuous Data Protection (CDP) for minimal RPO, and failover automation via scripts and Veeam Disaster Recovery Orchestrator. From recovery toward business continuity!