返回
-
标题
Virtual exports fail sporadically with "Vddk Handle is invalid" error -
说明
Virtual export jobs fail with error: "VddkApiException: VDDK Handle is invalid. This can be due to VDDK API proxy restart."
Error message sample:
Exception chain:Vddk Handle is invalid. This can be due to Vddk API proxy restart.Operation 'Disconnect' with diskHandle = '574334523648' failed with VddkApiException: Vddk Handle is invalid. This can be due to Vddk API proxy restart.Cannot execute an export taskOne or more errors occurred.
Other jobs that require to interact with the API, such as agentless snapshots, could also fail with a similar failure reason. -
原因
Core may restart VMware Proxy service if it doesn't respond after some period of time (5 minutes by default). The underlying cause of the VMware Proxy service unresponsiveness is usually system overload / lack of resources. -
解决办法
WORKAROUND
A workaround for this is increasing the timeout for VMwareProxyServiceConfiguration on Core side. Please note that the solution requires modifying the registry.
WARNING: Altering registry settings can have dire consequences on your machine. Be extremely careful to not delete any items in the registry. Quest does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support. To fix the issue perform the steps below.
- Open REGEDIT
- Browse to HKLM\SOFTWARE\AppRecovery\VMwareProxy
- Change MaxHandleInactiveTime to 00:15:00. If that key does not exist, create it as String.
- Restart the Core service.
- If exports continue to fail extend the timeout above further to 00:30:00.
-
缺陷ID
RR-99335 / D-34301 / AA-3026 -
其他信息
If the problem persists, our R&D team have developed a patch that helps improve the fault tolerance of ESXi jobs (AA-3026) by trying to use HttpContent instead of NamedPipes logic (to simplify and avoid possible memory using overhead). Please open a case with technical support to retrieve this patch.