3

Hello guys,

I have a runbook to launch but it takes more than 3 hours to run (process of partitions) and so, it stops before being complete. I wanted to know if there is a way to exceed the 3 hours limitation. I've heared about hybrid runbooks but I'm not sure how it could solve my problem. Do you know if there is other solutions ?

Thanks a lot.

Mathieu Ricour
  • 368
  • 1
  • 4
  • 25
  • Which type of runbook are you using? Powershell, Powershell Workflow, etc.? I am running into this same issue using a Powershell Workflow runbook and there doesn't seem to be a clear alternative. How did you eventually solve this issue? – cbrawl Sep 17 '18 at 19:20
  • The PowerShell runbook, and at the moment it is still unsolved... I had to split my process in multiple runbooks unfortunately – Mathieu Ricour Sep 18 '18 at 07:21

2 Answers2

1

If you want to stick to Azure Automation, you can use Checkpoints:

Azure Automation has a feature called “fairshare”, where any runbook that runs for 3 hours is unloaded to allow other runbooks to run. Eventually, the unloaded runbook will be reloaded, and when it is it will resume execution from the last checkpoint taken in the runbook. Thus, in order to guarantee that the runbook will eventually complete, you must add checkpoints at intervals that run for less than 3 hours.

Source.

Here is an example:

Martin Brandl
  • 56,134
  • 13
  • 133
  • 172
0

no. there are none, that is if you want Azure Automation. Your options are:

  1. Web Jobs
  2. Azure Functions (NOT consumption plan)
  3. Hybrid workers
  4. services\scripts\schedules on your own vms
  5. Azure Batch
  6. Possibly Azure Data Factory, depending on what you are doing

probably something else.

4c74356b41
  • 69,186
  • 6
  • 100
  • 141