locked
Constant nagging WHS2011 warning: A scheduled cleanup task for Client Computer Backup did not succeed RRS feed

  • Question

  • We are observing this issue on 3 different 2011 home servers builds.  we get the same warning in the WHS Alert Viewer and am stumped what we need to do to resolve it.  

    The warning is:

    A scheduled cleanup task for the Client Computer Backup did not succeed on [DATE 11:59:01 PM] and the task has not been successful in [NUMBER] days.  

    When one tries to "repair" the issue the warning simply goes away and is rearmed within an hour or so. The two client backup tasks in the Task Scheduler show they are running, but when you look at the status of the  "ConsistencyChecker", it shows an error code in the return status.   

    There is no obvious problems on the servers... All the client backups run fine..   Old backups are cleaned up on schedule as expected.

    Is this a common error on all WHS installs?     It's completely strange here as I'm seeing it on three totally different systems...

    Tuesday, June 25, 2013 11:48 AM

Answers

  • Found the solution.    The folder for the DriveLetter:\Server Folders\Client Computer Backups cannot use NTFS compression. Apparently during the cleanup task it dies for some reasons writing it's tmp files to the folder. Once we removed the compression flag on the folder the cleanup tasks ran properly and the server began recovering space due to the old backup sets slowly rotating out. To determine if you have the same issue, check the EventLog for a message similar to the following message:

    The Windows Server Client Computer Backup Service encountered the following error: Error code: 0x57 API name: SetFileValidData File: E:\ServerFolders\Client Computer Backups\{056EFA40-AAC5-4172-A519-5C43901B4C59}.tmp Error: The parameter is incorrect.

    Clearly this is a bug in Windows Server having issues working on NTFS compressed volumes.

    • Marked as answer by ArtieMcD Wednesday, September 3, 2014 3:04 AM
    Wednesday, September 3, 2014 3:03 AM

All replies

  • Hi,

    Thanks for posting your issue in the forum.

    Since you mentioned “ The two client backup tasks in the Task Scheduler show they are running, but when you look at the status of the  "ConsistencyChecker", it shows an error code in the return status. ” in the original post, would you please let me know the detailed error code you received? If all things go fine without any issue, maybe we could ignore the warning.

    Best Regards,

    Andy Qi


    Andy Qi
    TechNet Community Support

    • Marked as answer by Andy Qi Friday, July 5, 2013 9:24 AM
    • Unmarked as answer by ArtieMcD Wednesday, September 3, 2014 2:59 AM
    Thursday, June 27, 2013 10:03 AM
  • Found the solution.    The folder for the DriveLetter:\Server Folders\Client Computer Backups cannot use NTFS compression. Apparently during the cleanup task it dies for some reasons writing it's tmp files to the folder. Once we removed the compression flag on the folder the cleanup tasks ran properly and the server began recovering space due to the old backup sets slowly rotating out. To determine if you have the same issue, check the EventLog for a message similar to the following message:

    The Windows Server Client Computer Backup Service encountered the following error: Error code: 0x57 API name: SetFileValidData File: E:\ServerFolders\Client Computer Backups\{056EFA40-AAC5-4172-A519-5C43901B4C59}.tmp Error: The parameter is incorrect.

    Clearly this is a bug in Windows Server having issues working on NTFS compressed volumes.

    • Marked as answer by ArtieMcD Wednesday, September 3, 2014 3:04 AM
    Wednesday, September 3, 2014 3:03 AM