Veeam Cloud Connect Replication can sometimes complete with one of the following warnings:
- No static IP addresses detected for [VM Name], please specify default gateway settings manually.
- One or more source networks possible were mapped to the same cloud network. Simultaneous partial failover of VMs on these networks may cause issues.
These warnings can occur with Linux virtual machines, when the virtual machine has multiple network adapters, or when the networking configuration is not set up correctly.
No static IP addresses detected for VM, please specify default gateway settings manually.
This warning means that Veeam was unable to assign an IP address to the target replica VM. This is typically due to the source being a Linux VM. The following information is from the Veeam documentation and explains this behavior, including a registry key for a workaround.
- In case Veeam Backup & Replication fails to detect a static IP address of a tenant VM during the replication process, the SP or tenant must manually specify the IP address for the replica of this VM in VMware Cloud Director. In particular, Veeam Backup & Replication cannot detect an IP address of a Linux VM.
- Because Veeam Cloud Connect Replication does not support automatic network mapping for non-Windows VMs, during the job performance, in the list of operations for such VMs included in the job, Veeam Backup & Replication will display a warning that no static IP addresses are detected for the VM. If in fact the VM has a static IP address and network mapping settings are specified for the VM, this warning can be ignored.
- You can instruct Veeam Backup & Replication to suppress the warning. To remove the warning from the job session statistics, on the tenant Veeam backup server, create the registry value: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\CloudReplicaNoStaticIpSDetectedWarning = 0 (DWORD) and restart Veeam Backup Service.
One or more source networks possible were mapped to the same cloud network. Simultaneous partial failover of VMs on these networks may cause issues.
This warning means that Veeam wasn’t able to detect the gateway address of the source VM causing it to be unable to automatically determine which failover network to map the production network to.
The solutions for this include:
- Make sure that the default gateways are correctly listed under Backup Infrastructure > Service Providers > Service Provider > Default Gateways.
- Check that the IP address, subnet mask, and default gateway settings are correct. If any of these settings are incorrect or missing, update them accordingly.
- Checking the box for “route traffic between these networks” can also resolve these issues.
- Another option is to edit the replication job and enable the network mapping option. This allows the production virtual networks to be manually mapped to the correct failover networks.
-  https://www.veeam.com/veeam_backup_12_cloud_administrator_guide_pg.pdf
-  https://helpcenter.veeam.com/docs/backup/cloud/cloud_vcloud_director_infrastructure.html?ver=120
Please reach out to Managecast if the warnings persist and we can help troubleshoot and resolve the issue.