Backup fails: Specified entry does not exists: 'a440765d-63cb-7616-4324-e8a5d8be4168'
Somehow my backups are failing since a few days. I have no idea why and we did not change anything. When i open the log files is see the following errors:
Task 'Full Lan Backup' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09501ce
Fields: $module : D:\Acronis\vmProtect\Windows Agent\vmms.exe
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d32e
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 32778
Module: 248
LineInfo: c25b1498c08c3607
Fields:
Message: Failed to retrieve object access information.
--------------------
Error code: 32771
Module: 248
LineInfo: c25b1498c08c3602
Fields:
Message: Specified entry does not exists: 'a440765d-63cb-7616-4324-e8a5d8be4168'.
--------------------'.
Where do i have to look or what can i do? What does the last entry means? All services and the whole server has been rebooted. We are running Server 2003 std. X86.

- Log in to post comments

I'm having same error, and I tried to 'refresh' the object list by re-adding the ESXi host, but the error still remains.
best Regards
Enrico
- Log in to post comments

Hi Enrico,
It makes sense to contact our support team for assistance with this issue. Likely a short remote assistance session will be required to take a look at the environment and figure out what could be wrong (it can be duplicate InstanceUUIDs for example).
Thank you.
--
Best regards,
Vasily
Acronis Virtualization Program Manager
- Log in to post comments

We rebooted the ESXi server, and after a remove/rejoin it seems to work now.
The strange thing is that we have 2 identical ESXi hosts, and we were getting the same error on both.
The have identical configuration, no Vcenter integration (we need completely separate stuff for redundancey reasons); everything was working two weeks ago, and we did not make any change in configuration, simply we moved the system to another room, and it stayed off for a day.
We will complete the test (backup all VMS) and do same sequence also on second ESXi.
If anything fails again, i will contact the support.
Many Thanks
Enrico
- Log in to post comments