Veeam Replication Warning with Linux VMs

Replication Warning no static IPs detected

While setting up a replication job for a client I was getting a warning when the job ran that said: "No static IP addresses detected for SERVER_NAME, please specify default gateway settings manually."

After confirming with the Client that these 3 servers did indeed have static IPs, the next step was to investigate Veeam documentation. I landed on this article linked here:

What caught my interest specifically was this snippet here from the link:

At the Network step of the wizard, in the Network mapping section, click Add and select the production network to which VMs in the job are connected and network on the cloud host to which VM replicas must be connected. Repeat this step for every network to which Linux-based VM replicas must be connected — automatic network mapping for non-Windows VMs is not currently supported in Veeam Cloud Connect Replication.

Because of this limitation, during the job performance, in the list of operations for a non-Windows VM included in the job, Veeam Backup & Replication will display a warning that no static IP addresses are detected for a VM. If in fact a VM has a static IP address and network mapping settings are specified for a VM, this warning can be ignored.

The keywords to focus on from the documentation are "Linux-based VM". After confirming with the client that these 3 servers were indeed Linux-based, it was time to accept the fact that every time this job ran it would finish with a "Warning" status...really???

But that would not make monitoring Veeam Jobs easy if one has to acknowledge that certain jobs will finish with a "Warning" status and that it's "normal".

Thankfully, there is a regedit to fix this. The regedit will instruct all Veeam replication jobs to skip checking if VMs in replication jobs have static IPs.

WARNING: Only do this regedit after confirming that all the VMs you are replicating ACTUALLY have static IPs assigned to them. It's important for networking during failovers. Also, please follow best practice and backup the registry before making any edits.

All you have to do is create this registry value:

HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\CloudReplicaNoStaticIpSDetectedWarning = 0 (DWORD)

Then restart Veeam Backup Service.

And after that, all your Veeam replication jobs with Linux VMs will no longer display this warning.

Hopefully this helps you one day!