Protecting Virtual Machines from a vCenter Server
  
Protecting Virtual Machines from a vCenter Server
When the protected site is vCenter Server, 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 back up to 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 backup.
Use any of the following procedures depending on the site to which you need to recover:
Protected Site
Recovery Site
See Procedure...
vCenter Server
To a different vCenter Server site
Replication From a Protected Site vCenter Server to a Recovery Site vCenter Server
To the same vCenter Server site (local replication)
Replication From a Protected vCenter Server to the Same Site
To a different site using the Client Console or VMware Web Client
Protecting a Single Virtual Machine (Via the VMware Web Client or Client Console)
To a Hyper-V site
Replication From a Protected Site vCenter Server To a Recovery Site Hyper-V Host
To a Amazon Web Services (AWS) site
Replication From a Protected Site vCenter Server to a Recovery Site AWS
To a Microsoft Azure site
Replication From a Protected Site vCenter Server to a Recovery Site Microsoft Azure
Requirements for vSphere Environments
Before protecting your virtual machines, review Zerto Virtual Replication - Prerequisites & Requirements for vSphere Environments
Considerations
■ If one or both of the sites have vCloud Director installed, see “Protecting Virtual Machines to and From vCloud Director”, on page 120.
■ You cannot protect virtual machines with VirtualEthernetCardLegacyNetworkBackingInfo NICs or with IDE devices.
■ 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.
■ Zerto does not support protecting virtual machines that are connected to CDs / DVDs.