If they are not, recovery may not work properly, but you can still try. In the next panel, Iperius will show a “Compatibility Report”, detecting if there are incompatibilities between the source Hyper-V host and the target Hyper-V host (the one to which we are connected and where the VM will be restored), and indicating whether the detected issues are solvable. Then you have to configure the other two important options: whether to restore the virtual machine (and therefore the disks) in the default Hyper-V folder or in a specific folder, and whether to generate a new ID for the restored virtual machine (necessary in the case of a virtual machine with the same name already exists on the Hyper-V host).

This allows us to make a granular restore of a virtual machine to a specific time. Select the Full backup or one of the incremental or differential backups to restore and click on “Next”.Įach backup will have its own date and size. It must obviously be an accessible path (if it is a network path it may be necessary to specify an account for automatic authentication in the shared folder).

Then select the folder containing the backup of the virtual machine made by Iperius. You can see in the image below the simple configurations necessary to start the restore of a Hyper-V virtual machine from an RCT backup or from a direct copy of the virtual machine files:įirst, you need to create and / or select a connection account to a Hyper-V host (in this case we are talking about a local host) and connect. See also: Incremental and differential Hyper-V backup (RCT) with Iperius So there are just as many ways to recover Hyper-V virtual machines. As we can read in the specific Hyper-V backup tutorial, there are 3 backup modes: the incremental and differential one via block level RCT, the one with direct copy of the individual virtual machine files, and the one with block level image (compatible with Windows Server Backup).

Iperius has powerful backup and restore features of Hyper-V virtual machines.

Iperius backup hyper v