vmProtect 7, Failed to create a backup / Failed to retrieve object access information / Specified entry does not exists

Interesting indeed and would love to know the cause.  I got this today myself during some more tests (something I promised not to do but couldn't help myself).  Were there ANY changes at all on your one?

Problem: When I run the vmProtect GFS backup, I get this as well.
Error code: 32771Module: 248 LineInfo: c25b1498c08c3602 Fields: 
Message: Specified entry does not exists: 'b79d560d-b48d-053e-7864-1f2d5d4ddc74'.
QUESTION: What exactly is it looking for?

In my case there was a change which may help determine cause? 

Scenario: I created a new ESXi5 USB Key.
VM's Locations & vmProtect 5155 VM: No changes and VM's all located on the Server HDD. This remain unchanged.
Prior to Mounting;
- I ensured All original (Datastores) were mounted as per original name.
- ESXi was setup the same i.e. IP Address, Name etc

Loading: All VM's incl vmProtect, loaded and booted without error, which tells me that they were not aware of any actual change in environment.

vmProtect GFS Job: When one goes to Edit the job, it finds the original location without issue itself i.e. No errors and I didn't have to adjust anything in the backup job.  I even saved and run but it still fails with above noted error.

What Does Work: If I reboot the server with original ESXI USB stick and then run the job. It works.   WHY, what is vmProtect looking for?

Hi Paddy,

There were no changes made to the configuration. (Regarding Acronis VmProtect)
There were some new machines to backup, but nothing else. Even creating a new job does not resolve the problem.

We also have 1Tb online storage. And the backup even fails when backupping to the online storage.

I already send a ticket to acronis support after talking to one of their employees.

Hopefully the issue is resolved soon.

I'll post my findings.

Any fix on this from Acronis yet.

A work around for me was to reinstall a new vmProtect VM and set up all the jobs from scratch. This is far from ideal
- One loses all the previous Jobs.
- One loses the GFS backup and has to start from scratch.

It seems vmProtect is not "Movable" as a VM i.e. somehow binds itself to a specific install. That is a problem when one has to rebuild ESXi5 or upgrade ESXi5 to a later build (which is what I tested).

One Additional Observation:
My tests showed that One cannot after remounting the Original vmProtect VM, complete any of the following:
RESTORE, RECOVER, MOUNT, Nor Access Exchange from the Previous Backups. One can however use "File Recovery"

I did however Succeed in the above tasks using the Newly Installed vmProtect to mount the older backups. This at least worked. In short it seems at worst you will lose all your backup jobs as there is no method to copy them to a new install. which is a pain.

Dre Selen, did you do any restore tests?

No fix from acronis yet, but support is still working on it.

The root cause can be can come from many places... Hopefully the new build will solve those problems all at once..

I will post the result after i have a solution from Acronis.

Problem solved in the new version...