VM recovery includes the following methods:
- Instant Recovery (IR) — to instantly recover VMs directly from the compressed and deduplicated backup files. When you perform Instant Recovery, Veeam Backup & Replication mounts recovered VM images to a host directly from a backups stored on a backup repository. You can restore VMs to VMware vSphere or Microsoft Hyper-V environments. For more information, see Performing Instant VM Recovery of Workloads to VMware vSphere VMs and Performing Instant VM Recovery of Workloads to Hyper-V VMs.
Instant Recovery helps improve recovery time objectives (RTO), minimize disruption and downtime of production workloads. However, Instant Recovery provides for VMs “temporary spares” with limited I/O performance. To provide the recovered VMs full I/O performance, you must finalize Instant Recovery — migrate the recovered VMs to production environment. If you do not want to migrate the recovered VM, you can stop publishing it. This removes the recovered VM.
Use Instant Recovery for for tier 1 VMs with little tolerance for business interruption and downtime. Besides disaster recovery matters, Instant VM Recovery can also be used for testing purposes.
- Entire VM restore — to recover entire VMs. When you recover VMs, you extract VM images from backups to the production storage. Entire VM restore takes more resources and time to complete than Instant Recovery but recovers VMs with full I/O performance. You also do not need to perform additional steps to finalize the recovery process.
Use entire VM restore for VMs that require full I/O performance as soon as they are recovered and that tolerate some downtime.
- Staged restore — to run executable scripts for VMs before recovering them to the production environment. Staged restore is a part of entire VM restore.
Use this option when you need to make sure that recovered VMs do not contain any personal or sensitive data.
- Restore to Microsoft Azure — to restore workloads of different data protection environments as Microsoft Azure VMs.
- Restore to Amazon EC2 — to restore workloads of different data protection environments as EC2 instances.
- Restore to Google Compute Engine (GCE) — to restore workloads of different data protection environments as Google VM instances.