The deployment of the backup ends with an error
Good afternoon! A backup of the physical machine was created. The task is to virtualize it on hyper v. Acronis returns an error during recovery:
Command 'Recovering disks/volumes to new VM 'vm:255521EA-D9F6-4161-9194-1EFC63AF492B?type%3dmshyperv'' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields: $module : service_process_vs_50242
Message: Command 'Recovering disks/volumes to new VM 'vm:255521EA-D9F6-4161-9194-1EFC63AF492B?type%3dmshyperv'' has failed.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields: TraceLevel : 1, $module : disk_bundle_vs_50242
Message: TOL: Failed to execute the command. Recovering disks/volumes to new VM 'vm:255521EA-D9F6-4161-9194-1EFC63AF492B?type%3dmshyperv'
--------------------
Error code: 32788
Module: 114
LineInfo: 28314c961de7d41b
Fields: $module : disk_bundle_vs_50242
Message: Failed to recover virtual machine 'server_nt' with ID 'vm:255521EA-D9F6-4161-9194-1EFC63AF492B?type%3dmshyperv'.
--------------------
Error code: 768
Module: 149
LineInfo: ce47d41ec10269fd
Fields: $module : disk_bundle_vs_50242
Message: Recovery has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: 145a191bfe9050c3
Fields: $module : disk_bundle_vs_50242
Message: Failed to prepare an operation.
--------------------
Error code: 1
Module: 10
LineInfo: 6b87e19a45f35d7a
Fields: $module : disk_bundle_vs_50242
Message: Failed to prepare operations. Error code: 3 'Internal error: Script is inconsistent.'
--------------------
Judging by the logs, acronis reports that the hardware on hyper v is not compatible with the one on the previous machine. How to successfully deploy an image on hyper v?
Jose Pedro Magalhaes wrote:Hello,
Thank you for participating!
Please try the following solutions:
Reboot the machine and attempt the recovery again.
Recover the VM using the bootable media:
--- Create bootable media - https://kb.acronis.com/content/21728
--- Create a new VM and boot it from the bootable media.
--- Recover the VM directly from there.
Feel free to leave a comment if you have any questions.
Thanks in advance!
The recovery process freezes by 54% without any errors.
Player wrote:Jose Pedro Magalhaes wrote:Hello,
Thank you for participating!
Please try the following solutions:
Reboot the machine and attempt the recovery again.
Recover the VM using the bootable media:
--- Create bootable media - https://kb.acronis.com/content/21728
--- Create a new VM and boot it from the bootable media.
--- Recover the VM directly from there.
Feel free to leave a comment if you have any questions.
Thanks in advance!
The recovery process freezes by 54% without any errors.
Hello!
Please perform the following actions:
-
Reboot the VM: Log in to your virtualization platform or management console and initiate a reboot for the specific virtual machine.
-
Check RAM Allocation: Ensure that the VM has enough RAM allocated to handle the processing requirements. If you suspect that insufficient RAM is causing the issue, you can increase the allocated RAM. Here's how you can do it:
a. Stop the VM: If the VM is running, shut it down gracefully. b. Adjust RAM Allocation: In your virtualization platform's settings or control panel, find the option to adjust the RAM allocation for the VM. Increase it to a suitable value. c. Start the VM: Once the RAM allocation is increased, start the VM again.
-
Verify Process Status: Before assuming the process is frozen, make sure to verify if it's actually stuck or just slow due to the nature of the task (like a large backup). Monitor the VM's performance and resource utilization to confirm if the process is indeed frozen.
-
Monitor Resource Usage: Utilize your virtualization platform's monitoring tools or external tools to track the VM's resource usage (CPU, RAM, disk, network). This will help you determine if there are any resource bottlenecks causing the issue.
-
Additional Troubleshooting: If the above steps do not resolve the issue, consider these further troubleshooting steps:
a. Check Logs: Examine system logs or logs related to the process to gather more information about what might be causing the freezing. b. Resource Constraints: Ensure that other VMs or applications running on the same host are not consuming excessive resources, which could impact the VM in question. c. Software Updates: Ensure that the VM's operating system and relevant software are up to date with the latest patches and updates.
Remember, before making any changes to your VM or its settings, it's a good practice to back up your data or take a snapshot, especially if you're making significant changes like increasing RAM allocation.
Thanks in advance!