One pool with more than one job / jobs should not run in parallel
-
I have one pool with a bunch ob VMs. I have three backup jobs created (different requirements for different machines). They all are all set to start at 01:00. As far as I read in the docs, etc. all jobs would run in parallel then. Not sure if this is correct?
Is there any option to define that job 2 runs after job 1 finished. Job 3 after job 2, etc.? Cause I do not know for sure how long each job runs. I can estimate of course, but there is still a risk of "conflict".BR
C -
@cgasser I believe this was discussed in another thread, but to summarize you should set your job-concurrency, otherwise it defaults to something like 4 jobs at once.
But even in that scenario, not every job is going to run at 01:00 because some job would be waiting until the last job has completed, offsetting your start time of the next job.
-
@DustinB Thank's for your response. But how to set my job-concurrency? Like "just 1 job at the time"?
C
-
@cgasser here is an article on it that @olivierlambert wrote some time ago, https://xen-orchestra.com/blog/xen-orchestra-backup-concurrency/
Basically you have to set your concurrency to be lower than the default limit of 2 per the documentation. https://docs.xen-orchestra.com/backups#backup-concurrency
-
If you don't want any jobs running in parallel at all, you would set your concurrency to 1 (or maybe 0) so that only a singular VM would be completely backed up at a given time, but this will certainly break the "Start my Backups at 01:00".
Because your backup jobs are starting at 01:00 for the first VM chosen, but your last VM might not start it's backup until 23:00 the following day depending on your system and network performance...
-
@DustinB Will give it a try with "1". Thank you!
-
@cgasser This sounds like a perfect candidate for the new Backup Sequence feature. See https://xen-orchestra.com/blog/xen-orchestra-5-99/ for full details.
