Nitro187 Posted June 12, 2003 Report Share Posted June 12, 2003 I am testing retrospect on our servers, to see if it can meet our needs, and so far, it doesn't. I have Windows 2000 server, and it seems to backup fine in the background, but when it is done backing up.... retrospect does not let is open it up again, saying that it is currently running. When I check the task manager, Retrospect.exe is running, yet, using absolutely no CPU time. Why does it stay running, when I specifically told it in the preferences to "quit" when done backing up? I've even tried telling it to log off, or even restart the server... it does nothing. Help? The way I am running retrospect, is logging off, so that no one is logged into the server, and it starts the service, but doesn't exit, as far as I know, because it stays listed in the task manager. Please let me know what I can do, to get retrospect to CLOSE or LOG OFF when done. Thanks. Link to comment Share on other sites More sharing options...
AmyJ Posted June 13, 2003 Report Share Posted June 13, 2003 Are you using Terminal Services? Link to comment Share on other sites More sharing options...
Nitro187 Posted June 15, 2003 Author Report Share Posted June 15, 2003 I sure am... is that a problem? I log out everytime I terminal service into the server, and I tell Retrospect to do the same. Link to comment Share on other sites More sharing options...
AmyJ Posted June 19, 2003 Report Share Posted June 19, 2003 Are you completely quitting the TS session, or just logging off? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.