The main new feature in version 7.0 are incremental and differential Hyper-V backups for Windows 10, Server 2016 and Server 2019. These have challenges in larger environments, and this is not a preferred way to backup large numbers of mailboxes. On the Exchange side, backups are done to PST files. Note that this type of restore can be done on any virtual disk (not necessarily from an Iperius backup) and can be done with any Iperius installation, including the free version.įor whole VMs, the restores can be done to any host. Because Iperius protects data in its native format (VHD/VHDX for Hyper-V and VMDK for VMware, for example), you can easily mount a drive and extract a file or a folder, for either Hyper-V or VMware. Restoreīackup is useless if you can't restore your data. Iperius also supports replication of VMs between datastores and between hosts with no agent required. It supports both incremental and differential backup (CBT/VDDK) and connects to vCenter for backup or restore. Supported versions include ESXi 4.x, 5.x, and 6.x, along with ESXi free. On the VMware side, the story is more comprehensive. I could add individual hosts and see their VMs but not the overall cluster. I enabled this option, which saved about 50% disk space compared to the full size of my four production VMs.įor Hyper-V, Iperius isn't cluster-aware. One of the options was to use a zip utility to compress the backups. For instance, web hooks and maybe even an API would be good options so that you could set Iperius to let you know the status of your backup jobs in Slack or your IT service desk software. This was very straightforward, but I'd like to see additional notification beyond email.

Iperius backup service