locked
Cannot restore from WHS backup - RestoreVerifier: VerifyClusterBad: expected cluster data for cluster 0 RRS feed

  • Question

  • I have previously not had any problems restoring from WHS backups.
    Today however, the restore engine halted at 79% - which is quite common as i can see. I tried restoring to another PC, with the same result, so the issue seems to be server side.

    Here's a snippet from the logfile which actually explains the problem - my question is: How to fix it?

    [22-10-2008 19:04:14  b70] RestoreVerifier: VerifyClusterBad: expected cluster data for cluster 0
    [22-10-2008 19:04:14  b70] RestoreVerifier: VerifyClusterBad: expected cluster data for cluster 0
    [22-10-2008 19:04:14  b70] RestoreVerifier: VerifyClusterBad: expected cluster data for cluster 0
    [22-10-2008 19:04:14  b70] RestoreVerifier: VerifyClusterBad: expected cluster data for cluster 0
    [22-10-2008 19:04:14  b70] RestoreVerifier: VerifyClusterBad: expected cluster data for cluster 0

    [22-10-2008 19:04:16   e8] Session: DoGetConfiguration
    [22-10-2008 19:04:16   e8] Session: DoGetConfiguration
    [22-10-2008 19:04:23   e8] Session: DoGetConfiguration
    [22-10-2008 19:04:23   e8] Session: DoGetConfiguration
    [22-10-2008 19:04:43   e8] Session: DoGetConfiguration
    [22-10-2008 19:04:43   e8] Session: DoGetConfiguration
    [22-10-2008 19:05:14  8d8] Listener TcpEventCallback
    [22-10-2008 19:05:14  8d8] Listener TcpConditionCallback from 192.168.1.16
    [22-10-2008 19:05:14  cf4] Session: ThreadMain for 00ECA4D8
    [22-10-2008 19:05:14  cf4] Creating the server instance.
    [22-10-2008 19:05:14  cf4] Created the server instance.
    [22-10-2008 19:05:14  cf4] Client subject: CN=C8D673F730B9742BA80D54D1AA579B74C
    [22-10-2008 19:05:14  cf4] Client issuer: CN=MABA76BF089914861A525968307CA6F22
    [22-10-2008 19:05:14  cf4] Auth succeeded, ready for command
    [22-10-2008 19:05:14  cf4] Header: 5, Trailer: 16, MaxMessage: 16384
    [22-10-2008 19:05:14  cf4] Partner cert name is <CN=C8D673F730B9742BA80D54D1AA579B74C>
    [22-10-2008 19:05:14  cf4] Partner GUID is {8d673f73-0b97-42ba-...}
    [22-10-2008 19:05:14  cf4] Session: DoBeginVolumeConfig {8D673F73-0B97-42BA-80D5-4D1AA579B74C}
    [22-10-2008 19:06:14   e8] Session: DoGetConfiguration
    [22-10-2008 19:06:14   e8] Session: DoGetConfiguration
    [22-10-2008 19:26:01  b70] Error 10054 receiving data from partner
    [22-10-2008 19:26:01  b70] Breaking TLS sesssion...
    [22-10-2008 19:26:01  b70] Read 0 bytes, hr=80072746
    [22-10-2008 19:26:01  b70] RestoreVerifier: Maximum error count reached
    [22-10-2008 19:26:01  b70] Restore of MAIN E:\ by XPS1730 has failed.
    [22-10-2008 19:26:01  b70] Session: ThreadMain end for 00ED9DC0
    [22-10-2008 19:26:01  b70]  TLS::~TLS going away (first time)...
    [22-10-2008 19:26:01  b70] Breaking TLS sesssion...

    (There are around 100 lines similar to the first lines in the snippet.)

    It's a bit unclear to me weather this is a disk or a database error.

    Any ideas?

    Best regards,

    Kasper Hansen

    Wednesday, October 22, 2008 5:38 PM

Answers

  • Kasper,

    It could also be worthwhile checking both the server and client logs to see if they show anything. However, it sounds as though you maybe have a corrupt database.
    ( If you have the Toolkit installed, it provides a means of viewing these logs ).

    If you haven't already, it would be helpful if you could follow the info in Lara's post, and send in a bug report. The 79% bug is one of those with numerous possible causes, I believe they are narrowing them down, but any info would help.

    I'm willing to bet though, that you may have to delete all current backups and start again - not a good situation.

    Colin





    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Wednesday, October 22, 2008 6:13 PM
    Moderator

All replies

  • Kasper,

    Sorry to hear , it's PITA when there's a problem like this.
    Have you ran the Backup Repair tool available in the Backups section of the Settings menu in the Console?

    Colin

    ps: there is also a database checking tool, but this is an Alpha release, but if you can take a copy of your backup off, it could be worth trying.





    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Wednesday, October 22, 2008 5:49 PM
    Moderator
  • No, I haven't run the backup repair - I didn't know it existed.
    I'll report back a bit later, when it's done.

    Luckily I have a backup of the backup files AND an additional backup of that specific PC, so this isn't the end of the world - but it is of course worrying.
    This corruption is also likely the reason that none of my computers have been backed up the last few weeks. I noticed it, but haven't had the time to look into it.

    Best regards,

    Kasper Hansen
    Wednesday, October 22, 2008 6:03 PM
  • Kasper,

    It could also be worthwhile checking both the server and client logs to see if they show anything. However, it sounds as though you maybe have a corrupt database.
    ( If you have the Toolkit installed, it provides a means of viewing these logs ).

    If you haven't already, it would be helpful if you could follow the info in Lara's post, and send in a bug report. The 79% bug is one of those with numerous possible causes, I believe they are narrowing them down, but any info would help.

    I'm willing to bet though, that you may have to delete all current backups and start again - not a good situation.

    Colin





    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Wednesday, October 22, 2008 6:13 PM
    Moderator
  • Unfortunately I had no luck with the repair. I'm in the process of restoring the 200gb backup of the backup files from an external harddrive now.
    I'll take a look at Lara's post tomorrow and submit a bug report, as soon as I have the time.

    Thank you very much for your help.

    Best regards,

    Kasper Hansen
    Wednesday, October 22, 2008 9:16 PM