VDP Backups failing with error: 10058
search cancel

VDP Backups failing with error: 10058


Article ID: 326938


Updated On:


VMware vSphere ESXi



- Backups failing immediately with error 10058.
- Reviewing backup job logs show following errors:

2018-11-20T16:32:09.277Z avvcbimage Error <0000>: [IMG0014] Problem logging into URL 'https://vcsa:443/sdk' with user '[email protected]'
2018-11-20T16:32:09.277Z avvcbimage Info <9772>: Starting graceful (staged) termination, Failed to log into web service. (wrap-up stage)
2018-11-20T16:32:09.277Z avvcbimage Warning <40657>: Login failed
2018-11-20T16:32:09.277Z avvcbimage Info <40654>: isExitOK()=208
2018-11-20T16:32:09.277Z avvcbimage Info <17823>: Body- abortrecommended(t)
2018-11-20T16:32:09.277Z avvcbimage Info <40658>: vmparams (vcsa)
2018-11-20T16:32:09.277Z avvcbimage Info <40654>: isExitOK()=208
2018-11-20T16:32:09.282Z avvcbimage Warning <16004>: Soap fault detected, Connection problem with WS ticket, Msg:'SOAP 1.1 fault: SOAP-ENV:Client [no subcode]
"Name or service not known"
Detail: getaddrinfo failed in tcp_connect()

2018-11-20T16:32:09.529Z avvcbimage Info <16038>: Final summary, cancelled/aborted 0, snapview 0, exitcode 208: plugin error 08
2018-11-20T16:32:09.533Z avvcbimage Warning <16041>: VDDK:VixDiskLib: Failed to resolve IP address with error -2 at 2551.

2018-11-20T16:32:09.533Z avvcbimage Info <16041>: VDDK:VixDiskLib: Could not resolve server name for vcsa. Error 14008 (The specified server could not be contacted) at 2653.
2018-11-20T16:32:09.533Z avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Connect: Failed to allocate connection. Error 14008 (The specified server could not be contacted) at 4214.
2018-11-20T16:32:09.533Z avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_EndAccess: Failed to establish connection. Error 14008 (The specified server could not be contacted) at 4509.

2018-11-20T16:32:09.533Z avvcbimage Warning <0000>: [IMG0008] VixDiskLib vMotion reservation release returned fault(14008) (14008) The specified server could not be contacted - host:vcsa account:A
[email protected] dc:/ProductionSite&dsName: vmxpath:[ESX6-DAS2] VM-TestPC/VM-TestPC.vmx port:443vmmoref:vm-33823

- Above error indicates a login failure into vCenter server even though there are no issues with username/password:

2018-11-20T16:32:09.277Z avvcbimage Warning <40657>: Login failed


VMware vSphere Data Protection 6.1.x


This issue occurs if DNS resolution is not working on VDP appliance or any of the external proxies.


To resolve this issue make sure that name resolution is working from VDP appliance and external proxies if any.
To check whether name resolution is working run the following commands:

nslookup vcsa_hostname/ip
nslookup vdp_hostname/ip

In case name resolution is not working, investigate whether /etc/resolv.conf has valid DNS server entries similar to:

search domaincorp.domain.com domain.com
nameserver 192.168.xx.xx
nameserver 10.10.xx.xx

If /etc/resolv.conf is missing DNS nameserver IP, populate this file with valid DNS server IP address and then run nslookup commands again.