ignprint Posted March 17, 2010 Report Share Posted March 17, 2010 Hello. We are having problems with our Retrospect. We are attempting to run a backup script and during the initial scan, it crashes. So far, it has only once generated an error message - all the other times, it has simply crashed. Error Message - Retrospect From Retrospect. Automatic execution unexpectedly terminated (possibly due to a power failure or system crash). We've run backups on other parts of that particular server and were successfully able to back them up. It seems to be chocking on only one folder. We've tried rebuilding the set / running a separate set / creating a completely new set - nothing works. We've also upgraded to 6.1.230; as well as enabled and disabled ACL; we've also restarted the computer that it is sitting on. There was a kernel panic last Wednesday which involved that server (including that folder). However, everything was retrieved and as I mentioned before, backups have been successfully run on that server. It continues to crash, only when scanning that 1 folder. Details - Retrospect 6.1.230 (6.1.126) MAC OS X SERVER - Version 10.5.8 Processer - 2 x2 GHZ Dual Core Intel Xeon Memory - 16GB 667 MHZ DDR2 FB DIMM Any help would be greatly appreciated! Quote Link to comment Share on other sites More sharing options...
rhwalker Posted March 17, 2010 Report Share Posted March 17, 2010 Ok. Running 6.1.230 on Intel architecture you aren't going to be able to back up ACLs (it's an Apple bug with Rosetta emulation, and it will never be fixed), so check the box to not back up ACLs (Special > Preferences > OS X, Don't back up ACLs). You don't indicate whether you have run Disk Utility standalone (from your install DVD) on that volume. Do so. It could be filesystem corruption that is causing the issue. You don't indicate what version of Retrospect Driver Update ("RDU") you are running, or if you even have an RDU installed. Some bugs are fixed through the RDU. Try updating RDU. There may be some odd file in that folder that is causing the crash. You are just going to have to experiment to find that file if the filesystem looks good. Make your testing go fast by defining a subvolume with that folder, move files in and out until you find the problem file. Last, there may be some odd corruption of the retrospect preferences that is causing the crash. Here's how to test: (1) quit Retrospect (2) move the preferences file somewhere that Retrospect can't find it (such as your Desktop) on startup. That way, if this isn't the problem, you can move it back. It's at: /Library/Preferences/Retrospect/Retro.Config (6.0) (3) you will have to enter license code, etc., and won't have any scripts, etc. No matter, the purpose is to test that folder (as a subvolume). (4) If it still crashes, that's not the problem, quit Retrospect, move config file back. If it doesn't crash, that's the problem, restore the config file from a backup (you do have a backup, don't you) from when it was OK. Report results, we'll go from there. Russ Quote Link to comment Share on other sites More sharing options...
ignprint Posted March 17, 2010 Author Report Share Posted March 17, 2010 Thank you very much for taking the time to respond! We tried the 'Preferences solution' and that seems to have worked as it has begun the backup process. Thank you again! http://forums.dantz.com/skins/GL2007/icons/grin.gif 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.