Jump to content

Search the Community

Showing results for tags 'scheduled'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 3 results

  1. This is mostly a nit, but would be a plus for those of us who have scripts that have to run in a particular sequence. (like zero the destination, then copy to that destination. Get it in the wrong order, and you get trouble.) What I do is schedule my scripts at times that are different, but not far enough apart, relying on retro to execute them in the order they are requested. For instance, I have scripts: scriptA - 12:01 AM scriptB - 12:02 AM scriptC - 12:03 AM scriptD - 12:04 AM scriptE - 12:05 AM All these scripts specify a particular thread. I rely on this technique to ensure that A, B, C, D, and E are executed in the right order. This works. Each of these scripts can take a while, so at 3 AM, the console shows me little yellow trangles showing the scripts that have not yet run. The only problem is that the little yellow triangles are in the wrong order. It looks like they are in strict reverse order, but I'm not sure. There appears to be the occasional exception. It would be nice if the pending operations would appear in the activities window in the order that they are going to be launched. This is not a major functional issue, but would remove a bit of anxiety from the user ,who might think that the order presented will be the order of execution. BTW - this is retro 11.5.3 on engine and console. Mac os x 10.6 for console and mac os X 10.8 for engine.
  2. Retro 10.5.0(145) on Mac OS X 10.8.5, Mac mini (summer 2013), 16 GB mem My engine is stuck. I have a pro-active script that says "not active", which runs every 1 day. Active every day between 2:30 AM and 9 AM. It has not actually done anything since Nov 1st, though. I tried duplicating the script, and setting the "active" time to 1:pm to 5 PM on Monday (today) of the duplicate - called junk-script.. junk-script says it is (Not yet determined), and has been that way for a couple of hours. No other activities are active. Looking through the log, it looks like *none* of the proactive scripts are running - since Nov 1st. Is there something I can do to crank up the debugging to tell me what the engine is stuck on? I've had this happen before, and I may not notice it for several days, which is Bad Juju. Thanks,
  3. (Retro, Mac mini on Mac OS X 10.8.5. Client console on Mac OS X 10.6.8) The preference for selecting the number of "scheduled" activities does not work as expected. I have quite a few activities queued up for the turn of the year - midnight on 1 Jan 2014. I was puzzled why the scripts I had scheduled for a few hours after midnight were not showing up in the "activities" report. I had to bump it up to 50 to see the 20 scripts that are queued. It appears to be counting just the scripts that are doing a "recycle" backup, but is counting them wrong. I include 3 screen shots below, with the setting at 10, 20, and 50. None of the settings shows the number of scheduled activities that I expect (10, 20, or 50) It is generally more, but omits some, like the later "recycle" operations that are in the "middle" of the list. Is the preference 10/20/50 per day? The snaps: With the pref set to 10, I get 29 scheduled activities, but only 9 of the "recycle" ops. Set at 20, I get 35+ (a few hidden at the bottom, but only 19 recycle ops. Set at 50, I get a lot more, and can't show them on the screen all at once. These two snaps cover the 69 scheduled activities, and I finally get all my recycle ops. If this is how it is supposed to work, it needs a better description. ;->
  • Create New...