Skip to main content

Issues restoring Hyper-v machines with hard drives larger than 1tb.

Beginner
Posts: 1
Comments: 4

So, overall Acronis 12.5 is great. The backup and restore process seems faster and to have greater compression. Restoring directly to Hyper-v works pretty well. Having all dependent backups in a single file is great. The web-based administration interface is relatively clear. However, I miss some of the features and options of 11.7.

In particular, I do not see why the ability to restore from tibx directly to a vhd/vhdx has been removed. It is much missed.

I have a couple of backed up Hyper-v VMs which have hard drives greater than 1tb. They backup without error. Files can be individually recovered without a problem. They can be "instant restored" without a problem. But when I attempt to recover either of them to a new Hyper-v VM I get Acronis Error 11 "The target size of the virtual disk is not supported by the selected virtual machine"

If I could simply restore the disk straight to a vhdx there wouldn't be a problem. Anyone know how to get around this?

Thanks.

Forum Star
Posts: 22
Comments: 2660

Top

Hi Jeremy,

The conversion of backups into .vhd files is pending to be added in future updates (internal feature ID: ABR-116928 - most likely will be added in one of next year updates).

However the issue you've run into should be investigated further: if you're backing up a Hyper-V VM and restore it to the same Hyper-V host then there should be no such error related to the disks sizes. Please clarify how you perform the backup, e.g. via Agent for Hyper-V or via Agent for Windows/Linux installed inside the VM? Also what's the Hyper-V version (is it 2008 for example?)? How the recovery is configured in GUI - do you select "restore to new" VM + do you configure the disks mapping in there (some screen shots would be quite helpful)?

Thank you.

Beginner
Posts: 1
Comments: 4

Top

Hi,

I am backing up all Hyper-V servers via the Agent for Hyper-V on  the host. Hyper-V manager version is 6.3.9600.16384 on Windows Server 2012 R2. For these test restores I've been picking "restore to new VM" and there are not really any options in the disk mapping to configure.

For these test restorations it is not standard for us to restore to the same live production Hyper-V server the VM was backed up from, but since you mentioned that I've tried it without success. Even if it worked this seems only a partial solution, as a primary real-world use for recovering one of these backups is that the original hardware is having problems and one would wish to recover to a different, working, Hyper-V host.

I am still getting the same error when attempting to restore to a new VM on the original Hyper-V host server - or any other restoration attempt to another Hyper-V host, of whatever version. It always fails with "The target size of the virtual disk is not supported by the selected virtual machine" error.

1.png
2.png
3.png
4.png
5.png
6.png

Beginner
Posts: 1
Comments: 4

Top

Here is an example activity log:

 

2017-09-21 11:21:22:695 9144 I0135003A: User is running command. Command=Recovering a virtual machine; User=XXXXXXXX; clientProfileID=498E7FD9-D563-254A-02F6-13901765D01E; clientSessionID=4670B56E-4E57-4434-BA2D-A8B16A2436D3; tenantID=00000000-0000-0000-0000-000000000000
2017-09-21 11:21:25:668 9144 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 00000000000013B4
2017-09-21 11:21:26:957 9144 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 000000000000026C
2017-09-21 11:21:28:012 9144 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 00000000000015B0
2017-09-21 11:21:29:408 10020 I0135003A: User is running command. Command=Recovering the entire virtual machine; User=XXXXXXXX; clientProfileID=498E7FD9-D563-254A-02F6-13901765D01E; clientSessionID=4670B56E-4E57-4434-BA2D-A8B16A2436D3; tenantID=00000000-0000-0000-0000-000000000000
2017-09-21 11:21:29:431 10020 I0135003A: User is running command. Command=Preparing for recovery of virtual machine; User=XXXXXXXX; clientProfileID=498E7FD9-D563-254A-02F6-13901765D01E; clientSessionID=4670B56E-4E57-4434-BA2D-A8B16A2436D3; tenantID=00000000-0000-0000-0000-000000000000
2017-09-21 11:21:34:178 10020 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 0000000000000D04
2017-09-21 11:21:35:449 10020 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 0000000000000E34
2017-09-21 11:21:36:363 10020 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 0000000000000E38
2017-09-21 11:21:39:981 10020 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 0000000000000CFC
2017-09-21 11:21:40:951 10020 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 0000000000000DEC
2017-09-21 11:21:42:909 10020 E0135003D: Error 0x135003d: Command has failed. Command=Recovering the entire virtual machine; tenantID=00000000-0000-0000-0000-000000000000
| trace level: error
| channel: tol-activity#621A2287-990F-49E9-BA7E-69615BA6A879
| line: 0x4a8728dc8a1c95a1
| file: k:\7048\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: service_process_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Recovering the entire virtual machine
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 6F80C46F-90AC-4F6F-9578-3CAEF754A637
| $module: service_process_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Recovering the entire virtual machine
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 6F80C46F-90AC-4F6F-9578-3CAEF754A637
| $module: disk_bundle_vsa64_7048
|
| error 0x728064: Failed to recover the entire virtual machine.
| line: 0x2b2c9ed481007bcd
| file: k:\7048\enterprise\migration\impl\manager_group_restore.cpp:325
| function: MigrationManagement::MigrationManagerImpl::RestoreEntireVm
| $module: disk_bundle_vsa64_7048
|
| error 0x728067: Failed to copy source disks to a new virtual machine.
| line: 0xfde974fd2ebcfe15
| file: k:\7048\enterprise\virtualization\features\convert_to_vm\manager_convert.cpp:588
| function: MigrationManagement::MigrationManagerImpl::CopyToNewVM
| $module: disk_bundle_vsa64_7048
|
| error 0x728013: Failed to create a dummy virtual machine.
| line: 0x28314c961de7d6bb
| file: k:\7048\enterprise\migration\impl\manager_vmbackup.cpp:2508
| function: MigrationManagement::MigrationManagerImpl::CreateAllocatedDummyVM
| $module: disk_bundle_vsa64_7048
|
| error 0x3c000b: The target size of the virtual disk is not supported by the selected virtual machine.
| line: 0x57dbe0d228f9e2d0
| file: k:\7048\core\fdisk\virtual\msvirtualdisk.cpp:233
| function: CheckMSDiskParameters
| $module: hv_srv_vsa64_7048
2017-09-21 11:21:42:135 10020 I00000000: Using ar_io_local to open '\\backup\Backups\vm-all-daily\' with token 0000000000000D00
2017-09-21 11:21:42:877 10020 I00BD0000: Creating dummy virtual machine 'bdmtest' on 'D:\'.
2017-09-21 11:21:42:883 10020 E0135003D: Error 0x135003d: Command has failed. Command=Preparing for recovery of virtual machine; tenantID=00000000-0000-0000-0000-000000000000
| trace level: error
| channel: tol-activity#65C2425C-E9A5-48C2-BFB6-DA325E4C4729
| line: 0x4a8728dc8a1c95a1
| file: k:\7048\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: service_process_vsa64_7048
|
| error 0x728064: Failed to recover the entire virtual machine.
| line: 0x2b2c9ed481007bcd
| file: k:\7048\enterprise\migration\impl\manager_group_restore.cpp:325
| function: MigrationManagement::MigrationManagerImpl::RestoreEntireVm
| $module: disk_bundle_vsa64_7048
|
| error 0x728067: Failed to copy source disks to a new virtual machine.
| line: 0xfde974fd2ebcfe15
| file: k:\7048\enterprise\virtualization\features\convert_to_vm\manager_convert.cpp:588
| function: MigrationManagement::MigrationManagerImpl::CopyToNewVM
| $module: disk_bundle_vsa64_7048
|
| error 0x728013: Failed to create a dummy virtual machine.
| line: 0x28314c961de7d6bb
| file: k:\7048\enterprise\migration\impl\manager_vmbackup.cpp:2508
| function: MigrationManagement::MigrationManagerImpl::CreateAllocatedDummyVM
| $module: disk_bundle_vsa64_7048
|
| error 0x3c000b: The target size of the virtual disk is not supported by the selected virtual machine.
| line: 0x57dbe0d228f9e2d0
| file: k:\7048\core\fdisk\virtual\msvirtualdisk.cpp:233
| function: CheckMSDiskParameters
| $module: hv_srv_vsa64_7048
2017-09-21 11:21:42:982 9144 E0135003D: Error 0x135003d: Command has failed. Command=Recovering a virtual machine; tenantID=00000000-0000-0000-0000-000000000000
| trace level: error
| channel: tol-activity#8B8EEEEE-C0E0-4062-B87F-C8C5B60BADFA
| line: 0x4a8728dc8a1c95a1
| file: k:\7048\enterprise\common\tol\gating_activity.cpp:251
| function: Tol::`anonymous-namespace'::BusinessActivityTracker::OnCompleted
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Recovering a virtual machine
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 08FF37D8-FB90-49A3-828B-B9A8CDA417B3
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Recovering a virtual machine
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 08FF37D8-FB90-49A3-828B-B9A8CDA417B3
| $module: disk_bundle_vsa64_7048
|
| error 0x728061: Failed to recover a virtual machine.
| line: 0x8cf6eec01474e1cb
| file: k:\7048\enterprise\migration\commands\group_restore\src\group_restore_logic.cpp:321
| function: MigrationManagement::GroupRestore::GroupRestoreCommandLogic::RunLogic
| $module: disk_bundle_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Tol::IsolateCommand
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 4504F8D4-2727-42AB-BB4F-A42EDBB790A0
| $module: mms_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Recovering the entire virtual machine
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 6F80C46F-90AC-4F6F-9578-3CAEF754A637
| $module: service_process_vsa64_7048
|
| error 0x1350016: TOL: Failed to execute the command. Recovering the entire virtual machine
| line: 0x8d165e86fb81959b
| file: k:\7048\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: 6F80C46F-90AC-4F6F-9578-3CAEF754A637
| $module: disk_bundle_vsa64_7048
|
| error 0x728064: Failed to recover the entire virtual machine.
| line: 0x2b2c9ed481007bcd
| file: k:\7048\enterprise\migration\impl\manager_group_restore.cpp:325
| function: MigrationManagement::MigrationManagerImpl::RestoreEntireVm
| $module: disk_bundle_vsa64_7048
|
| error 0x728067: Failed to copy source disks to a new virtual machine.
| line: 0xfde974fd2ebcfe15
| file: k:\7048\enterprise\virtualization\features\convert_to_vm\manager_convert.cpp:588
| function: MigrationManagement::MigrationManagerImpl::CopyToNewVM
| $module: disk_bundle_vsa64_7048
|
| error 0x728013: Failed to create a dummy virtual machine.
| line: 0x28314c961de7d6bb
| file: k:\7048\enterprise\migration\impl\manager_vmbackup.cpp:2508
| function: MigrationManagement::MigrationManagerImpl::CreateAllocatedDummyVM
| $module: disk_bundle_vsa64_7048
|
| error 0x3c000b: The target size of the virtual disk is not supported by the selected virtual machine.
| line: 0x57dbe0d228f9e2d0
| file: k:\7048\core\fdisk\virtual\msvirtualdisk.cpp:233
| function: CheckMSDiskParameters
| $module: hv_srv_vsa64_7048

 

Forum Star
Posts: 22
Comments: 2660

Top

Hi,

According to the screen shots there is 4TB disk being recovered, and looks like it's tried to be created as .vhd instead of .vhdx format, where .vhd has 2TB limitation on Hyper-V which explains the failure. Still I can't guess why this happens, since during recovery to new VM on Hyper-V we always enforce creation of disks in .vhdformat, unless the original format of the virtual disk was .vhd, which we preserve during recovery within the same platform.

I have tried to reproduce the problem in our QA lab but was unable to - created a VM with 4TB IDE disk, then backed it up and restored as new VM on the same Hyper-V 2012 host - all completed successfully. Therefore the issue in your case is related to specifics of the original backed up system. Can you please clarify the format of the original (backed up) VM disks + how the 4TB volume was organized in it (was it a logical volume on dynamic disk by any chance?)?

Thank you.

Forum Star
Posts: 22
Comments: 2660

Top

Jeremy,

Looks like I understood what happens - the problem is not with the 4TB disk, but rather with that 1.99TB one, which on original system is in .vhd format (very close to its limit). During recovery into new VM there is slight logical disk resize performed by Acronis Backup (to ensure system bootability and patch the boot loader), which expands the disk beyond 2TB limit for .vhd, while since we preserve the original disk format, it results in attempt to create 2TB+ disk in .vhd format and thus there is the failure from the Hyper-V. This is quite a rare "corner" case.

The solution would be to convert the original 1.99TB disk into .vhdx format from Hyper-V Manager (this is a standard operation) and then re-create the backup, so that information about .vhdx format is saved in it and thus upon recovery there will be no problems.

Thank you.

Beginner
Posts: 1
Comments: 4

Top

Thanks for the information. When I can have down time, I will convert the initial hard drive to vhdx, retry all operations, and let you know.

Beginner
Posts: 1
Comments: 4

Top

Thanks for your assistance - conversion of first vhd to vhdx did the trick, and I am able to successfully restore this system. I did not think of the size of the vhd as a problem, because there are only a few hundred gigabytes of data on it - it did not occur to me that Acronis would try to resize the drive even a bit.

Looking forward to the option to restore directly to a disk image being reintroduced, hopefully soon.

Thanks again!