By dweilmuenster - 4 July 2021 1:16 PM
Hi, looking for advice on how best to do this.
I have three different backup jobs (1 image, 2 file folders) that run by schedule on Sunday mornings. Currently I schedule them to run a couple of hours apart, and all works without problems.
But, I'm wondering if there isn't a better approach that would cause the jobs to run immediately in succession to each other. I thought about scheduling them all at the same time, with the condition that each should run immediately after missing a schedule start. But, not sure if that is good practice, or would even work as I'm expecting.
Basically, I'm just trying to schedule the jobs so that each runs immediately after the one following it. Again, all three jobs use different backup definitions.
Suggestions?
Thanks,
David
|
By jphughan - 4 July 2021 1:49 PM
Schedule them one minute apart from each other. That will give you control over the exact sequence, which scheduling them at the exact same time wouldn’t, and it will still cause Reflect to run them back to back since Reflect always queues new jobs if an existing job is currently running.
|
By dbminter - 4 July 2021 6:14 PM
Did v8 address the queuing issue with v7? On v7, I have 3 backups that run on Day 1 of each month, each spaced 5 minutes apart. The first backup always ran first because,well, it was first.  The order of the other 2, however, never seemed consistent. Sometimes #3 would run 2nd and sometimes they'd run in the intended order.
|
By jphughan - 4 July 2021 6:46 PM
Didn’t know that happened in V7, haven’t tested that in V8 since I don’t have a use case for having more than one backup queued at any given time.
|
By dbminter - 4 July 2021 6:57 PM
That was several years ago, but back when it I first noticed it on v7, I asked about it. Someone from Macrium said that could happen because there was no mechanism to execute a backup necessarily in the order they were queued. And, I admit, I haven't paid attention to it on the Day 1's that have happened since beta testing/production release of v8.
|
By dweilmuenster - 4 July 2021 10:17 PM
+xSchedule them one minute apart from each other. That will give you control over the exact sequence, which scheduling them at the exact same time wouldn’t, and it will still cause Reflect to run them back to back since Reflect always queues new jobs if an existing job is currently running.
Thanks! I'll try that and see how it goes.
Regards,
David
|
By DanDanz - 5 July 2021 1:52 PM
+xDid v8 address the queuing issue with v7? On v7, I have 3 backups that run on Day 1 of each month, each spaced 5 minutes apart. The first backup always ran first because,well, it was first. The order of the other 2, however, never seemed consistent. Sometimes #3 would run 2nd and sometimes they'd run in the intended order.
If the order of more than 2 jobs is important, you could schedule 1 script that invoked the other processes in the order that you wanted.
|
By jphughan - 5 July 2021 2:10 PM
^ The downside to that is that if you called the script and it threw an error code other than 0 (success), it wouldn’t be clear which if the jobs caused the exit code.
|
By dweilmuenster - 5 July 2021 3:13 PM
+x+xDid v8 address the queuing issue with v7? On v7, I have 3 backups that run on Day 1 of each month, each spaced 5 minutes apart. The first backup always ran first because,well, it was first. The order of the other 2, however, never seemed consistent. Sometimes #3 would run 2nd and sometimes they'd run in the intended order. If the order of more than 2 jobs is important, you could schedule 1 script that invoked the other processes in the order that you wanted.
Thanks. In my case, the order of the jobs is not important. I'm going to try the suggestion to schedule them to start a few minutes apart and see how that goes.
Regards,
David
|
By dbminter - 5 July 2021 3:23 PM
The order of operations is not important for my queued backups either.
|
|