Protecting Virtual Machines From Azure

Virtual Machines created in Azure can be protected to the following platforms:

Protected Site	To Recovery Site	See Procedure...
Azure	To a vCenter Server site	Replication From a Protected Site Microsoft Azure to a Recovery Site vCenter Server
	To a Hyper-V site	Replication From a Protected Site Microsoft Azure to a Recovery Site Hyper-V Server
	To a vCloud Director (vCD)	Replication From a Protected Site Microsoft Azure to a Recovery Site vCloud Director
	Within Azure	Replication From a Protected Site Microsoft Azure to a Recovery Site Microsoft Azure
	To a Amazon Web Services (AWS) site	Replication From a Protected Site Microsoft Azure to a Recovery Site AWS

Requirements for Microsoft Azure Environments

Before protecting your virtual machines, review Zerto Virtual Replication - Prerequisites & Requirements for Microsoft Azure Environments

Limitations and Considerations

The following are not supported:

■ Volumes residing in premium storage accounts.

■ Virtual machines with managed disks attached.

■ Azure temp drives.

■ Backup is not supported for “From Azure” VPGs

■ Offsite Backup not supported (back up tab removed from “From Azure” VPGs)

■ Resizing of protected disks on Azure is not supported and will not result in an auto-resized recovery disk. After resizing, the protected disk from Azure, the VRA will not crash but the VPG will be stuck in a Needs Configuration state until the resized disk, VM, or VPG is removed.

Notes:

■ When Reverse Protection is configured, in the Recovery step of the wizard the VPG and VM default network settings are configured as if a new VPG to Azure was created. The original VM network settings of the on-premise VPG are not reproduced in the VPG network settings in reverse protection configuration.

■ When creating or editing a VPG from Azure to vSphere or Hyper-V, re-IP of the NIC configuration is supported only if VMware Tools (vSphere) or Microsoft Integration Services (Hyper-V) are available for each virtual machine in the VPG, in which case the IP address of the originally protected virtual machine is used.

■ Protection can be set up to enable recovery to a point in time, up to 30 days prior to a disaster.

■ Azure local SSD disks, which are created with the virtual machine but not provisioned to the virtual machine, are not protected.

■ Boot order configuration for virtual machines recovered from Azure to on-premise sites is supported.

■ Both the protected and recovery sites must be running Zerto Virtual Replication version <LatestVersion>.