locked
Backup Repair Crashes RRS feed

  • Question

  • My Index.4096.dat file got corrupted a few days ago, probably due to a power outage.   As a result, my entire backup set seems lost.  I was hoping the backup repair tool might help with this condition, but it appears that it won't.  Is there any way to get my backups back, or do I have to start over?

    Note that backup server bombs out with the same error.  I guess I don't have to tell you how frustrating this is.  I was hoping to rely on WHS to keep data from older computers that I may no longer have safe, but this appears to not be a good idea.

    [6/10/2008 9:49:00 AM  ac0] *******************************************************************
    [6/10/2008 9:49:00 AM  ac0] Backup Repair Tool Started.
    [6/10/2008 9:49:00 AM  ac0] Unexpected error 0x26 from unexpected EOF on D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\Index.4096.dat: Reached the end of the file.
    [6/10/2008 9:49:00 AM  ac0] Process HomeServerConsole failed at d:\wssg_src\whs_v1se\qhs\src\backup\util\diskfile.cpp(359).

    As an aside: as a result of this error, I cannot finish updating the connector on my client machines because they can't get through the configuring backup step.

    Another nit: it's a little unfriendly for the WHS Console to just exit without any message when this happens.  I had to look at the log files to know that an error occurred.



    Tuesday, June 10, 2008 4:59 PM

Answers

  • Please file a bug on Connect at http://connect.microsoft.com/WIndowsHomeServer and submit your CAB files using the Toolkit.  If you don't submit bugs via Connect with your logs - then the team can do nothing to help you.

     

    Tuesday, June 10, 2008 5:22 PM
  • The steps are documented in the Release Documentation for installing the Toolkit on the server

     

    Tuesday, June 10, 2008 5:44 PM

All replies

  • Please file a bug on Connect at http://connect.microsoft.com/WIndowsHomeServer and submit your CAB files using the Toolkit.  If you don't submit bugs via Connect with your logs - then the team can do nothing to help you.

     

    Tuesday, June 10, 2008 5:22 PM
  • While it's likely that you'll have to start over, I certainly agree that the Repair feature shouldn't crash the console like that. I would suggest that you submit a bug on Connect, with Talq logs from at least the server.
    Tuesday, June 10, 2008 5:24 PM
    Moderator
  • I will do that.  I'm assuming the toolkit can be installed on the server directly if I can't get my connector to run?
    Tuesday, June 10, 2008 5:34 PM
  • The steps are documented in the Release Documentation for installing the Toolkit on the server

     

    Tuesday, June 10, 2008 5:44 PM
  • The bug has been reported, with talq data (ID 350302).
    Tuesday, June 10, 2008 6:04 PM
  • Thank you!

    Tuesday, June 10, 2008 6:10 PM