Cannot write Windows 10 image backup

[Schmidt4711]

I use VM ESXi to manage our virtual workstations. All of them (until now Windows 7 Professional) are backed up using Windows Backup system images. Each workstation, each week, starts a batch file that essentially contains this line:

Wbadmin start backup -backupTarget:\\(our QNAP machine)\(path to individual backup folder)\ -include:C: -vssFull -quiet

This has worked for years for all Windows 7 machines.

Recently we have updated several VMs from Windows 7 Professional to Windows 10 Professional. Everything works fine, except the aforementioned backup procedure fails consistently. It seems to be impossible to write a Windows system image file to NAS!

The error message appears explicitly as a fail dialog box when the Windows image backup is executed manually. The following Windows error appears:

"There was a failure in preparing the backup image of one of the volumes in the backup set" (0x807800C5),

Also 0x80780081 (backup disk cannot be found) is shown.

I have been researching for hours and found numerous references to this problem. I have followed many of the fix ideas (like including "strict allocate = yes" in the SMB config file smb.conf on QNAP) but nothing works.

By the way, the image backup from Windows 10 VMs to a second virtual drive (instead of the NAS samba share) works perfectly, so it must be a QNAP or QNAP/Windows 10 problem.

Please help! Thank you in advance.

Many regards

Haegar

My setup:

• QNAP TS-410U
• QNAP Firmware: 4.2.0 Build 20160311
• All workstations run as VMs on ESXi 5.5 HP server
• All VMs runing Windows 7 Professional perform successful image backups as described
• All VMs running Windows 10 Professional fail as described, all current Microsoft patches (as of April 24, 2016) are installed

[aakerbeere]

Hi Schmidt
Have you got a solution for this? I have exactly the same problem since upgrading W7E*64 to W10E*64(1703). Until now i did not manage to set "strict allocate = yes" in smb.conf (not very familiar). But if it doesn't resolve it's not worth the try.
File based backup is working as expected, but i would like to do a system image to the nas for recovery reasons.

TS-459 Pro+

[aakerbeere]

sry

My profile was not up to date

Kind regards

[dolbyman]

make sure the WIN10 machines can reach \\NASNAME you might have to check that (netbios was disabled by default in earlier WIN10 builds and they are still finicky about workgroup names) .. or maybe just try \\NASIP instead

[aakerbeere]

Thx dolbyman

I can browse and select the appropriate nas share by W10 backup frontend. I can reach \\NASNAME and \\NASIP.
But still no success with systemimage.
File based backup works as expected

Cheers markus

[calaver4]

Hi, I've the same problem.
I tried to change SMB version and system image backup on a brand new share fails anyway.

bye

[dolbyman]

I will try it later at home ... but I have an older 4.2.x version of the firmware, so it might not really help

[Spider99]

This may not help but...

I use Veeam to backup my win10 machines daily - to get veeam/qnap to talk to each other so the backup can be written to a NAS share - i have to use the admin usr/password combo otherwise the backup will fail - not ideal but works

YMMV

Ps. This was on 4.2.x and now 4.3.3 210

[calaver4]

The problem started after upgrading firmware to QTS 4.3.3.0210 Build 20170606.
I tried with regular user and admin, both fails.

Any idea?

[aakerbeere]

I added "strict allocate = yes" to the appropriate shares section of "smb.conf". But no success. System Image is still failing.
And "System Image Backup (SIB) Solution" is set to "Deprecated" by MS and therefore might be removed in a future release.

regards

[oyvindo]

For what it's worth - I have noticed exactly the same when I try manually to back up a windows system image directly to the NAS. However, backing up from the Windows PC to a locally attached USB drive works just fine, and then manually copying the resulting backup folders to the NAS also works just fine. So I've concluded that there's some asyncronism happening between the NAS and the Windows image backup software that causes it to fail.
Have you also tried creating the backup manually from Windows 10 to the NAS? (and experienced the same error)....

[confour]

The problem started after upgrading firmware to QTS 4.3.3.0210 Build 20170606.
I tried with regular user and admin, both fails.

Any idea?

This is the same for me too !!!!!! - Since I updated QNAP firmware in June - I have been unable to get a Windows System Image Backup to go - same error everytime !!!
It still works on all my other external drives - USB and other Ethernet drives.

[confour]

The problem started after upgrading firmware to QTS 4.3.3.0210 Build 20170606.
I tried with regular user and admin, both fails.

Any idea?

This is the same for me too !!!!!! - Since I updated QNAP firmware in June - I have been unable to get a Windows System Image Backup to go - same error everytime !!!
It still works on all my other external drives - USB and other Ethernet drives.

This is now even worse -
I have Acronis, Macrium Reflect and Windows System Image - ALL failing when trying to start an 'incremental' backup.
Macrium and Acronis work only if I create a new Backup each time - which makes invalid the use of automating !!!
This is a real issue. Please help !!?

[Toxic17]

Not sure if this is related but noticed Windows 10 (1703) is now using SMB 3.1.1 which I dont think QNAP fully supports.

Just a guess, this maybe a SMB Multichanneling issue perhaps?

try disabling smb mutichannel on your Windows box.

from Powershell: Set-SmbClientConfiguration -EnableMultiChannel $false

to re-enable: Set-SmbClientConfiguration -EnableMultiChannel $true

its worth a try.

[oyvindo]

@Toxic17, I tried this, but regretfully it made no difference....