Voltar
-
Título
Plugin for VMware 11.3 and upper Fails to Open Virtual Disk for VM due VDDK error Code 14009 -
Descrição
Backup for VM fails with error:
Failed to open virtual disk and [14009] The server refused connection
We see the same error when we run Diagnose Virtual Machine from Actions in the selection tree.
Also Debugging traces point to the same error:
4 VDDK :66588 35 0 152755.175217 Opening disk '[DataStore] CENTOS7/CENTOS7.vmdk'3 DYNLIB :66588 12 0 152755.175222 00007FFC9B8A7380 = GetDynamicLibFunctionAddress. FunctionName = VixDiskLib_Open0 VDDK :66588 36 0 152755.596072 Failed to open vmdk0 VDDK :66588 138 0 152755.596081 VDDK error encountered: code 140093 DYNLIB :66588 12 0 152755.596089 00007FFC9B8A9410 = GetDynamicLibFunctionAddress. FunctionName = VixDiskLib_GetErrorText3 DYNLIB :66588 12 0 152755.596094 00007FFC9B92D260 = GetDynamicLibFunctionAddress. FunctionName = VixDiskLib_FreeErrorText1 VDDK :66588 139 0 152755.596098 Retrieving error message text0 VDDK :66588 52 0 152755.596103 VDDK error message is 'The server refused connection' -
Causa
There is no connectivity between the ESXi host and the VMware proxy.
This issue also occurs in situations where vCenter and some of the hosts are running VMware 5.5 or upper but the host where is located the VM is running VMware 5.1 or below.NetVault Backup Plug-in for VMware 11.3 and upper is not compatible with VMware 5.1 and below.
-
Resolução
Check the connectivity:
- On PowerShell, run the following commands. Repeat if there are multiple ESXi
- Test-NetConnection -ComputerName "ESXihostname" -Port 902
- Test-NetConnection -ComputerName "ESXihostname" -Port 443
- Test-NetConnection -ComputerName "vCenterServername" -Port 443
- If there is an error, check DNS name resolution
- On PowerShell, run the following commands. Repeat if there are multiple ESXi