bovilexic Posted May 8, 2011 Report Share Posted May 8, 2011 Hi - Just checked the log for my last nightly backup, and saw the following: + Normal backup using Nightly Backup at 5/8/11 To Media Set Nightly Backup Media Set... - 5/8/11 2:00:00 AM Sunday May 8, 2011: Copying Macintosh HD > *File "/Volumes/Macintosh HD/Library/Application Support/Retrospect/Config80.dat": can't read, error -39 ( unknown) 5/8/11 2:33:15 AM Sunday May 8, 2011: Snapshot stored, 354.3 MB 5/8/11 2:34:11 AM Sunday May 8, 2011: Comparing Macintosh HD *File "/Volumes/Macintosh HD/private/var/log/system.log": different data size (set: 784, vol: 1247) *File "/Volumes/Macintosh HD/Users/pjs/Library/Preferences/ByHost/com.apple.iCal.helper.0016cbac5fdb.plist": didn't compare 5/8/11 2:36:01 AM Sunday May 8, 2011: 1 execution errors Completed: 626 files, 870.7 MB Performance: 157.8 MB/minute (94.3 copy, 483.7 compare) Duration: 00:36:00 (00:24:57 idle/loading/preparing) It seems that the Config80.dat file couldn't be read??? But, the backup seems to have proceeded normally - that it, it succeeded. I've seen forum posting from folks who have had problems with this file, and have had to restore it or have it recreated due to some corruption issue (settings lost, user had to input license number, etc.) But in my case, no other symptoms/problems were evident, and the backup did seem to work correctly. Should I be concerned...is there anything I need to do here??? Thanks! Quote Link to comment Share on other sites More sharing options...
bovilexic Posted May 8, 2011 Author Report Share Posted May 8, 2011 Hi - Just checked the log for my last nightly backup, and saw the following: + Normal backup using Nightly Backup at 5/8/11 To Media Set Nightly Backup Media Set... - 5/8/11 2:00:00 AM Sunday May 8, 2011: Copying Macintosh HD > *File "/Volumes/Macintosh HD/Library/Application Support/Retrospect/Config80.dat": can't read, error -39 ( unknown) 5/8/11 2:33:15 AM Sunday May 8, 2011: Snapshot stored, 354.3 MB 5/8/11 2:34:11 AM Sunday May 8, 2011: Comparing Macintosh HD *File "/Volumes/Macintosh HD/private/var/log/system.log": different data size (set: 784, vol: 1247) *File "/Volumes/Macintosh HD/Users/pjs/Library/Preferences/ByHost/com.apple.iCal.helper.0016cbac5fdb.plist": didn't compare 5/8/11 2:36:01 AM Sunday May 8, 2011: 1 execution errors Completed: 626 files, 870.7 MB Performance: 157.8 MB/minute (94.3 copy, 483.7 compare) Duration: 00:36:00 (00:24:57 idle/loading/preparing) It seems that the Config80.dat file couldn't be read??? But, the backup seems to have proceeded normally - that it, it succeeded. I've seen forum posting from folks who have had problems with this file, and have had to restore it or have it recreated due to some corruption issue (settings lost, user had to input license number, etc.) But in my case, no other symptoms/problems were evident, and the backup did seem to work correctly. Should I be concerned...is there anything I need to do here??? Thanks! One other thing - I've seen folks suggest that the Config80.dat file be backed up separately in its own Media Set (or via other means). That seems sensible, but does that imply that I exclude Config80.dat from my usual nightly system backup? Thanks! Quote Link to comment Share on other sites More sharing options...
f30e6e60-a263-4d69-8f60-c92703669308 Posted May 8, 2011 Report Share Posted May 8, 2011 It seems that the Config80.dat file couldn't be read??? Correct; if the config file is open and active during the backup process, Retrospect won't be able to copy it (and if it were to copy it, it would likely be corrupt upon restore). Don't worry about trying to construct a rule to just exclude this one file (although you could); easier to just ignore the message and construct some other way to keep copies. I have no problem using a Copy script of my /Library/Application Support/Retrospect/ folder, and I also have a disaster recovery archive created by shutting down the Engine and copying over the config file, along with the Retrospect installer disk image, client installer and a text doc of my license code. Worst case where I have to start up a completely new or borrowed system, I can at least get the software running again without panicking (yet). Quote Link to comment Share on other sites More sharing options...
bovilexic Posted May 8, 2011 Author Report Share Posted May 8, 2011 Correct; if the config file is open and active during the backup process, Retrospect won't be able to copy it (and if it were to copy it, it would likely be corrupt upon restore). Don't worry about trying to construct a rule to just exclude this one file (although you could); easier to just ignore the message and construct some other way to keep copies. I have no problem using a Copy script of my /Library/Application Support/Retrospect/ folder, and I also have a disaster recovery archive created by shutting down the Engine and copying over the config file, along with the Retrospect installer disk image, client installer and a text doc of my license code. Worst case where I have to start up a completely new or borrowed system, I can at least get the software running again without panicking (yet). That sounds reasonable...just don't recall having seen that error before, in many years of Retrospect usage. Thanks! Also, the "disaster recovery archive" idea sounds like a very good one. Think I'll do this, as well. Certainly would save a lot of hassle :-) - Philip Quote Link to comment Share on other sites More sharing options...
Guest Steve Maser Posted May 9, 2011 Report Share Posted May 9, 2011 If it came down to having to restore something -- you can always restore the "config80.bak" file -- and then just rename it to "config80.dat". In my experience, the "bak" file is at most a few hours older than the "dat" file. 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.