Retrospect Error -643 or -645 During Scan
  • 13 Nov 2023
  • 1 Minute to read
  • Dark
    Light
  • PDF

Retrospect Error -643 or -645 During Scan

  • Dark
    Light
  • PDF

Article Summary

Resources

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:

Error -643 (not a chunk file or badly damaged

Error -645 (chunk file damaged during save)

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

: Close Retrospect, navigate to

: Head to System Preferences > Retrospect and stop the Retrospect engine. Navigate to

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: January 10, 2017


Was this article helpful?