Backup failed with error code 517 & 2155348041

I'm running a Windows server2008r2 server with two folders on it that I need backed up to a remote NAS.  
I get EventId of 517 with error message of 2155348301 "The backup operation that started at '¿2013¿-¿12¿-¿03T15:36:58.178086600Z' has failed with following error code '2155348041' (None of the source volumes were backed up.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

Under Windows Server Backup -->View Details (of last backup ) I get this:"The version does not support this version of the file format."

What I'm not understanding is that on the NAS where the backup is supposed to go Windows creates a Folder"WindowsImageBackup" and you navigate down there is a .VHD file with the days backup on it. I cannot open the .VHD. So did it back it up or not?

Any thoughts or suggestions?
Scott
scott190Asked:
Who is Participating?
 
marsiliesConnect With a Mentor Commented:
It has to do with backing up to a Linux-based NAS running Samba. You have to change a setting in the Samba configuration on the NAS to get it to work:
http://blogs.technet.com/b/asiasupp/archive/2010/11/03/windows-server-backup-failed-with-error-quot-the-version-does-not-support-this-version-of-the-file-format-quot.aspx
Symptom:
You try to backup the files and folders on a windows server 2008 R2 system, the backup target is a share folder created in a storage drive on NAS device running Linux system. After starting the backup and taking several minutes, error message will appear “the backup of volume xxx could not be completed, Error: the version does not support this version of the file format.” The backup operation stopped before completing.
Before clarify the root cause of this problem, we should first let you know a background of windows server backup
 
Background:
The windows backup will have problems with sparse file only in case of "File Level (Selected file/folders in a volume)" backup. For "Block Level (full volume)" backup the sparse file is not a problem and the backup/recovery would succeed. This is because for Block Level Backup the .vhd file is never mounted whereas for File Level Backup the .vhd is mounted which does not support mounting of sparse file.
Thus, we can easily get the root cause
The failure happens while the .VHD file created by Windows Backup is mounted during backup.
The .VHD file is created as a sparse file and this is not supported by the native VHD driver and hence mounting of the .VHD failed.
 

After some investigation, we found that the "strict allocate = yes" option of Samba will force it to not have UNIX style behavior of creating sparse file. Solution is adding "strict allocate = yes" to the smb.conf and restarting the Samba.
You can get more information about smb.conf configuration on the following link
http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html


More info:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/a13cce27-c99c-42a3-83f2-d10ef6ca62a4/win-2008-r2-backup-fails-with-error-code-2155348301-there-was-a-failure-in-updating-the-backup?forum=windowsbackup
http://wiki.samba.org/index.php/Linux_Performance#Linux_and_Windows_File_systems
http://forum.qnap.com/viewtopic.php?f=189&t=48793
0
All Courses

From novice to tech pro — start learning today.