Windows 10: System Image Backup failed with odd message

I have tried to run a system image backup on my Win10 VM and it fails with an odd message.
the location must not be "compressed or encrypted or sparse".
Now I understand what compressed and encrypted mean and the location is not those, but sparse?

Details
Host: Win7 64bit SP1
Guest: Win10 64 bit build 10565
Location: Netgear ReadyNAS

with TBs to spare

:)

 

System Image Backup Failed with error: The backup failed. Windows Backup encountered an error when writing data to the backup target. (0x80780166) & 0x80070002 on Windows 10

Found another solution which may apply to some people.

I'd taken a system image and system repair disk before sending my laptop off for repair. As it turned out I was sent a new, identical unit instead. I successfully re-created my previous installation from those two backups. When I went to do a system image
of the new box some time later, to the same external disk, it failed on 0x80780166 and 0x80070002.

Most of the recommendations I found on the various fora seemed to relate to permissions and I realised the most likely explanation was that the new box couldn't access a folder created by the old box. I just deleted the old image backup folders and let it
start from scratch and it worked fine.

All of the above were done on Windows 10. The latest major update had just been applied prior to the most recent backup attempt.

But Microsoft, I think it's pretty lame that in 2016 you're still spitting out 0x80780166 and 0x80070002 when surely it would be no more trouble or expense to give something like "System image does not have permission to read folder xx\yy\zz". It would save
people a lot of time and exasperation. Just sayin'.

 

System Image Backup Failed with error: The backup failed. Windows Backup encountered an error when writing data to the backup target. (0x80780166) & 0x80070002 on Windows 10

I couldn't agree more, Andy. As hard as MS is trying to make this edition the best ever, little things like this are so discouraging. Thank you. John

 

Try defragmenting your hard drive. I believe that by sparse, it wants a contiguous location of free disk space to save the image.

I've never thought of a location as being sparse, only an existing file could be sparse as far as I knew.

 

also try extend or shrink the destination partition

 

Thanks for both the replies.
Unfortunately the location I quoted is in a device which I cannot control. It is a Netgear ReadyNAS NV+ which appears to have a Linux type of O/S. I know nothing about Linux. The device is quite old and has been working for some time so the disks (Raid) may be fragmented but I know of no way of 'de-fragmenting' them. The device is so old that Netgear no longer support the version I have.

 

Oh ok. That's the sort of information that one would include in the initial post *Smile

Since it's a NAS, and runs Linux, ignore my last post. Fragmentation isn't the issue.


How are you accessing the NAS, via SMB (Windows share), or WebDAV, or FTP or something else? I know Linux better than I know Windows, and if you want to get this working, I'm determined to help.

 

I thought I had given enough info in the beginning Location a Netgear ReadyNAS.
However thanks for your continued help.
In windows 7 and windows 10 there is a Backup Restore function (app or tile or something).
In Windows 7 you can select a network location by opening the dialog and entering the location in the way you may recognise L: \\ReadyNAS\FolderName Windows 7 then checks that it can connect to that location and then you go on and setup what you want to backup. When you start the backup it appears to assemble the data and then starts to write to the Location. It is at that point I get the error Backup failed with the details I quoted "the location must not be "compressed or encrypted or sparse".
In Windows 10 I have to map the location drive and folder to a Drive letter as the latest builds (insider) do not display the computer that supports the NAS. It cannot therefore be selected as the network location. Having mapped the drive\folder the backup proceeds in the same manner as in Win 7 and fails with the same error.
Thinking a little more clearly I think this may not be a Win 10 problem but a problem with the NAS support s/w but I could not understand the "sparse".

 

It doesn't seem to be Windows 10 per se - you need to update the Samba conf file on the NAS.

Windows Server Backup failed with error "The version does not support this version of the file format" - Microsoft Reduce Customer Effort Center - Site Home - TechNet Blogs

See also Windows and Linux NAS file system compatibility | BackupAssist

 

Thanks I will investigate the possibility.

 

From looking into similar problems with ReadyNAS devices, the true samba configuration file isn't located in the standard location.

Apparently editing the normal file located at /etc/samba/smb.conf will only result in a temporary edit. Rebooting will regenerate that file based on the file at:

Code: /etc/frontview/samba/smb.conf.*[/quote] That's the one you'll want to edit.

 

A complete failure.
I cannot find the folder or files you indicated.
There does not seem to be any way I can access them. They do not show up when I use a browser to access the ReadyNAS or if I examine the contents using Windows file explorer.

there is no folder etc that I can find.