Guest abg Posted March 25, 2011 Report Share Posted March 25, 2011 Hi- For the last several weeks my backup script has failed to launch (triggered manually) due to the one and only source volume (macintosh HD) not being listed as the source. If I manually re-select it as the source, the backup runs OK from that point on. Any thoughts or ideas as to why the source isn't being kept in the script? Details: intel imac, OS 10.6.7, Retro V8.2.0 (399) backing up to external hard drive. Thanks in advance, Alan Quote Link to comment Share on other sites More sharing options...
twickland Posted March 25, 2011 Report Share Posted March 25, 2011 When oddities like this happen, it may mean that the configuration file Config80 has become corrupted. This unfortunately happens more frequently than any of us likes. Try this: Quit the Retrospect Console (if it's running); then go to System Preferences and stop the Retrospect Engine. Go to /Library/Application Support/Retrospect and drag the files Config80.dat and Config80.bak to the Desktop or other convenient place. Restart the Engine and launch the Console; you'll need to re-enter your license code and point Retrospect manually to your media set catalogs. Try recreating and running your script. If it now behaves as expected, it's almost certain that Config80 was corrupt. If you don't have a backup copy of that file from before the time things started to go south, you will then need to recreate all your scripts and lists from scratch. We once experienced a problem with Retrospect losing track of certain changes that even a brand-new, clean copy of Config80 didn't fix. We needed to uninstall and reinstall both the Engine and Console, after which we were actually able to reuse the copy of Config80 we thought had been corrupt. Quote Link to comment Share on other sites More sharing options...
Guest abg Posted March 25, 2011 Report Share Posted March 25, 2011 When oddities like this happen, it may mean that the configuration file Config80 has become corrupted. This unfortunately happens more frequently than any of us likes. Try this: Quit the Retrospect Console (if it's running); then go to System Preferences and stop the Retrospect Engine. Go to /Library/Application Support/Retrospect and drag the files Config80.dat and Config80.bak to the Desktop or other convenient place. Restart the Engine and launch the Console; you'll need to re-enter your license code and point Retrospect manually to your media set catalogs. Try recreating and running your script. If it now behaves as expected, it's almost certain that Config80 was corrupt. If you don't have a backup copy of that file from before the time things started to go south, you will then need to recreate all your scripts and lists from scratch. We once experienced a problem with Retrospect losing track of certain changes that even a brand-new, clean copy of Config80 didn't fix. We needed to uninstall and reinstall both the Engine and Console, after which we were actually able to reuse the copy of Config80 we thought had been corrupt. Thanks for the tip. I'll give it a shot this weekend. Alan 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.