Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by stefanwoe

  1. After having back upped my machines for a number of years using Retrospect 8.5, i recently started removing some old unneeded snapshots in order to save space. That went well for one machine, but on the other machine i now see errors that i can not recover from. The point here also was, that the NAS target device once shut down during operation by its timetable. So i now tried several times to recreate or repair the Catalog using the according function in Retrospect 8.5 and i also repeated this with a evaluation of 11.5. But still i get many errors like: Fehlerhafter Backup-Set-Vorspann: 0xa573d3c7 at 662.585.085.952 Die für die Datei "xyz..." generierte MD5-Prüfsumme stimmt nicht mit der gespeicherten überein. which google translates to: Incorrect backup set header: 0xa573d3c7 at 662.585.085.952 The MD5 checksum generated for the file "xyz" does not match the stored values. Hundreds of the first message, and about 10 from the second one. What can be possible done here? And how deep is the damage? I made some tests and still i can search for and recover various files. Thanks a lot for answers. Stefan
  2. The problem occurs with both my NAS: 1) 500GB Teac Alu NAS 2) Iomega Home Network HDD 1TB According to retrospect Support in germany, a Catalog rebuild results in a certain "stresstest" for a NAS. I cant see, why a NAS should fail, where a USB mounted device succeeds. It may be slower but it must work. The real pain is that Retrospect shows no such hint. I only see the message "Disk contains no Backup data" - which is untrue. If there would be a hint "this might be a NAS-Problem" - i would have needed a couple of hours less.
  3. Solution Found! After purchasing a Support case for 80.-Euros and after having the German Support asking in America the solution is: Rebuilding catalog files does not work - sometimes - with NAS-Drives. If i connect the same drive via USB, the catalog rebuild works! It i use it via LAN id does not! Why are these basic things are so difficult sometimes!
  4. I doubt strongly that the data is corrupted. It was created through a initial backup a few days before and i was able to browse it, using the BackupSet-File. If i dont use the BackUpSet file, i can not rebuild it. All this is rather a test, but i am shocked that such a important function does not work. I always stored my catalog files on the same volume as my data. I cant understand why it should be useful to store it on the drive which's fault i want to be prepared on. NOW - i know that that my strategy was right. So - do you have any other hint?
  5. Yes of course - i tried every single folder in the whole hierarchy. From the root down to th folder where the rdb files are.
  6. I just tried to rebuild a catalog from all the existing rdb files. It seems to be impossible. I point Retrospect 7.6.1 to the directory of the rdb-files and it tells me that this volume does not contain any backup data. I retried it with every directory level. What am i doing wrong ?
  • Create New...