scotty321 Posted April 3, 2009 Report Share Posted April 3, 2009 I don't know what is going on with this Retrospect 8, but every day, it decides to just completely DELETE schedules for scripts that we've already scheduled! We have a backup script called "Nightly Backup" with 2 schedules: 1. One schedule backs up to Media Set A every Mon/Weds/Fri/Sun at 10pm 2. The other schedule backs up to Media Set B every Tues/Thurs/Sat at 10pm Yet every 24-48 hours, Retrospect decides to just COMPLETELY DELETE one of the two schedules from the script. You go back into the script, and one of the two schedules is just COMPLETELY GONE altogether. We have to re-create that particular schedule from scratch. Help, please? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 3, 2009 Report Share Posted April 3, 2009 Can you tell if Retrospect is crashing? You can check the OS X Console logs or the assert_log.utx file for updates. Failure to keep changes to the script is a known bug that we will have fixed soon in a pending bug fix update. Quote Link to comment Share on other sites More sharing options...
scotty321 Posted April 3, 2009 Author Report Share Posted April 3, 2009 I've launched the Mac OS X Console, but I don't know where to check to see if Retrospect is crashing. Where would I look? Also, I did a Spotlight search on the Retrospect server machine for "assert_log" and it couldn't find anything. Thanks, Scott Quote Link to comment Share on other sites More sharing options...
Mayoff Posted April 3, 2009 Report Share Posted April 3, 2009 The assert log is normally in Application support/Retrospect The console would have some type off note that Retrospect terminated or closed. Quote Link to comment Share on other sites More sharing options...
scotty321 Posted April 3, 2009 Author Report Share Posted April 3, 2009 Thanks, Robin. I checked /Library/Application Support/Retrospect, and there were no files that have the word "assert" in there. (I just have: a folder called "Catalogs" that is filled with Catalogs, a Config80.bak file, a Config80.dat file, operations_log.utx, retro.ini, RetrospectEngine.bundle, and an empty folder called RtrExec.dir). If I go into the Console, and choose CrashReporter on the left, it shows that Retrospect DID crash twice on 3/31/09. Quote Link to comment Share on other sites More sharing options...
Maser Posted April 3, 2009 Report Share Posted April 3, 2009 I've found that if Retrospect crashes, it seems to load from the .bak file -- at least that's my perspective on this. However, if you crash *twice* before the .bak file is updated, then you roll back even further (or start with a clean set of preferences.) Nothing I can reproduce, but I've been rebooting the system every time I make a major change to anything -- just to force an update to the .bak file. Quote Link to comment Share on other sites More sharing options...
mauricev Posted April 3, 2009 Report Share Posted April 3, 2009 Failure to keep changes to the script is a known bug that we will have fixed soon in a pending bug fix update. This is the same bug being described here. 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.