Skip to main content

Acronis Backup Converstion to VM Failed

Thread needs solution
Beginner
Posts: 1
Comments: 0

I am trying Acronis out and using the conversion to VM feature in the backup jobs. I am testing it out on some of out physical servers. Our VM environment is Hyper-V. When the first backup job ran the VM was made, but when the next backup job ran the next day the conversion to VM failed with the following error. 

Backup Management Console

Message

TOL: Failed to execute the command. Converting backups to virtual machines

Additional info:

------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"mms_vsa64_14330","CommandID":"DAFCCD45-545C-4740-9E0E-5D4DAD9F826C"}
Message: TOL: Failed to execute the command. Converting backups to virtual machines
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"virt_task_handlers_registry_vsa64_14330","CommandID":"DAFCCD45-545C-4740-9E0E-5D4DAD9F826C"}
Message: TOL: Failed to execute the command. Converting backups to virtual machines
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"mms_vsa64_14330","CommandID":"4504F8D4-2727-42AB-BB4F-A42EDBB790A0"}
Message: TOL: Failed to execute the command. Tol::IsolateCommand
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"service_process_vsa64_14330","CommandID":"B3AF2D36-A22A-4D2D-BE42-718EBF1833DC"}
Message: TOL: Failed to execute the command. Converting backup to VM 'USCLP008-HP_converted'
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB819597
Fields: {"$module":"disk_bundle_vsa64_14330","CommandID":"B3AF2D36-A22A-4D2D-BE42-718EBF1833DC"}
Message: TOL: Failed to execute the command. Converting backup to VM 'USCLP008-HP_converted'
------------------------
Error code: 32795
Module: 114
LineInfo: 0xFDE974FD2EBCFEB8
Fields: {"$module":"disk_bundle_vsa64_14330"}
Message: Failed to convert the backup to the virtual machine.
------------------------
Error code: 32788
Module: 114
LineInfo: 0x28314C961DE7D8C6
Fields: {"$module":"disk_bundle_vsa64_14330"}
Message: Failed to recover virtual machine 'USCLP008-HP_converted' with ID 'vm:D7E5B17E-34AD-4296-985E-C04BD1A1FECA?type%3dmshyperv'.
------------------------
Error code: 768
Module: 149
LineInfo: 0xCE47D41EC1026A17
Fields: {"$module":"disk_bundle_vsa64_14330"}
Message: Recovery has failed.
------------------------
Error code: 1060
Module: 1
LineInfo: 0x145A191BFE9050C1
Fields: {"$module":"disk_bundle_vsa64_14330"}
Message: Failed to prepare an operation.
------------------------
Error code: 1
Module: 10
LineInfo: 0x6B87E19A45F35D88
Fields: {"$module":"disk_bundle_vsa64_14330"}
Message: Failed to prepare operations. Error code: 7 'Disk is not found. Ensure that all the hard disks are installed in the machine.'

 

This same message is happening to multiple conversion to VM jobs. The two server I am testing with are being converted to two different Hyper-V servers.

But if I delete the converted VM on the Hyper-V server the next time the backup job runs a new converted VM is created. 

0 Users found this helpful
Support specialist
Posts: 0
Comments: 1017

#1

Hello Jeff,

welcome to Acronis forums!

If I understood you correctly, the failure occurs when conversion to VM happens after incremental backup is created. However, everything is OK when the conversion happens after a full backup job is done.

There is a quite similar issue has been reported to Acronis Support Team. Please open a case with Acronis Support Team if you do not mind sharing your backup content for investigation purposes.

 

Beginner
Posts: 0
Comments: 1

#2

I have the same issue

see below error message

 

Activity 'Recovering virtual machine disks' failed. Failed to prepare operations. Error code: 7 'Disk is not found. Ensure that all the hard disks are installed in the machine.'
Support specialist
Posts: 0
Comments: 1017

#3

Hello Hakan,

welcome to Acronis forums!

I advise that you contact Acronis Support Team with this issue. Support engineers should provide you with a special build where this issue is fixed (ABR-233514).

Otherwise, please consult the respective KB article for a workaround https://kb.acronis.com/content/63495