Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
False Failed Backup Error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote




    I am running WHS SP2 PP1 with three XP clients as a backup server with the backup window set each night from Midnight to 7 a.m.

    Almost every night I get an email messsage from the Remote Notification Add-In that the "Digital" client backup has not run when it actually did run successfully.

    The error below sent by WHS at 5:15:33 a.m. on 2/21/09 says that the "Digital" backup had not been run since 2/20/09.  I logged into the WHS Console and checked the computer backups.  The "Digital" client was backed up on 2/20 at 1:58 a.m. and it was backed up again on 2/21 at 5:15 a.m.  It is interesting to me that the error saying the backup had not run since 2/20 was issued 33 seconds after the backup ran at 5:15 a.m. on 2/21.

    The actual error is below:

    Got Error: WHS.Backup.Machine.{1CA19E6D-D02F-484B-B1A8-77D13F1EEFEA} Type:WHS_NOTIFICATION_ADD Head:DIGITAL Backup Warning Desc:DIGITAL has not been successfully backed up since 2/20/2009. Ensure that DIGITAL is turned on and connected to you network, or use "Backup Now" to back it up manually.

    I have submitted two bug reports to Microsoft Connnect including the CABs from the WHS and the 3 clients.  Connect told me each time everything is working as designed - pretty cut and dried with no room for discussion.  Connect has been worthless in answering my question to resolve this issue.

    This false error message has occurred sometimes in the past for the other two clients but 95% of the time the false error message occurs on the "Digital" client.


    1.)  Does anyone know why I am getting a an error telling me the backup has not run when it actually did run
    successfully?

    2.)  Does anyone know what time of day or night the WHS 24 hour clock looks at the backups to determine if they did or did not run within that 24 hour period?

    3.)  When "View Backups" states 1:58 a.m. is that the time the backup started or completed?

    4.)  Can anyone give me a telephone number for Microsoft that I can call and pay money to talk to a Microsoft WHS tech support person to discuss and resolve this problem?

    This issue has been going on for months.  I have previously posted this same issued on the Microsoft WHS forum and the We Got Served forums with no solutions.

    Thanks everyone for your help!
    Best Regards, Bill Artman Kansas City - USA
    Sunday, February 22, 2009 7:03 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Bill Artman said:

    Got Error: WHS.Backup.Machine.{1CA19E6D-D02F-484B-B1A8-77D13F1EEFEA} Type:WHS_NOTIFICATION_ADD Head:DIGITAL Backup Warning Desc:DIGITAL has not been successfully backed up since 2/20/2009. Ensure that DIGITAL is turned on and connected to you network, or use "Backup Now" to back it up manually.

    1.)  Does anyone know why I am getting a an error telling me the backup has not run when it actually did run
    successfully?


    Hi,

    You can probably solve this by removing DIGITAL from the Computers & Backup tab and then add it again. But by this your current backups for this client will be lost. So maybe you'd try this as a last resort.

    One reason for you false notifications I can think of is when the WHS backup error/warning thresholds for this machine are set incorrectly? You can check this by remoting into the WHS Desktop. From there start->run->type: "regedit"<enter>

    (Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor)

    Check the values at:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Backup\{1CA19E6D-D02F-484B-B1A8-77D13F1EEFEA}

    • OverdueWarningThreshold
    • OverdueErrorThreshold

    These key should hold the number of hours before the client is notificated. The D_WORD value should be greater then (decimal) 24.

    Theo.

    No home server like Home Server
    Sunday, February 22, 2009 9:23 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Bill Artman said:

    Got Error: WHS.Backup.Machine.{1CA19E6D-D02F-484B-B1A8-77D13F1EEFEA} Type:WHS_NOTIFICATION_ADD Head:DIGITAL Backup Warning Desc:DIGITAL has not been successfully backed up since 2/20/2009. Ensure that DIGITAL is turned on and connected to you network, or use "Backup Now" to back it up manually.

    1.)  Does anyone know why I am getting a an error telling me the backup has not run when it actually did run
    successfully?


    Hi,

    You can probably solve this by removing DIGITAL from the Computers & Backup tab and then add it again. But by this your current backups for this client will be lost. So maybe you'd try this as a last resort.

    One reason for you false notifications I can think of is when the WHS backup error/warning thresholds for this machine are set incorrectly? You can check this by remoting into the WHS Desktop. From there start->run->type: "regedit"<enter>

    (Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor)

    Check the values at:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Home Server\Backup\{1CA19E6D-D02F-484B-B1A8-77D13F1EEFEA}

    • OverdueWarningThreshold
    • OverdueErrorThreshold

    These key should hold the number of hours before the client is notificated. The D_WORD value should be greater then (decimal) 24.

    Theo.

    No home server like Home Server
    Sunday, February 22, 2009 9:23 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote


    Hello Theo;

    Thank you for your reply.  Hopefully you put me on the right track.  I didn't realize that the long character string in the error message was from the registry!

    I checked the registry as you suggested, and for all three of the client machines the OverdueWarning AND OverdueErrorThreshold was set to a D_WORD decimal value of 24.  I changed the setting for all three clients to 25 since you said the value should be greater than 24.

    We will see tonight if that fixes the problem.  I will give it a couple of days to sync in and will report back.

    Thanks very much for your help!  Have a super week!
    Best Regards, Bill Artman Kansas City - USA
    Monday, February 23, 2009 2:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Bill Artman said:



    Hello Theo;

    Thank you for your reply.  Hopefully you put me on the right track.  I didn't realize that the long character string in the error message was from the registry!

    I checked the registry as you suggested, and for all three of the client machines the OverdueWarning AND OverdueErrorThreshold was set to a D_WORD decimal value of 24.  I changed the setting for all three clients to 25 since you said the value should be greater than 24.

    We will see tonight if that fixes the problem.  I will give it a couple of days to sync in and will report back.

    Thanks very much for your help!  Have a super week!

    Best Regards, Bill Artman Kansas City - USA



    FYI, the default for Warning is Decimal 120 (5 days) and the default for Error is Decimal 360 (15 days).  I don't think doing 25 hours is a good idea (since it's not an even amount of days).
    Tuesday, February 24, 2009 1:49 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote


    kariya21 -

    Thanks for your reply!  I am a professional photographer who is using WHS to backup my image files after burning them to DVD.  I really want to know for lack of a better word immediately (within the next day) if a backup does not run.  Waiting 5 days to get a warning is much to long.  I understand what you are saying about 25  hours not being an even number of days.

    Have super day!
    Best Regards, Bill Artman Kansas City - USA
    Tuesday, February 24, 2009 2:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Bill Artman said:



    kariya21 -

    Thanks for your reply!  I am a professional photographer who is using WHS to backup my image files after burning them to DVD.  I really want to know for lack of a better word immediately (within the next day) if a backup does not run.  Waiting 5 days to get a warning is much to long.  I understand what you are saying about 25  hours not being an even number of days.

    Have super day!

    Best Regards, Bill Artman Kansas City - USA



    In that case, I would suggest setting the warning to 48 (2 days) and the Error to 72 (3 days).
    Wednesday, February 25, 2009 4:54 AM
    Moderator