-
- Influencer
- Posts: 22
- Liked: 2 times
- Joined: Jun 11, 2015 1:57 pm
- Full Name: Scott
- Contact:
Run replication jobs in a loop during certain times of the day
Hey all,
I have a bunch of replication jobs set up to run one after another. Example: I have the schedule set to run the job automatically after the previous job.
Job 1 runs after job 5.
Job 2 runs after job 1.
Job 3 runs after job 2.
Job 4 runs after job 3.
Job 5 runs after job 4.
This currently runs all the time. If possible I'd like to only have these jobs run during the day and not over night.
Is there a way I can keep the jobs running in this loop and specify what time of day to run?
I know I can throttle down the network at certain times but I want the jobs to completely stop running.
TIA
I have a bunch of replication jobs set up to run one after another. Example: I have the schedule set to run the job automatically after the previous job.
Job 1 runs after job 5.
Job 2 runs after job 1.
Job 3 runs after job 2.
Job 4 runs after job 3.
Job 5 runs after job 4.
This currently runs all the time. If possible I'd like to only have these jobs run during the day and not over night.
Is there a way I can keep the jobs running in this loop and specify what time of day to run?
I know I can throttle down the network at certain times but I want the jobs to completely stop running.
TIA
-
- Product Manager
- Posts: 2581
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Run replication jobs in a loop during certain times of the day
Hi Scott,
Each Replication job has Window option under Schedule.
Restrict night hours and that should do the trick!
/Thanks!
Each Replication job has Window option under Schedule.
Restrict night hours and that should do the trick!
/Thanks!
-
- Influencer
- Posts: 22
- Liked: 2 times
- Joined: Jun 11, 2015 1:57 pm
- Full Name: Scott
- Contact:
Re: Run replication jobs in a loop during certain times of the day
I will try that.
Will doing this trigger failed job alerts when it reaches the termination time?
Will doing this trigger failed job alerts when it reaches the termination time?
-
- Product Manager
- Posts: 2581
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Run replication jobs in a loop during certain times of the day
I don't remember exact statuses, but I am quite sure termination of already running job shall trigger a warning, however next runs within locked window should be suppressed without changing status.
-
- Influencer
- Posts: 22
- Liked: 2 times
- Joined: Jun 11, 2015 1:57 pm
- Full Name: Scott
- Contact:
Re: Run replication jobs in a loop during certain times of the day
This did not work. Even with the jobs set to not run after hours they continue to run all day / night.
-
- Product Manager
- Posts: 2581
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Run replication jobs in a loop during certain times of the day
Strange, seems like a bug to me.
Will investigate.
Will investigate.
-
- Product Manager
- Posts: 2581
- Liked: 708 times
- Joined: Jun 14, 2013 9:30 am
- Full Name: Egor Yakovlev
- Location: Prague, Czech Republic
- Contact:
Re: Run replication jobs in a loop during certain times of the day
Discovery shows that backup window is bypassed if you run job manually, and in such rare case as yours with infinite loop "Job2 after Job1 after Job 3 after Job 2" backup window will never get a chance to work. I do agree that backup windows shall be respected for all non-user-interactive job runs, thus we will see if that behavior can be altered in future versions.
As of now, switch first job in a sequence to run based on time(not chained), and adjust "Periodically every X hours\minutes: " to be as close to your existing loop cycle period as it could be. Backup window will be respected here as well as chained jobs will not start outside allowed window.
/Thanks!
As of now, switch first job in a sequence to run based on time(not chained), and adjust "Periodically every X hours\minutes: " to be as close to your existing loop cycle period as it could be. Backup window will be respected here as well as chained jobs will not start outside allowed window.
/Thanks!
Who is online
Users browsing this forum: Bing [Bot] and 72 guests