Posted Wed, 15 May 2019 15:11:25 GMT by Francois Labrecque

I have 2 seperate jobs that have complex dependencies that I do not know how to handle. Your help is more than welcomed. These are distinct issues.

Case #1 : Don't execute during database back up
I have a job suite that has 10 jobs and takes 10 hours to execute (for the sake of argument, let's say each jobs take around 1 hour to complete).

This suite is triggered by a filewatcher monitor, which can happen at any time.

Between 5AM and 7AM, we have a database back up. The job requires to read and write data to that database. If the jobs execute during these times, it will fail. Failing mid-load is very complicated to resume.

How can I make sure that none of the job members execute during the back up?

Case #2 : A monthly weekly load
I have a weekly job suite. I would like to setup a job that runs monthly, but depends on the first execution of a job member in the job suite.

I can't specify in the weekly job suite to run a member only once.

I can't have an individual job dependent on a job suite / job member.

 

Posted Wed, 15 May 2019 17:37:12 GMT by dennis grimm

Case #1.  What happens if a member is already running when the backup kicks off?  is that ok are you cannot have that either, in which case is the non run window more like 4am-7am, or even 3am-7am to be safe?  My thinking here is you can use a schedule queue here, just holding the queue the member jobs run in during the backup.  You just need to figure out the time to hold the queue.

 

Case #2.  You should be able to use a date list here, and place that date list into the suites special instances, then use the skip special instance on the member job.  use the built in help to get an understanding of all 3 of those settings, then we can answer any more questions from there.

Posted Wed, 15 May 2019 19:43:54 GMT by Francois Labrecque

On case #1, the back up isn't scheduled through automate. To be safe, we would put a few hours buffer to make sure that a job doesn't execute during the back up.

The good news is that we only need to execute 1 job at a time on this server. I made a proof of concept to test the fonctionality with a job queue and it works. Hourra! :)

You must be signed in to post in this forum.