From time to time there are questions around using Orchestrator as a batch robot, for example run a set of file copy jobs every night. In general Orchestrator was not designed as a job scheduler, even it if would work in small scale. Challenges you can run into when trying to this are
- There is not a single view to show when you have schedule which runbooks. For example if you want to check all runbooks configured to run every night you have to browse through all your runbooks in Runbook Designer.
- There is not a single view to show all the calendars you have configured and how they are configured.
- There is not a single view to see if all runbooks was successfully last ran, for example if you have a number of runbooks running every night you want to have one view in the morning to verify that everything worked.
- There is no easy way to import a calendar from another tool
- By default a runbook server can run 50 jobs at the same time. You can reconfigure this (http://technet.microsoft.com/en-us/library/hh420378.aspx) but you should consider the resource requirements of the runbooks on a particular server. Lets say you start one runbook that checks for new files in a folder and then for each new file you invoke another runbook. What if there are 1500 new files in that folder? 1500 running runbooks would require a lot of runbook servers to run all that at the same time. If you donâ€™t have another runbook servers a queue would be built up, which could result in long delays and affect other runbooks.
If you still want to schedule a runbook, for example to run every 12 hours, you can use a Monitor Date/Time activity. A disadvantage is that the runbook will be running all the time, monitoring the schedule. As the runbook is running all the time, it will use one of the 50 (by default) slots on your runbook server.
If you want to run your runbook 01.00 on Sundays onlyÂ you can also use the Monitor Date/Time activity, but you need to combine it with a runbook level schedule. Create a new schedule, check only Sundays, and configure your runbook to use the new schedule. You configure the runbook to use the schedule by right-click on the runbook tab, selectÂ properties and then clickÂ schedule.
AfterÂ you have configured a runbook to run for example every Sunday at 1 am you start it. The runbookÂ will get the green “running” icon and in the database it will be marked as pending. Once it gets Sunday at 1 am the runbook will run. AfterÂ the schedule time window the runbook willÂ stay in running status, until next schedule time window,Â even if it is not allowed to execute between the scheduleÂ time windows. Â If the runbook tries to run other times a platform event will be generated.
Instead of using OrchestratorÂ to trigger runbooks based on aÂ schedule you can use Windows Schedule Tasks, see this blog post from the Orchestrator Engineering team. I have two related blog posts around this, one about execute runbook laterÂ and one about runbook servers in different time zones.
Note that this is provided â€œAS-ISâ€ with no warranties at all. This is not a production ready management pack or solution, just an idea and an example