Protecting Virtual Machines from Hyper-V

When the protected site is SCVMM, protection can be set up to cope with the following situations:

A disaster, enabling recovery to a point in time in the 30 days prior to the disaster.
The need to retain files saved either daily or weekly for a period of up to one year. The same wizard is used to set up both disaster recovery and the retention policy.

Use any of the following procedures depending on the site to which you need to recover:

Protected Site To a Recovery Site See Procedure...
Hyper-V Server To a different Hyper-V Server site Replication From a Protected Site Hyper-V Server to a Recovery Site Hyper-V
To the same Hyper-V Server site (local replication) Replication From a Protected Site Hyper-V Server to the Same Site
To a VMware vCenter site Replication From a Protected Site Hyper-V Server to a Recovery Site VMware vCenter Server
To a VMware vCloud Director site Replication From a Protected Site Hyper-V Server to a Recovery Site VMware vCloud Director
To an Amazon Web Services (AWS) site Replication From a Protected Site Hyper-V Server to a Recovery Site AWS
To a Microsoft Azure site Replication From a Protected Site Hyper-V Server to a Recovery Site AWS

Requirements for Hyper-V Environments

Before protecting your virtual machines, review Zerto - Prerequisites & Requirements for Microsoft Hyper-V Environments

Considerations

A Hyper-V host with a pass-through disk is ignored by the Zerto Virtual Manager.
Any virtual machine that is supported by the hypervisor can be protected. When recovering to a different hypervisor, the protected virtual machines must also be supported by the recovery hypervisor.
You cannot protect the following virtual machines:
A VM VRA which is a virtual machine with a VRA installed on it.
A virtual machine on a host that has no VRA installed.
A virtual machine that was created after performing a Failover Test.
A virtual machine that is connected to DVDs.
A virtual machine with no disks attached.
A virtual machine that was removed from the inventory.
A virtual machine with pass-through disks and shared disks.