Search the Community
Showing results for tags 'config'.
The search index is currently processing. Current results may not be complete.
I work for a school running Retrospect 8 on an Apple 10.6.8 server (set up by a prior IT person who is no longer here). This server backs up the other servers and the backups are stored on an attached Drobo. The backups had not been working for a while and upon investigation the internal HD of the server was filling up each night when the backups occurred. I researched and moved the Catalog folder to the Drobo, assuming that was getting large. That worked for a few days but now we're getting the disk full warnings at night again, though when I check the next morning there's plenty of free space so there must be temporary files clogging things up. My Google-Fu is escaping me. We have about 120 GBs free on the internal drive, but every night when the backups attempt to run that internal drive fills up and then empties again. I'd like to move any files that expand greatly in size during backup to the Drobo (which has several TB's free and is set up in a mirrored RAID). My current suspicions lie with Config80.dat, Config80.bak and RtrExec.dir which all live in their default location of /Library/Application Support/Retrospect. Which of those do you think is causing this and can I move them to the Drobo? Thanks so much for your help!!
Reporting the news. All retro 10.5.1 (145). Console running on mini, 10.6.8. Engine on 10.8.5 on newer mini. 16 GB mem. I had the console up for a while. I clicked on "refresh" for one of my clients, and it seemed to take a while. I put the console in the background and forgot about it. A good hour later, I brought the console to the front, and it was *still* spinning, waiting for access to the client. I clicked onthe little "x" to tell it to quit, and then clicked on the client, and the "refresh" again. I don't remember exactly what I did at that point, but the console stayed up, and the engine appeared to crash. The display collapsed to the icon for the engine/server, and it said "connecting". I tried to restart the console, and it did not help. It also refused to connect the the enfine. I moved over to the server, and being aware of the problems with retro crashing and messing up its prefs, I decided I would see if there was a crash log, and maybe do something about the prefs *before* i restarted. On the server, the engine was still running, but refusing all console connections. As I recall, after I restarted the engine, the console still would not connect. Once the engine was up, restarting the console worked. I went to the control panel on the server, and noticed that "instant scan" was enabled (I KNOW I disabled it and left it disabled) I unlocked it and pressed the stop button. The engine stopped. I then went to /Library/Applications Supprt/Retrospect, and noticed that config80.dat was 14.7 MB, and config80.bak was 1.7 MB. This looked sub-optimal. I don't want one of those huge config80.dat files. I moved config80.dat to config80.dat.bad, and then I copied config80.bak -> config80.dat. I also copied config80.bak to config80.bak.bak (just in case - not certain retro is actually backing up its pref files) I restarted the engine, and all is well EXCEPT that the "activities" prior to today are all gone. I can see the activity in the log, and I can see the passt backups, but the stuff in the "activity window is gone. Small price to pay. Why did it crash? Why did it crash without actually crashing? Did the "non-crash" cause the "large" config file? Why did the crash "re-enable" the insta-scan? What state in the console would prevent it from connecting to the engine?