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	To Recovery Site	See Procedure...
vCenter Server	To a different vCenter Server site	“Protecting From a VCenter Server - To a Recovery Site vCenter Server”, below
	To the same vCenter Server site (local replication)	“Protecting Virtual Machines to the Same Site”, on page 156
	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)”, on page 158
	To a Hyper-V site	“Protecting Virtual Machines to Recovery Hyper-V Hosts”, on page 159
	To an Amazon Web Services (AWS) site	“Protecting Virtual Machines on a vCenter Server to AWS”, on page 171
	To a Microsoft Azure site	“Protecting Virtual Machines on a vCenter Server to Azure”, on page 184

■ 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.