Cannot get service content. Soap fault. No DataDetail: 'get

[Odarchuk]

Hi, all!
VBR 6.5 p1
Vmware 5.1.b
Some VM has error:

24.01.2013 16:49:43 :: Processing configuration Error: Client error: Cannot get service content.
Soap fault. No DataDetail: 'get host by name failed in tcp_connect()', endpoint: 'https://vcenter.domain.local:443/sdk'
SOAP connection is not available. Connection ID: [vcenter.domain.local].
Failed to create NFC upload stream. NFC path: [nfc://conn:vcenter.domain.local,nfchost:host-6633,stg:datastore-7270@SQL-HQ01_replica/SQL-HQ01.vmx].

case: 00173658.

Veeam support: We recomended use stansalone ESXi-host instead of vCenter.
But i have 4-servers in cluster and my VM not binded from some ESXi-host

Help me !

[Vitaliy S.]

Hi Sasha,

Using standalone hosts is a bad idea, as after any VM migration you will have to adjust your existing backup jobs.

Based on your error message, I can say you have a connectivity issue to your vCenter Server (SOAP requests cannot be processed for some reason). Can you please tell me how many hosts and VM you're managing with this vCenter Server? What is the hardware configuration of your vCenter Server? Also what is the resource utilization on your vCenter Server when you run backup/replication jobs?

Thanks!

[Odarchuk]

Using standalone hosts is a bad idea, as after any VM migration you will have to adjust your existing backup jobs.

+100500 but your colleagues have recommended me to use a this configuration

I have:
- 6 ESXi hots
- 40+ VMs

I tried to migrate this VM to another host - didn't help me (replica not working).
I also tryied to migrate another VMs to this host - replica is working.

[Vitaliy S.]

Hmm...so you have only one VM affected by this behavior, right? I've got one suggestion to try - can you please run this job once again and once you receive this error message try to download VM VMX file manually via vSphere Client connected to the vCenter Server?

[aaronlalonde]

I am having the exact same issue- what was the resolution to this?

[veremin]

Typically, you might get this kind of errors due to some networking issues.

However, it’s way too hard to say certainly without seeing an infrastructure and/or backup logs; thus, it stands to reason to open a ticket with our support team and let them investigate it directly.

Thanks.