Connectivity Issue When Adding Veeam Backup & Replication to Enterprise Manager

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.