Skip to main content

Acronis 11.7 Recovery to VM failed

Thread needs solution

Hi all,

I hope someone could help me with this issue. I am trying to recover the exisiting back up (.tib file) into virtual machine. I have setup the agent for VMWare binding and configured VMware vCentre integration. As far as I can troubleshoot, there is nothing wrong with the network between Acronis and VM. However, I was unable to recover my backup file into VM and keep on getting the following messages in the log:

TOL: Failed to execute the command. Recovering disks/volumes to new VM 'vm:806CDEDE-AD84-45F2-BAF2-7E0C54997521?type%3dvmwesx'
Additional info:
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields:  TraceLevel : 1, $module : disk_bundle_vs_50088
Message: TOL: Failed to execute the command. Recovering disks/volumes to new VM 'vm:806CDEDE-AD84-45F2-BAF2-7E0C54997521?type%3dvmwesx'
--------------------
Error code: 32788
Module: 114
LineInfo: 28314c961de7d41b
Fields:  $module : disk_bundle_vs_50088
Message: Failed to recover virtual machine 'New Virtual Machine' with ID 'vm:806CDEDE-AD84-45F2-BAF2-7E0C54997521?type%3dvmwesx'.
--------------------
Error code: 23
Module: 83
LineInfo: c61573f663f5d91a

Fields:  $module : esx_srv_vs_50088
Message: Failed to get access to hard disk '[Datastore1] New Virtual Machine/New Virtual Machine.vmdk'.
--------------------
Error code: 94
Module: 83
LineInfo: c61573f663f5d88c
Fields:  $module : esx_srv_vs_50088
Message: Failed to open virtual disk file '[Datastore1] New Virtual Machine/New Virtual Machine.vmdk'.
--------------------
Error code: 14009
Module: 0
LineInfo: c61573f663f5d771
Fields:  $module : esx_srv_vs_50088
Message: NBD_ERR_NETWORK_CONNECT
--------------------

Could anyone help please? Thanks in advance.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Vivien,

The typical reason for such failure is inability to resolve the target (for recovery) ESXi host address into IP address from the Agent for VMware side. Note that it's not Agent->vCenter connection (which should be OK according to your description)), but specifically Agent->ESXi host connection.

What happens: when the agent requests the target ESXi host address from vCenter (while configuring restored VM location), the vCenter returns the ESXi host address in the same form as it was specified while registering this ESXi host in vCenter, so vCenter may return the ESXi host hostname to the agent instead of ESXi host IP address and thus there could be problems with the name resolution.

In other words you need to make sure that the target ESXi host registration address (same as it appears in vCenter while connected to it from vSphere client) is resolved to IP (pingable) from the machine running Agent for VMware (appliance or Windows agent). See https://kb.acronis.com/content/60505 for details on how to check it.

If the above does not help, then the issue should be investigated with help from our support team. 

Thank you.