Skip to main content

Backup & Recovery 10 Advanced Virtual - backup fails if hyper-v VM disk attached through symbolic link

Thread needs solution

Hi! I'm evaluating Acronis B&R 10 Advanced Virtual Edition and have troubles with backup. On two of my Hyper-V VMs (one - Win2008 server, second - Win2003 server) backup fails. Other VMs backup are ok. I try to investigate the problem and found what both this VMs are using "fixed size" VHD disks (other VMs use dynamic). Host computer is Windows 2008 Server (Hyper-V v1). But the same problem on second computer with Windows 2008 Server R2 (Hyper-V v2). I'm using latest (12497) build of ABR. Below is a sample error log. This is very strange, does Acronis B&R 10 AVE have problems with fixed size vhd disks? Regards, Yuri

sample error log:
1 Information 26.11.2010 3:48:23 Priority changed to Low.
2 Information 26.11.2010 3:48:26 Accessing VHD file snapshot 'C:\hyper-v\vms\srv-router\Snapshots\1D1F86DC-B00D-4440-8B05-50F676FD8CBE\srv - router fixed_7644242B-6731-480C-8907-46D2CE96EBC3.avhd'...
3 Information 26.11.2010 3:48:28 Attempting to create a multi-volume snapshot.
4 Information 26.11.2010 3:48:28 Adding 'C:\hyper-v\vms\srv-Router' to multi-volume snapshot...
5 Information 26.11.2010 3:48:28 Adding 'C:\hyper-v\vms\srv-router\' to multi-volume snapshot...
6 Information 26.11.2010 3:48:28 Adding 'C:\hyper-v\vms\srv-router\Snapshots\1D1F86DC-B00D-4440-8B05-50F676FD8CBE\srv - router fixed_7644242B-6731-480C-8907-46D2CE96EBC3.avhd' to multi-volume snapshot...
7 Information 26.11.2010 3:48:28 Adding 'C:\hyper-v\vms\srv-router\disks\srv - router fixed.vhd' to multi-volume snapshot...
8 Information 26.11.2010 3:48:28 Setting up the 'use VSS' option...
9 Information 26.11.2010 3:48:28 VSS component is included in the multi-volume snapshot: [writer class='66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE', writer instance='00000000-0000-0000-0000-000000000000', component name='1D1F86DC-B00D-4440-8B05-50F676FD8CBE'].
10 Information 26.11.2010 3:48:30 The multi-volume snapshot has successfully been created.
11 Error 26.11.2010 3:48:30 Failed to open raw hard disk data file 'srv - router fixed_7644242B-6731-480C-8907-46D2CE96EBC3.avhd'.
Additional info:
--------------------
Error code: 94
Module: 83
LineInfo: 383ffdb092990da7
Fields:
Message: Failed to open raw hard disk data file 'srv - router fixed_7644242B-6731-480C-8907-46D2CE96EBC3.avhd'.
--------------------
Error code: 94
Module: 83
LineInfo: 383ffdb092990dea
Fields:
Message: Failed to open raw hard disk data file 'srv - router fixed_7644242B-6731-480C-8907-46D2CE96EBC3.avhd'.
--------------------
Error code: 2
Module: 60
LineInfo: ceff4fee961a414f
Fields:
Message: Error: unable to open virtual disk.
--------------------
Error code: 17
Module: 4
LineInfo: 497a70fdd71a3fb8
Fields:
Message: The specified file does not exist.
--------------------
12 Error 26.11.2010 3:48:30 Source is not selected. The operation has been terminated.
Task 'srv-Router - Level 2 backup' has failed on machine 'server2008.binarysense.local'.

Attachment Size
sysinfooutput.zip 5.15 MB
0 Users found this helpful

I found source of error - this is not a fixed disks fault. The problem with NTFS symbolic link.
Let me explain. For example, I use C:\Hyper-V for Hyper-V VMs, but after some time - no free space on drive C:, so we just move (keeping access rights) some folders with disks files (vhd) to another drive and make a symbolic link (symlink) to this folder in source folder on drive C:
So, we don't need to change anything in VMs settings and it keeps running as usual.
But if we try to backup this VM using ABR - we receive error as above. If we change VM settings, so attached disks paths will show to real .vhd files (not through symbolic link) - all backups are successful.

Yes, I understand what this scheme with symlinks are not good, but sometimes we need to use it :)

ps: I change subject of topic, so it tells about real problem.

Hello Yuri,

Thank you for posting.

I really appreciate that you have taken the time to report your findings. Although we do not support symlinks at the moment, we have created a task for our Development team to either implement the support in the next builds of Acronis Backup&Recovery or at least create more comprehensible error messages, so that the cause of this issue is clearly understood.

If you need additional assistance, please let me know.

Thank you.