Veeam Backup failure – SOAP issue with vSphere

When you get the error message “SOAP connection is not available” pointing out to the vCenter. You will start to look at the Veeam logs located in C:\ProgramData\Veeam and you will find quickly, that the logs are pointing to nowhere.

The jobs shows this message:

The log shows the same:

[29.09.2022 03:46:03] <29> Error Soap fault. Temporary failure in name resolutionDetail: ‘getaddrinfo failed in tcp_connect()’, endpoint: ‘https://vcsa01.irgnet.wtf:443/sdk’
[29.09.2022 03:46:03] <29> Error SOAP connection is not available. Connection ID: [vcsa01.irgnet.wtf].
[29.09.2022 03:46:03] <29> Error Failed to create NFC download stream. NFC path: [nfc://conn:vcsa01.irgnet.wtf,nfchost:host-10028,stg:datastore-10029@

So next you will have a look into the vCenter logs and will not find any log entry pointing to this issue.

The Solution

You can stop your troubleshooting on the Veeam and VMware side. This issue is related to DNS servers. Your proxies used into your backup job cannot resolve the vCenter and ESX-Host properly. You need to check your DNS forward and also reverse DNS lookup entries.

And additional you should check every VM/Host you normally backup over your Veeam Backup Server. After a workaround about 1 hours and restart my Veeam Backup Proxies (Linux, Debain based) and there we go: Veeam Backup Success!

If you have any questions, please leave it in the comment section below! 🙂