Intermittent SOAP faults after change ot VCSA

[ramnefors]

I have moved from an old vCenter server running on Windows Server 2008 to the vCenter server appliance (v5.5U2).

Having created a new job against the the same VM that worked OK for Win2008 I now get intermittent SOAP faults with the VCSA. For example:

2015-06-01 20:38:18 :: Processing veeam Error: Cannot get service content.
Soap fault. Host not foundDetail: 'get host by name failed in tcp_connect()', endpoint: 'https://vcsa.novotis.se:443/sdk'
SOAP connection is not available. Connection ID: [vcsa.novotis.se].
Failed to create NFC download stream. NFC path: [nfc://conn:vcsa.novotis.se,nfchost:host-16,stg:datastore-17@veeam/veeam.vmx].

First backup job 20% of the VM fail. The job retries and after one or two retries all VM have been backed up. Different VM may fail.

The environment is tiny, 3 hosts with 20 VM and is lightly loaded. Veeam B&R is v8U2.

Any suggestions?

[foggy]

Mats, please include support case ID for this issue, otherwise your post will be removed by moderators.

[ramnefors]

Problem found and fixed. Secondary name server incorrectly configured.

When B&R took snapshot of primary name server, name lookups went to secondary server which did not return correct address for VCSA, hence the SOAP faults.