Protecting Virtual Machines From Azure
Virtual Machines created in Azure can be protected to the following platforms:
Requirements for Microsoft Azure Environments
Before protecting your virtual machines, review Zerto Prerequisites and Requirements for Microsoft Azure Environments.
Limitations and Considerations
|
•
|
You cannot protect the following virtual machines: |
|
•
|
A virtual machine that was created after performing a Failover Test. |
|
•
|
A virtual machine with no disks attached. |
|
•
|
A virtual machine that has multiple NICs using the same MAC address. |
|
•
|
Volumes residing in premium storage accounts. |
|
•
|
VMs with disks that are not Managed Premium disks, Managed Standard SSD disks or Managed Standard HDD disks. |
|
•
|
VMs with disks in storage accounts. |
|
•
|
Retention is not supported in Azure. |
|
•
|
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. |
|
•
|
Resizing of protected disks in Azure is supported. |
|
•
|
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. |
|
•
|
When a VM is recovered to Azure, a temporary drive is automatically created in the drive letter following the OS drive. Due to this temp drive, the non-OS drives you had set up in your production site may be shifted when recovered to Azure. |
|
•
|
Every block blob, page blob and Managed disks that are created by Zerto, are Encrypted at Rest on the Microsoft Azure platform, using the Microsoft-managed default key. |
|
•
|
Both the protected and recovery sites must be running Zerto <LatestVersion>.
|