Instant VM Recovery

Boot VMs directly from compressed and deduplicated backups

Recover VMware and Hyper-V

Recover VMware and Hyper-V
VMs in seconds

Migrate the booted VM

Migrate the booted VMs
to production environment

Use booted VM for sandbox

Use booted VMs for sandbox
testing or recovery

The Fastest VM Recovery

When a business-critical VM goes down, every minute of downtime can be costly and painful. With NAKIVO Backup & Replication, you can recover entire VMware and Hyper-V VMs from their backups within minutes. The Flash VM Boot feature enables you to boot the VMs directly from compressed and deduplicated VM backups, without recovering the entire VMs first. This feature works right out of the box without any special setup. Just choose a VM backup, a recovery point, and a recovery location (a host, a resource pool, or a cluster where you want to run the recovered VM), then push a button – the VM is booted in no time.

Once the VM is running, you can migrate the VM to production for permanent recovery. What’s important is that the backup from which the VM is booted is not affected. Changes you make to the running VM do not modify or remove data in your VM backup.

Why Use Flash VM Boot

In addition to the VM recovery capabilities, the Flash VM Boot feature also has several helpful functionalities. For example, you can:

  • Access files, folders, and application objects of any application on any OS
  • Test system updates and application patches before applying them to your production VM
  • Verify the VM backup to ensure that the OS and applications run properly
  • Copy a VMDK or VHDX file and then delete the virtual machine

How Flash VM Boot Works

NAKIVO Backup & Replication consists of two main components. The Director is the management instance, while the Transporter performs actual data protection and recovery tasks. By default, both components are automatically installed to enable all features out of the box.

When you run a Flash VM Boot job, the Director creates a new VM without any disks on the target server, then commands the Transporter to expose the VM disks from the Backup Repository as iSCSI targets. Finally, the Director mounts the exposed disks to the newly created VM.

Recovery diagram

This process is fully automated and takes only seconds to complete, after which the VM OS boot is started. Once booted, the VM can be migrated to the production environment using the hypervisor’s native live migration feature.