Limitations for Cloud Connect Backups
Veeam Backup & Replication has the following limitations for cloud repository usage:
Backup, Backup Сopy and Restore
- Veeam Backup & Replication does not support backup copy jobs if the cloud repository is used as a source backup repository. The backup copy job must use a backup repository configured locally on tenant's side as a source one.
- Veeam Cloud Connect does not support transaction log backup. You cannot enable transaction log backup options in the properties of a backup job targeted at the cloud repository.
- Instant VM Recovery, multi-OS file-level restore and restore to Microsoft Azure from backups in the cloud repository are not supported.
Tenants can manually copy backup files to and from the cloud repository using the Files view in the Veeam Backup & Replication console. Scheduled file copy jobs are not supported.
Limitations for Cloud Connect Replication
Veeam Backup & Replication has the following limitations for cloud host usage:
- Veeam Cloud Connect Replication does not support DHCP. To allow a VM replica on the cloud host to be accessible over the network after failover, a replicated VM must have a static IP address.
- Automatic network settings detection is supported for Microsoft Windows VMs only. For cloud replication of non-Windows VMs, a tenant should specify network mapping settings and public IP addressing rules manually.
- A tenant cannot specify Re-IP rules for VM replicas on the cloud host. At the process of the replication job configuration, if a tenant selects the Re-IP option and then selects the cloud host as a replication target, Veeam Backup & Replication will disable the Re-IP option.
- Pick datastore option is not supported for replication jobs targeted at the cloud host.
- A tenant can restore VM guest OS files from a VM replica on the cloud host only to a Microsoft Windows file system.
- [For Microsoft Hyper-V VMs] Cloud replication of Shielded VMs is not supported. Replicas of such VMs can run only on guarded Hyper-V hosts that have access to Host Guardian Service deployed on the tenant side.
- Ensure all VMs have static IPs set.
- Check that in the event of a full site failover or isolated test that all replicated systems only reference the DNS names or IPs of other replicated systems.
- If you intend to open port 3389 and RDP directly to VM during a full site failover you should ensure NLA is disabled within the systems RDP settings.
- If replicating one domain controller out of many you may need to perform additional steps to get active directory services running post-failover. See the following Veeam KB