Jump to content

Search the Community

Showing results for tags 'schedule'.

  • 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 12 results

  1. The default time window for Proactive backup scripts is 00:00 to 00:00 i.e. midnight to midnight the next day and Retrospect server specifically treats this as the beginning of one day to the beginning of the next day. Unfortunately the same logic does not seem to apply to custom user defined time windows. For example if one wanted to do midday to midday i.e. 12:00 to 12:00 then Retrospect rejects this and will not accept it at all and therefore will not treat it as covering a 24 hour period. This is not only I feel a bug it is rather annoying since despite what Retrospect themselves may think I am not going to be coming in to the office to change over the backup media at midnight each day. As a result if typically one did change over the media at midday with the standard 00:00 to 00:00 window then actually you will only get backups happening for half the day at most.
  2. There are occasions when you need to force tasks to run sequentially, and as quickly as possible, ideally immediately one after the other. {EG: Each morning you might want to Verify the previous nights' backups, then initiate a Snapshot Transfer Task to Tape for offsite copy.} The usual compromise is to take a guess at how long each Task will need and then schedule them in time sequence with a gap in between to allow for variation in run time. Whilst this works (provided you at least have an estimate of the run time for each job) it is not very efficient or fast, and very difficult if you have no idea how long a task may take. Try this method to force tasks to run sequentially with each one starting immediately the previous one has finished. The trick is in forcing them all to use the same execution unit. Schedule each job to start a short time, (say 1 minute) after the previous one. This is just to get them in the right order. It doesn't matter how long they may actually take to run. At the bottom left of the Script window for each task is the Execution Unit selector, which defaults to ANY. Set it to the highest numbered Execution unit, (so it won't clash with any other task which will pick the lowest numbered available unit by default) for each of your Sequential Tasks. At the appointed time the first of your sequential tasks will start with the specific Execution unit. 1 minutes later the next one will try to start, but since the execution unit is in use, it cannot, and will be added to the Waiting Queue. The rest of your sequential tasks will follow at 1 minute intervals. You should now see them in the Waiting Tab of the Activity Monitor, all waiting, in order, for the Execution unit to become free. As soon as the first task completes, releasing the Execution unit, the next one will start. Your tasks will now execute, sequentially, as quickly as possible. See the User Guide, Chapter 7, Controlling Operations > Multiple Concurrent Executions > Assigning Execution Units.
  3. I'm looking at Image 1 and I'm confused why the Script 7 Day seems to think it needs to do schedules in the past ... I look at the Script (Images 2 and 3) and it looks right to me.
  4. I have a backup script that copies several volumes and folders to a dedicated external drive. I have two of these drives that I alternate between. I only need to complete this backup once a week to whichever drive is present. Previously, I used a two regular scripts for these backups. I wanted to combine them into a single script with both destination volumes set up in Media Sets. As a regular script, however, I found that Retrospect would get stuck looking for the missing media set. So, I changed to a proactive script, thinking that the script would run only on the available destination, regardless of which volume was present. Rather than use the default schedule of continuous operation, I've set my proactive script to run weekly on Sundays at midnight. For the past two Sundays, though, the script has not run and no backup has been attempted at all to the available drive. Was I mistaken? Is there a better setup here? Is the only approach to separate the scripts again? Is Proactive appropriate since one of the two drives is always absent? Or, should I return to standard scripts, separate media sets, and hope that each week one of the two will succeed because its media set is available and the other will fail because its set is not—but it won't get stuck.
  5. Retrospect 11.5.3 keeps failing to run scheduled scripts. It'll run for a few days, then just fails without warning. Of course, I don't notice the lack of emails for a few days. This is very bad. I thought I asked for help about this before but got nothing. Tonight I launched Retrospect to check on something and noticed that nothing was running. It then started running today's scheduled scripts, except they never got around to actually doing anything - just sat there saying "Preparing to execute" for half an hour, which is much longer than they normally do that step. So I stopped them, but they never stopped either. Not even logging out and back in would fix that. I had to reboot, and even then I had to force it to shut down because something (and I'd bet ten bucks that something was Retrospect) was preventing it from shutting down. Fix this crap.
  6. Is it possible to create a schedule that will start on a specific date, backup each day for week, then not run again for another week? I have tried this, several times, and it just does not seem to work correctly. I have two sets of tapes, which get rotated weekly, on a friday. I then set my backup to begin Friday so any large data backups happen over the weekend, then smaller incremental backups will happen throughout the rest of the week. The problem i am having is that when i come in on Monday, the backup has happened, but the next backup date is at least a week away...when it should be tonight! The schedules are set to repeat "weekly, every 2 weeks on every day" - It looks as if Retrospect wants each week to start on Sunday, so if i choose to start Friday, it behaves as if i am starting at the end of the week and will only run backups until the end of the week... I should be able to set when the week starts..ie. If i start on Friday, then there should be 7 backups before the schedule pauses for a week, then the next set starts up in a weeks time. Is there any way i can set this scheduling up, because it is really annoying to have to rewrite my scripts on Monday morning every week! adam
  7. 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,
  8. I recently created a script (Retro 10.2) to verify my media sets periodically. It has a bunch of media sets to do. When I set up a schedule, I note that there is a popup listing all 8 media sets to be verified. When I set up a schedule, I can "attach" that schedule to one of the media sets. If I have multiple schedules, they can be "attached" to different sets. Which set seems to make no difference. Happily, any schedule, attached to any set verifies all 8 sets. What is the purpose and significance of the popup?
  9. I have a proactive that runs on the weekend, but wanted it to run *now* to test recent changes. I went to the "schedule" tab on the script, and added a second "schedule" by pushing the "+". I set it to be active on thursday (today), and planned to remove the second "schedule" when the backup ran. When I pressed "save", the "thursday" schedule **replaced** the weekend schedule, rather than being added to it. (two entries) I have yet to have two entries in the schedule that work. If there is a "+" button, it should work. If it doesn't work, it should be disabled.
  10. I just had one of my proactive scripts quit because it hit its "scheduled stop time". I wanted it to finish, so rather than create a new script, I thought I would add another schedule item to run it just for today, leaving the existing schedule and script intact. When I went to add another script entry for "10 AM to 3 PM/every day", I ended up with two schedule entries on the script, both saying "12AM-12AM/every day". Clearly the act of adding the additional script entry overwrote/corrupted the existing schedule entry. I have seen this before in other circumstances. In my experience, the scheduling machinery does not work well. A single entry generally works, but more than one is trouble. (Retro, Mac OS X 10.6.8)
  11. I would like to setup a daily backup in v9 that will only be active from 8 pm to 8am M-F and 24hours on SS. This was very straightforward in version 6, but how do I do this in v9? Thanks! Chris
  12. I'm not certain about this, but it appears that having more than one entry in a schedule for a "proactive backup" does not work. I stumbled on this today when I wanted one of my proactive backups to run *now* and the scipt was "inactive". I thought I could simply add another entry to the schedule, saying that on Sunday, all day, it could run. I was unable to get this to work, and I don't know why. It *appeared* that the second schedule entry was simply ignored, but I did not experiment enough with it to be sure. The reaction time of the engine was also a frustration. Sometimes the engine would start up the activity IMMEDIATELY when I changed it in the script. Other times, it would not respond for some time. Again, I did not experiment enough to figure out what was happening, but there is clearly something there that is unexpected, even if it is intended. Retro, Mac OS X 10.6
  • Create New...