Connectivity Issue When Adding Veeam Backup & Replication to Enterprise Manager

KB ID: 2098
Product: Veeam Backup & Replication
Published: 2016-02-15
Last Modified: 2022-05-26
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

When attempting to add a Veeam Backup Server to Veeam Backup Enterprise Manager the following error occurs:
Connection to Veeam Backup service unavailable.
Correlated with this error will be entries n the svc.VeeamBES.log on the Enterprise Manager server stating “host not resolved.”

Cause

These connectivity issues may be related to the following causes:

  • The Enterprise Manager server is unable to connect to the Veeam Backup Server over the required ports.
  • The Enterprise Manager is unable to resolve the Veeam Backup Server via both DNS and rDNS.

Solution

Ports

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.
 

DNS/rDNS

  • 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 via DNS and rDNS.

If one or the other is unable to resolve the others hostname or FQDN to the correct IP, correct the environment so that DNS resolves. Editing the hosts can be done as a workaround.

More Information

Security Warning

The advice in this section is intended for use in environments where internal networks are isolated, and a connection needs to be made that will not traverse the Internet. The communication methods that the software uses are not designed to support NAT, however, modifications can be made to make it work with NAT.

Veeam strongly advises against using these modifications when the connection between the Enterprise Manager Server and Veeam Backup Server will occur over the open Internet, as that would expose critical Veeam Backup & Replication services. Instead, Veeam advises that if Enterprise Manager must manage a Veeam Backup Server across an internet connection, a VPN or private network solution be used.

Connection When NAT is Involved

NAT Workaround Credit to http://forums.veeam.com/veeam-backup-replication-f2/making-veeam-enterprise-manager-work-over-a-wan-link-t14740.html#p67775

Veeam Backup Enterprise Manager expects that the Veeam Backup Server added to it will be resolvable via DNS and rDNS. That is to say, if a Veeam Backup Server is added via IP address, the Enterprise Manager server can resolve that IP address to a DNS name that can be contacted to reach the Veeam Backup Server. This can be made more complicated by the fact that during some interactions,  Veeam Backup & Replication will directly communicate to the Enterprise Manager server its actual DNS/FQDN and IP address, which of course, will not work when that Veeam Backup Server is behind NAT.

If NAT is being used between the Enterprise Manager server and Veeam Backup Server, you must configure the following registry keys on the Veeam Backup Server.

  • This value controls whether Veeam Backup & Replication will send its local IP when communicating with Enterprise Manager. This value should be set to “false” to prevent conflicts with NAT.

    Key Location: 
    HKLM\Software\Veeam\Veeam Backup and Replication
    Value Name: Remoting_UseIPAddress
    Value Type:
     String Value (REG_SZ)
    Value Data: false
  • This value allows the FQDN/Hostname that Veeam Backup & Replication reports back to Enterprise Manager to be manually assigned.
    Remember, the Enterprise Manager must be able to resolve the FQDN or HostName through DNS or hosts file.

    Key Location: HKLM\Software\Veeam\Veeam Backup and Replication
    Value Name: Remoting_MachineName
    Value Type: String Value (Reg_SZ)
    Value Data: <fqdn/hostname>

After configuring these registry values, verify that the Enterprise Manager can resolve the configured FQDN/Hostname and that the required ports can be reached on the Veeam Backup Server from the Enterprise Manager Server.

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.

 

 

If, after a reboot, the Veeam Backup Service cannot start on the Veeam Backup Server, check to see if the Veeam Backup Server is resolving its internal IP address correctly. 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.

 

 

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.