Backup Copy job, No such host is known

[hyvokar]

Case #02647256 is slowly going nowhere, so I'll ask here.



I have two backup copy jobs for my cluster. One for offsite, one for archival purposes.
Currently, the offsite copy is in our local network, so the settings for both jobs are roughly similar.

One VM from DMZ in office backup copy job fails with following error:

9.3.2018 2:27:20 :: Error: resolve: No such host is known
9.3.2018 2:27:20 :: Processing finished with errors at 9.3.2018 2:27:20
9.3.2018 2:27:20 :: Maximum retry count reached (5 out of 5)


06.03.2018 06:04:17] <10> Info Updating host 'win7proxy': credentials 'e88290d7-1190-46ef-a75d-e0fbcbebd81b'
[06.03.2018 06:04:17] <05> Error Failed to resolve DNS name. Host name: [192.168.111.xxx]
[06.03.2018 06:04:17] <05> Error No such host is known (System.Net.Sockets.SocketException)

Support told me that the name resolution for win7test is not working, but it is.
I'm not sure why I get an error "Error Failed to resolve DNS name. Host name: [192.168.111.xxx]". It's a windows machine used for testing purposes over site-to-site vpn link and will be populated later by offsite backup. That server is not used by these jobs.

[Andreas Neufert]

Hi, thanks for sharing this here. There are several usecases why Veeam connect to this Veeam managed server. For example when you have selected a Gateway Server or any other role in "Automatic" mode and Veeam falls back to it as you experienced a network issue (your statement at support). Based on the support case the issue was solved without an action from Veeam side. Can you please describe what the root cause was and if you use any Veeam Roles like Mount Server/Gateway Server/Guest Interaction in Automatic mode?

[hyvokar]

No idea what the root cause was. One day it just started working.