Jump to content

otolithe

Members
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

1 Neutral

About otolithe

  • Rank
    Newbie
  1. otolithe

    The State of Support

    That's reassuring... the next step now would be to fix the numerous bugs introduced by the new (and otherwise great) Mac version 9. Keep the good work!
  2. Once in a while, the RetroEngine process will start using a *lot* of CPU, up to 100% of the two cores, while the console shows absolutely no activity from the server. If I try to stop/restart the engine through the Retrospect Preference Pane, it does nothing and the engine keeps running. Looking at the OS X console, I can see the following error message: The only way to stop the RetroEngine process is to effectively force quit it through Terminal or the Activity Monitor. If I then relaunch the RetroEngine using the Preference Pane, it starts immediately using all the available CPU again. The only way to go back to normal is to reboot the machine. My configuration: MacBook 2,1 Core2Duo 2GHz, 3Gb RAM Mac OSX 10.7.3 Retrospect 9.00 (319) Backups of the two clients are done over gigabit ethernet using Proactive Backups This is a real problem since it requires me to manually reboot the backup server more or less every 2-3 days.
  3. Here is my problem: Retrospect Server 9.0x (latest version) running on Mac OS X Lion 10.7.2, the Client settings don't stick. I can check all the "allow clients to..." checkboxes in the Server preferences, but they don't do anything client-side and, if I quit and relaunch the console app, the boxes are unchecked... Meaning I can't allow my clients to abort a backup, trigger a restore or simply deactivate Retrospect Client! That plus the fact that, sometimes, even if the Server is not doing anything (no Activity currently running), the RetroEngine eats up 80%+ of the machine it's running on, and I can't turn the Server off from the OSX preference pane, I have to kill it using a terminal command while sudo rooting. Way to go Retrospect. Although it IS nice finally having a real 64bits, Lion ready version. Also, I'd really like to know two things: 1) why are the retrospect server preferences still stored in the old cryptic format and not using the standard XML .plist format? 2) why in Hell are OPERATION LOGS stored in the Config80.dat file, mine grew up to 20MB! and 3) now that Retrospect is version 9.x, maybe that file should be called Config90.dat? Note: this problem is mentioned in another thread about another server issue: http://forums.retrospect.com/index.php?/topic/147522-clients-v9-cant-back-up-now-only-work-as-schedule-proactive/
  4. Same problem here: Retrospect Server 9.0x (latest version) running on Mac OS X Lion 10.7.2, the Client settings don't stick. I can check all the "allow clients to..." checkboxes in the Server preferences, but they don't do anything client-side and, if I quit and relaunch the console app, the boxes are unchecked... Meaning I can't allow my clients to abort a backup, trigger a restore or simply deactivate Retrospect Client! That plus the fact that, sometimes, even if the Server is not doing anything (no Activity currently running), the RetroEngine eats up 80%+ of the machine it's running on, and I can't turn the Server off from the OSX preference pane, I have to kill it using a terminal command while sudo rooting. Way to go Retrospect. Although it IS nice finally having a real 64bits, Lion ready version. Also, I'd really like to know two things: 1) why are the retrospect server preferences still stored in the old cryptic format and not using the standard XML .plist format? 2) why in Hell are OPERATION LOGS stored in the Config80.dat file, mine grew up to 20MB! and 3) now that Retrospect is version 9.x, maybe that file should be called Config90.dat?
×