KenBrey Posted June 28, 2010 Report Share Posted June 28, 2010 I am investigating why a couple of scheduled backups didn't run. Perhaps there was no user logged into any console or remote desktop session. Is it required that a user be logged in for Retrospect to execute scheduled tasks? OS: Windows Server 2008 R2. Quote Link to comment Share on other sites More sharing options...
Daniels Posted June 28, 2010 Report Share Posted June 28, 2010 I don't believe so. However you need to make sure to change the preference to tell Retrospect to always as run as a certain user. I have also found that stopping and re-starting the Retrospect Launcher service helps to make sure Rterospect runs correctly with no user longged in. Quote Link to comment Share on other sites More sharing options...
KenBrey Posted June 28, 2010 Author Report Share Posted June 28, 2010 I upgraded from 7.6 to 7.7, and confirmed that it now does log in automatically even when there is no user logged in to the server. Quote Link to comment Share on other sites More sharing options...
Ramon88 Posted June 29, 2010 Report Share Posted June 29, 2010 This has been the case for a long time. We run Retrospect under its own user account and have been doing so for quite some time. One drawback is if you, for example, have rebooted the backup server and have Retrospect running as a service, if it is executing a scheduled backup you can't access the Retrospect program/user interface itself. If you try to launch the program in such case, the OS will inform you the current execution will be stopped. Well at least that is the case with 7.6.123. We haven't tried it with 7.7.325 yet, but I expect it to be the same. We leave the program always 'open' so we can always access the interface. Quote Link to comment Share on other sites More sharing options...
Richy_Boy Posted June 30, 2010 Report Share Posted June 30, 2010 (edited) I leave the user logged in at all times, just have a lock timeout. Our servers are sat in a comms room with restricted access - geenrally checking is done via RDP, very rarely the server is touched. Rich Edited June 30, 2010 by Guest Quote Link to comment Share on other sites More sharing options...
Ramon88 Posted June 30, 2010 Report Share Posted June 30, 2010 Yup, same here! :teeth: Quote Link to comment Share on other sites More sharing options...
KenBrey Posted July 23, 2012 Author Report Share Posted July 23, 2012 Is it advisable to configure an auto-login on the server, either to the console or to a remote session, so that Retrospect can start its interactive session after a server reboot? I really don't like when it runs as a blind service. I really wish they would make the worker process allways run as a service, but make a user interface that can be run in any session, or remotely. Quote Link to comment Share on other sites More sharing options...
Ramon88 Posted July 27, 2012 Report Share Posted July 27, 2012 Well, since my last post in this thread two years ago nothing really has changed. But I expect this issue to be on 'the list' of the devs, or so I hope. Quote Link to comment Share on other sites More sharing options...
Chevelle Posted August 23, 2012 Report Share Posted August 23, 2012 I really hope they can address this issue also. I am currently having issue running this on Windows Server 2008 R2. Scheduled backups are not running and cannot stay logged on via RDP so leaving it "open" is not an option. Quote Link to comment Share on other sites More sharing options...
johnnymacgo Posted August 24, 2012 Report Share Posted August 24, 2012 I really hope they can address this issue also. I am currently having issue running this on Windows Server 2008 R2. Scheduled backups are not running and cannot stay logged on via RDP so leaving it "open" is not an option. You really don't need to stay logged on via RDP to keep Retrospect running. I connect via RDP to check the status of backups and then just disconnect (not logout) and everything keeps running. Quote Link to comment Share on other sites More sharing options...
Chevelle Posted August 25, 2012 Report Share Posted August 25, 2012 You really don't need to stay logged on via RDP to keep Retrospect running. I connect via RDP to check the status of backups and then just disconnect (not logout) and everything keeps running. I will give that a try. 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.