Contents x
    Retrospect Error -643 or -645 During Scan
    • 31 May 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Retrospect Error -643 or -645 During Scan

    • Updated on 31 May 2024
    • 1 Minute to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    If the Retrospect process ends unexpectedly, it could result in problems saving some of temporary data files that are used when negotiating security with your servers. This could result in the following errors being reported during the scanning phase of a backup:

    • Trouble Scanning, Error -643 (not a chunk file or badly damaged

    • Trouble Scanning, Error -645 (chunk file damaged during save)

    To resolve these errors, the damaged files must be deleted so Retrospect can recreate them.

    • Windows: Close Retrospect, navigate to C:\ProgramData\Retrospect\, and remove the contents RtrSec.dir directory for the volume you are trying to back up.

    • Mac: Go to to System Settings > Retrospect and stop the Retrospect engine. Navigate to /Library/Application Support/Retrospect and remove the contents RtrSec.dir directory for the volume you are trying to back up. Relaunch the Retrospect engine.

    The next time you launch Retrospect and run a backup, new security files will be generated to replace the old, and your backups should continue as normal.

    Last Update: May 2024

    Was this article helpful?
    What's Next