locked
Backup (and database clean up) failing with message "Can't read or write data on server" RRS feed

  • Question

  • This are messages in the Home Server Event Log:

    Failed backup:

    Unexpected error 0x57 from SetFileValidData on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\{6D6D99A0-D198-4901-B47F-CAF4E99D8E5B}.tmp: The parameter is incorrect.

    Failed database clean up:

    Unexpected error 0x57 from SetFileValidData on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Data.4096.8.new: The parameter is incorrect.

    Application Event log realted to failing database celan up:

    Application error. Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x00063604.

    THe backup fails suddenly (it was working before) by 2 of my laptops, other 2 are working OK. SInce the backup failure also database celan up fails with the message above. I searched extensivelly the forum and did delete all backup data and performed chkdsk /r (script) but this didn't solve the issue with those 2 PCs.

    I haven't found such srreor message reported at the forum so far.

    Any ideas are very much appreciated. THANKS!

    • Changed type Ocino Tuesday, February 1, 2011 11:05 AM
    Monday, November 15, 2010 1:48 PM

All replies

  • Were any errors reported when you ran chkdsk on your server's drives using the script?

    You can try deleting the entire backup database (found in D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}), then restarting your server; afterward you may have to run a database repair, reconfigure backups of your home computers (if you've made any exclusions), or both.


    I'm not on the WHS team, I just post a lot. :)
    Monday, November 15, 2010 2:21 PM
    Moderator
  • Can't help you with your error, but if "misery loves company" I've gotten that error every Sunday (the backup consolidation day) for the 11 months I've been using WHS.  I guess I'm an unsupported configuration (both the Home Server and all the backed-up machines are VMWARE virtual systems) but it is quite frustrating.

    In my case it means that the storage space gradually runs out and I have to periodically purge the database and start over, leaving the machines unprotected until each new first backup completes.

    There are certainly some lingering bugs in WHS, with this one a possibility.  We also can't backup files above about 60 gigs in size; WHS simply can't handle them.

    Art

    Tuesday, November 16, 2010 11:56 PM
  • Thank you for the tips.
    First to answer your question about the errors - when I ran chkdsk /r for the first time yes, there were quite some related to the backup files. So I deleted all backups, ran Database Clean up  (succesful) and also database repair to be sure (all OK). The errors didn't show up after that.

    Now I am running my wife's lapto backup whcih a lways workes, works this time too.
    However my Windows 7 64-bit Enterprise still throws the very same error which, when you look in the Home Server Console, is actually slightly different than what I find in hte Event Log (and is stated above). When I look at the failed drive I read:

    An error occured reading or writing fron server storage.
    D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\{7B291539-F4A7-4E70-839C-B49679E62BB0}.tmp
    SetFileValidData
    87

    I have done chkdsk /r on my laptop too, tried to backup just 1 drive (have 3 logical primary partitions) to no avail.
    I am almost convinced that the problem is on the server and not on my laptop.

    Any further help is greatly appreciated.


    Sunday, November 21, 2010 5:39 PM
  • I would try running chkdsk /r on all the drives in your server again, followed by another round of database repair and cleanup. If that doesn't work, you can delete the backup database (it's in D:\Folders\etc.), then do a repair, after which you may need to reconfigure backups for your PCs. the problem most likely doesn't exist on your laptop, but on your server, and the errors that were reported imply that whatever disk generated them is potentially failing.
    I'm not on the WHS team, I just post a lot. :)
    Sunday, November 21, 2010 6:00 PM
    Moderator
  • Thanks Ken.

    I have some more observations I have made doing an analysis of the systems, both WHS and my laptop.

    1. I have cleaned the database, ran chkdsk /r on all drives and I can backup other computers + I can backup my laptop's E: drive. So to my judgement my WHS backup works correctly.

    2. However (here is the catch) once I try to backup my laptop's C: or D: drive (all of them, including E: are ONE physical drive) I will receive above mentioned error.

    3. I can run database clean up and it will remove failed backup form the Computer backup list.

    4. Running chkdsk /r on all drives will reveal the following:

    a. On PRIMARY DISK D - Windows replaced bad clusters in file 82120 of name \folders\{00008~1\DA7840~1.DAT . And 14 more such files which however are not visible when I look at the D: drive vie Remote Access. Additionally it lists replacement of the bad clusters of 4 files which exist on the drive.

    b. On secondary (2TB) drive under C:\fs\1J2 - Same messages on 18 files, same 4 file names visible on the drive and some equal non-visible file names.

    5.Those erros were not on the drive before I attempted to back up my laptop's D: drive.

    QUESTION: Does observation in 4. mean that WHS duplicates the backup files by default? How come there are files reported by CHKDSK which are not visible in file explorer (hidden system files visible)?

    6. I run the same chkdsk /r on my laptop's D: drive and didn't find any errors, despite of the message from Acronis Drive Monitor which tells that my disk helth is critical becasue of Reallocated Sector Count is 47.

    The bad part:

    Running chkdsk /r on WHS didn't fix the errors. Repeated run still shows the same problems. I believe they dissapear when I delete the WHS backup folder content.

    Any ideas?



    • Edited by Ocino Sunday, June 26, 2011 3:47 PM Still didn't resolve those issues
    Tuesday, November 23, 2010 10:55 AM
  • Hi folks,

    I still didn't resolve the issues listed above. Meanwhile I found out that 2 of our laptops won't simply backup C: (boot) partition. On one of the laptops I replaced the harddrive to no avail. Only those 2 laptops are actually problematic, I added new PCs to our network meanwhile and they backup just fine.

    I am considering to upgrade to WHS 2011 now but it is unsure if this will resolve the issue.

    Thanks for any hint.

     

    Sunday, June 26, 2011 3:51 PM
  • This are messages in the Home Server Event Log:

    Failed backup:

    Unexpected error 0x57 from SetFileValidData on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\{6D6D99A0-D198-4901-B47F-CAF4E99D8E5B}.tmp: The parameter is incorrect.

    Failed database clean up:

    Unexpected error 0x57 from SetFileValidData on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Data.4096.8.new: The parameter is incorrect.

    Application Event log realted to failing database celan up:

    Application error. Faulting application whsbackup.exe, version 6.0.2423.0, faulting module whsbackup.exe, version 6.0.2423.0, fault address 0x00063604.

    THe backup fails suddenly (it was working before) by 2 of my laptops, other 2 are working OK. SInce the backup failure also database celan up fails with the message above. I searched extensivelly the forum and did delete all backup data and performed chkdsk /r (script) but this didn't solve the issue with those 2 PCs.

    I haven't found such srreor message reported at the forum so far.

    Any ideas are very much appreciated. THANKS!

    WHS backup SetFileValidData error and CqvSvc 9000 Warnings solved!!!! (At least on my setups)

    I was getting the same problem on all of my Windows Home Servers v1 (I had several reincarnations of them at home). After literally years of frustration on this error all that I was able to find online and get from Microsoft support was CHKDSK recommendations which didn't help ever. This problem (at least on all of my setups) was actually caused not by hard drive failures but by NTFS compression!!!

    My setup is:

    1. HP MediaSmart Server EX495 with Windows Home Servers v1 with PP3 and all Windows and HP updates.
    2. Drive C: - Compressed
    3. Drive D: - Compressed

    My symptoms were like this:

    1. Computer backups were failing with the following error was happening on all kind of files in backup folder:
      Unexpected error 0x57 from SetFileValidData on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\{5FF939E3-7F4B-488F-BED9-206A56F2E219}.tmp: The parameter is incorrect.
    2. When I was trying to repair backup database - it was sometimes failing but sometimes was saying that everything is successfully repaired.
    3. Database cleanup was failing pretty much all the time.
    4. Event log had Warnings like: CqvSvc.exe: Event ID=9000, Exception occurred:  System.Runtime.InteropServices.COMException

    Last month I was reading some msdn article and had to read documentation on SetFileValidData which explicitly warns you not to use this function on compressed files. It enlightened me and I went to my WHS and did the following:

    1. Remote Desktop to your WHS or use Advanced Admin Console
    2. Stop "Windows Home Server Computer Backup" service
    3. Open Windows Explorer on your WHS
    4. Open properties on folder: D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\
    5. Click on "Advanced" button and unselect "Compress content to save disk space". Hit OK twice.
    6. System will ask you if you want to do it recursively - select "Apply changes to this folder, subfolders and files". This will take a lot of time (may take hours - depending on the size of your backup database).
    7. Some of the files will still be shown as compressed because they are actually NTFS links and not real files. Ignore this.
    8. Since your backup database may be scattered across all your hard drives - you need to do the same on other hard drives. Note: All your WHS hard drives are linked under C:\fs.
    9. Uncompress all folders like Open properties on folder (you may have different kind of drive IDs instead of "1J9"): C:\fs\1J9\DE\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}
    10. Not all of your linked drives will have such folders; you may not found them at all. This is OK - it depends on a lot of factors. But if they exist - make sure that you uncompressed ALL of them.
    11. Start "Windows Home Server Computer Backup" service
    12. You may try to cleanup your computer backup database now or try to backup the computer where the backup was failing.
    13. If you still cannot backup the computer - Repair computer backup database, Cleanup computer backup database, Remove failing computer from WHS by uninstalling WHS connector, install WHS Connector again and join computer back to WHS and run Manual Backup. Some of this steps may take hours. First manual backup of my failing computer took 2 days over WiFi N with 300Mbs (it has a lot of games installed). But it worked!

    So what I have now:

    1. All my computer backups work now!!!
    2. WHS Computer Backup Database cleanup works all the time (although it takes a LOT of time).
    3. WHS Computer Backup Database is not compressed but it is not a big deal - like 30% bigger only.

    I am still getting "Fault bucket 1575745692." in the event log from time to time but it no longer seems like a big deal to me since all my computer backups work now!!!



    • Edited by Vladimir Lashchev Thursday, June 7, 2012 12:42 AM Clarified some troubleshooting steps
    • Proposed as answer by Vladimir Lashchev Thursday, June 7, 2012 12:42 AM
    Thursday, June 7, 2012 12:29 AM
  • Vladimir, if your backup folder was compressed at some point, it was done by you, because Windows Home Server doesn't compress any of the data it manages.

    I'm not on the WHS team, I just post a lot. :)

    Sunday, June 10, 2012 2:30 AM
    Moderator