Jump to content

Search the Community

Showing results for tags 'md5 digest'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. I have seen this behavior since v9, and it seems to be rare, but about the same. You can see my post about this in: http://forums.retrospect.com/index.php?/topic/151548-verify-vs-copy-and-data-errors/ ( and http://forums.retrospect.com/index.php?/topic/151193-error-in-the-log-what-does-it-mean/ and http://forums.retrospect.com/index.php?/topic/150803-what-does-verify-error-mean/ ) In short, I get MD5 errors in media sets that remain even after the media set is copied, and seem to be repeated if the same file is backed up again. It is as if there is something about the file that the MD5 algorithm can't handle correctly. A verify of the media set will reliably complain of the MD5 error. A restore of file with the MD5 error will succeed without error, and if I copy the media set, the copy operation will see no MD5 error, but the resultant copied media set will show the MD5 error on the same file when I do a verify on the copied media set. I would normally blame this on hardware - bad disk, bad cables, flaky hardware, but I have seen this on several disks and several computers, and the problem does not appear to be hardware. The pattern appears to be a software problem in MD5 generation (or verification). The error usually happens on files with very long "garbage" file names. (generated by some sort of hash) I can't pin this down, nor reliably reproduce it. If I can, I'll do so.
  2. I get the following error. Any ideas of what it might be? Happens while every time Retro verifies the backup. Seems it's now up to four instances where this file is not being matched. !Generated MD5 digest for file "/Volumes/Mac Mini HD/Library/Application Support/Retrospect/Catalogs/USB_Pool_Maxtor300.rbc" does not match stored MD5 digest. !Generated MD5 digest for file "/Volumes/Mac Mini HD/Library/Application Support/Retrospect/Catalogs/USB_Pool_Maxtor300.rbc" does not match stored MD5 digest. !Generated MD5 digest for file "/Volumes/Mac Mini HD/Library/Application Support/Retrospect/Catalogs/USB_Pool_Maxtor300.rbc" does not match stored MD5 digest.
×