rcolley Posted August 8, 2002 Report Share Posted August 8, 2002 Does anyone have any ideas why we might be getting unexpected quits from retrospect 5.0.205 server whilst running in backup server mode? when this happens retrospect does not relaunch itself, trying to relaunch it manually doesn't work, the OS has to go through a logout first. Our backup script is set to run 24 hours, does this effect it's relaunch? Rob Link to comment Share on other sites More sharing options...
lv2ski Posted August 8, 2002 Report Share Posted August 8, 2002 I wonder if your config files are damanged. Try pulling them out and relaunching Retrospect. Set up the script again and see what happens. Link to comment Share on other sites More sharing options...
Maser Posted August 8, 2002 Report Share Posted August 8, 2002 We see this too. Running backup server 24x7, we'll come in and check the servers and Retro has just quit. No error message -- nothing. I wonder if this is related to how much RAM the app sucks up when you run it in Backup Server mode? Maybe it finally overwhelms something and barfs? Link to comment Share on other sites More sharing options...
rsmith Posted August 12, 2002 Report Share Posted August 12, 2002 I've seen this happen myself. Retrospect 5.205 has a memory leak. As time goes on, Restrospect is continuing to gobble up memory, up to the point where it eats itself alive, and then causes general system instability. Check up on your backup server as the day goes on, the application(in this case, Restro Backup is carbon, so it's LaunchCFMAPP) will increase slowly from 10MB to over 100. Until Dantz fixes this, it's been in my experience that a busy server will crash every 1 to 2 days. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.