Discussions specific to the VMware vSphere hypervisor
Post Reply
ramnefors
Influencer
Posts: 10
Liked: 2 times
Joined: Nov 11, 2014 1:02 pm
Full Name: Mats Ramnefors
Contact:

Intermittent SOAP faults after change ot VCSA

Post by ramnefors » Jun 02, 2015 10:30 am

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
Veeam Software
Posts: 18261
Liked: 1561 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Intermittent SOAP faults after change ot VCSA

Post by foggy » Jun 02, 2015 12:59 pm

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

ramnefors
Influencer
Posts: 10
Liked: 2 times
Joined: Nov 11, 2014 1:02 pm
Full Name: Mats Ramnefors
Contact:

Re: Intermittent SOAP faults after change ot VCSA

Post by ramnefors » Jun 02, 2015 4:45 pm 1 person likes this post

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.

Post Reply

Who is online

Users browsing this forum: fondazionetls and 33 guests