Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About NoelC

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Got it working. Success was as simple as realizing that Retrospect.exe with a run document (xxxxxx.rrr, as saved during script setup) as a parameter will just do the backup specified by the run document then do what's configured when done (e.g., exit in my case). No scheduling at all needs to be done in Retrospect, Enable Management console is unchecked, Enable Retrospect Launcher service is unchecked, and Instant Scan needs is disabled. Voila, one scheduled job in the Windows Task Scheduler done at a particular time that invokes my nightly backup. There are no ongoing running processes from the intergalactic backup program that I just need to do one very simple backup at the same time each night. While it would have been nice for it to work like this right out of the box (e.g., easy integration with Windows Task Scheduler just by setting the right options in the Restrospect UI), I can live with rolling my own. Might be a case where developers, very close to the product and constantly focused on adding valuable features, have forgotten that it can/should be a basic low-impact backup solution too. The only other downside I've seen so far (and will work on next) is that Retrospect emits my system "Asterisk" (ding in my case) sound - presumably to announce that the backup has succeeded - which has awakened me at about 3:30am twice so far. Next step will be to configure it to not interact with the console at all if possible. I suspect that will just be a small change in the Task Scheduler to "Run whether user is logged on or not", which is what I want anyway because I don't want to have to leave it logged on to get backups done. Still on the trial period but I suspect I'll succeed and Retrospect will get my business. -Noel
  2. Thanks. It occurred to me I didn't provide enough information. My backup is set for once per night at 2am; my look ahead time is minimized to 1 hour, and I have disabled Instant Scan. Basically I want a very simple, once per night, single computer backup to permanently attached local storage. The system runs 24/7. I find these text lines from the post at the first link you posted most interesting, as they are pertinent to my question: > Retrospect is configured to run as the logged-in user (who has all permissions needed for backups), and the Task Scheduler is configured to run its task under that same user account. This enables Retrospect windows to appear normally on that user's desktop. > ) Invoking Retrospect.exe with a "Run Document" argument opens the main window, runs that script and any waiting scripts, and either stays in Retrospect or exits (depending on Startup Preferences). > Exit (or others) (Works only with a "Run Document" argument´╗┐.) The above describe my situation and imply it's possible I simply have not yet found the proper combination of options and command line arguments. I have not tried saving the one and only script I've created as a "Run Document". The only thing I'd rather not have to do is leave the system logged on, though in practice that is almost always the case. My remaining question is whether the setting for "Enable Retrospect Launcher Service" and "Automatically Launch Retrospect" should be left checked but the retrorun service set to "Manual" or "Disabled", or should they just be unchecked. I will proceed presuming the latter. Appreciate your help! -Noel
  3. Hello, New Retrospect user here... Looks like a good product; I like that I could quickly set it up to do exactly the nightly backup I needed, and that it's reporting 0 errors and 0 warnings for incremental backups of multiple terabytes of volumes that complete in good time. However, the need to keep service retrorun running bothers me. I have a philosophy of keeping installs of all software on my computers as lean as possible. By following this philosophy and enforcing a minimal running process count through the use of e.g., Autoruns I have been able to keep Windows installations efficient and performant and have often advanced performance. People often complain that Windows slows down over time. Not my Windows systems! Windows provides a perfectly good Task Scheduler. Can Retrospect be configured to use it, eliminating the need for the retrorun service component to be kept running? I have seen, for example that the command line given to Retrospect.exe contains the term "autostart", and an attempt to start Retrospect.exe from the Task Scheduler at the time of my nightly scheduled backup DID work after a fashion but did not yield the expected process exit after the backup was complete. Thanks for any wisdom you are willing to share on this. -Noel