Object specified by ID cannot be found
We recently upgraded to vSphere 5.5 and I am doing my first restore from vmProtect in this environment. I get the following error just a few seconds after I click Run Now.
Group restore error: Failed to restore the virtual machine.
Additional info:
--------------------
Error code: 8
Module: 436
LineInfo: 89658f6232025312
Fields:
Message: Group restore error: Failed to restore the virtual machine.
--------------------
Error code: 32795
Module: 114
LineInfo: fde974fd2ebd012a
Fields:
Message: Failed to convert the backup to the virtual machine.
--------------------
Error code: 32768
Module: 114
LineInfo: fde974fd2ebcff98
Fields:
Message: An object specified by ID '805,307,289' cannot be found.
--------------------
I am restoring to a new vm, and not overwriting the existing. Any help would be appreciated.
-Billy

- Log in to post comments

Vasily,
I recreated the recover task, same result.
Our version is Acronis vmProtect 9.0 Agent (build 9.0.9802).
We actually set up a new 5.5 instance, migrated all VM's, did a fresh install of vmProtect, and manually set up new backup tasks. The backups we are trying to restore from were all created in this new environment.
Please advise. Desperately need this virtual machine restored.
-Billy
- Log in to post comments

Hi Billy,
Thank you for the details - the problem here is in the particular backup being restored. It seems to contain invalid disk IDs inside it which is the reason for why the recovery doesn't work. From what I have checked that part of code is not used when you perform Run VM from Backup (since there is no partitions allignment performed and VM is emulated "as is") so it should be the quickest possible restore option in your case. You can Run VM from Backup of this VM and then perform migration to different datastore (different from the one you specified where to keep changes in Run VM from Backup wizard) of the mounted VM to finalize it permanently on new datastore.
In order to investigate the original issue (why recovery doesn't work), please check the private message which I'll send you in a couple of minutes.
Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager
- Log in to post comments

The Run VM from Backup task failed too:
Failed to publish virtual machine.
Additional info:
--------------------
Error code: 9
Module: 405
LineInfo: 476adbf26d208b4b
Fields:
Message: Failed to publish virtual machine.
--------------------
Error code: 6
Module: 405
LineInfo: 476adbf26d2088e1
Fields:
Message: Failed to emulate virtual machine's disks.
--------------------
Error code: 44
Module: 83
LineInfo: 26eed62d2c1407e3
Fields:
Message: Failed to obtain server object 'config.hardware.device' (vm-456).
--------------------
I even tried last night's backup, same result. I can't have backups I can't use.
- Log in to post comments

Hi Billy,
There is one more tip to try here: shutdown Acronis vmProtect Virtual Appliance and upgrade its virtual hardware from the vSphere client. After that power it On and try the recovery/Run VM from Backup once again. If that still doesn't help then proceed as I described in the private message.
Can you please also clarify where your backups are physically located? I assume it is some kind of NAS device, but need to make sure.
Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager
- Log in to post comments

Tried updating the virtual hardware, same result. I will proceed with PM directions.
Backups are physically located on a SAN, connected as a local disk to the vmProtect vm via iSCSI.
-Billy
- Log in to post comments

Hi!
To summarize the thread: the original recovery issue has been resolved by a newer build of Acronis vmProtect 9 (Update 1) so this fix will be included into all future builds as well as into the official update. Besides that there was performed a virtual hardware upgrade of the virtual appliance which some times might be necessary on vSphere 5.5 environment.
Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager
- Log in to post comments

Thanks. It should be included in the change logs I think.
- Log in to post comments