blm14 Posted August 26, 2008 Report Share Posted August 26, 2008 I am seeing (twice now) "Sorry, can't save configuration, error -644 (chunk file damaged during access)" but retrospect isn't crashing and it doesnt appear that anything else is going wrong... Should I worry about this? I am using retrospect 7.6.111 on windows server 2003 SP2. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted August 26, 2008 Report Share Posted August 26, 2008 You probably have corrupt preferences. Rename the Retrospect folder in documents and settings\all users\application data and see what happens. Quote Link to comment Share on other sites More sharing options...
blm14 Posted August 26, 2008 Author Report Share Posted August 26, 2008 If I do that, though, wont I lose all my settings? I assume you mean to rename it and then move it back? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted August 26, 2008 Report Share Posted August 26, 2008 Yes, you are doing this as a test to see if it fixes the problem. Quote Link to comment Share on other sites More sharing options...
blm14 Posted August 27, 2008 Author Report Share Posted August 27, 2008 It doesn't happen consistently though, it's only happened twice so far over about a week, and if I remove my configuration then no backups will run so wont I have to wait several days to see if it happens again during which time no backups will be done? I'm not sure I can afford to wait and not be running any backups just to see if I get a positive result... Lets assume that the config files ARE corrupt, how do I fix that? Quote Link to comment Share on other sites More sharing options...
SHnee Posted August 28, 2008 Report Share Posted August 28, 2008 by renaming the Retrospect folder in documents and settings\all users\application data At the next start, Retrospect will then create a new Retrospect folder with new uncorrupted preferences in documents and settings\all users\application data Quote Link to comment Share on other sites More sharing options...
blm14 Posted August 28, 2008 Author Report Share Posted August 28, 2008 Correct me if I'm wrong here, but the new "application data" folder will have no scripts, no clients, no knowledge of my existing backup sets, etc. So by doing this we may prove that my configuration files were corrupt but we aren't fixing them, we're throwing them away and creating a huge amount of work to recreate them. Lets assume they are corrupt, is the only way to correct this problem to completely rebuild them from scratch? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted August 28, 2008 Report Share Posted August 28, 2008 You can always restore an older version of these files from your backup if the current copies appear corrupted. Quote Link to comment Share on other sites More sharing options...
shaggy314 Posted October 8, 2008 Report Share Posted October 8, 2008 In case a Mac OS user gets to this topic... It will tell you the corrupted pref "Retro.Config (6.0)" by name. It is in /Library/Preferences/Retrospect. Trashing it will require you to locate your serial number and don't panic about missing users/lists/etc. Restore the prefs from your last backup (as suggested above). You DO backup that folder right? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.