This article documents issues that may arise when attempting to add a Veeam Backup Server to Backup Enterprise Manager, include when NAT is being used. When using NAT either server may not be able to mutually resolve the other external IP address. Other issues can arise in situations where NAT is not in use but either server is unable to resolve the hostname/fqdn of the other server, or ports are blocked.
When these issues occur the Enterprise Manager web console will report “Connection to Veeam Backup service unavailable.”
Errors will be found in the svc.VeeamBES.log on the Enterprise Manager server stating “host not resolved.”
This is caused by the Veeam Backup server, Backup Enterprise Manager server, or both not being able to correctly initiate a connection. When NAT is involved, the Veeam Backup Server will incorrectly reply back to the Backup Enterprise Manager server with its internal IP address as the preferred IP address, and the connection will time out and produce an error.
Port and DNS Requirements
Please review the port requirements section of the user guide for Backup Enterprise Manager.
Ensure that the ports above are open and communication can be made between the Veeam Backups Server and the Backup Enterprise Manager server.
- The Veeam Backup Server must be able to resolve the Backup Enterprise Manager’s FQDN and hostname.
- The Backup Enterprise Manager must be able to resolve the Veeam Backup Server’s FQDN and hostname.
Connect when using NAT
If NAT is being used between the two servers the following registry keys will need to be set on the Veeam Backup Server.
These registry entries are added in the following location on the Veeam Backup Server.
HKLM\Software\Veeam\Veeam Backup and Replication
•Default value: true
•Description: Control whether Veeam Backup & Replication must send its local IP or not (should be set to “false” to allow Veeam Enterprise Manager to connect over NAT). Apply on Veeam Backup Server.
•Default value: none
•Description: Manually sets which FQDN the Veeam Backup Server will send to the Backup Enteprise Manager server. Apply this entry on the Veeam Backup Server. Enterprise Manager must be able to resolve FQDN or HostName though DNS or hosts file.
After completing the above steps and ensuring that ports and DNS resolution is working restart the Veeam Backup Server.
If after the reboot the Veeam Backup Service is unable to start, check to see if the Veeam Backup Server is resolving its internal IP address. If it is unable to a local hosts file edit may have to be made so that the services on the Veeam Backup Server will connect to the local SQL instance.
With all of the above confirmed and implemented the Veeam Backup Server can be added to the Enterprise Manager using the FQDN of the Veeam Backup server.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.