Retrospect Error -643 or -645 During Scan
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.
Windows: Close Retrospect, navigate to
C:\ProgramData\Retrospect\, and remove the RtrSec.dir directory.
Mac: Head to System Preferences > Retrospect and stop the Retrospect engine. Navigate to
/Library/Application Support/Retrospectand remove the
RtrSec.dirdirectory. 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: 10 Gen 2017