Thanks.

I’ll give it a try, but because of the way my schedules are organized, I won’t know if it worked until this time next month.

If jobs are added in two batches at different times, does the oldest batch have to be completely finished before the newer one is started?

 

My backups are made fd -> file (disk) store -> copy to tape (an old LTO2 drive).

 

One client is huge compared to the others, copying it to tape takes some time (about 5 tapes).

 

My problem is that new incremental backups that should start while it is being copied, just sit there “waiting for execution” until the copy operation has completed – yet they are set to run at a higher priority, neither the storage they are to be written to nor any source fd is in use at the time, and the sd and director both have sufficiently high ‘maximum concurrent jobs’ settings.

 

I’ve gone over all configuration files several times to see if I haven’t forgotten a ‘maximum concurrent’ or so, but I find no reason why those jobs shouldn’t start.

 

PS: sorry if this is a repeat question, it sounds rather familiar while I am writing it, but I didn’t find an older version.  It’s also possible that I started writing it a few months ago, but then decided not to post it and continue searching a bit more ;)

 

 

Do all of your jobs have the same priority setting?  Jobs with different priorities won't execute at the same time.

Ah actually I see that you say above you're using different priority levels.  Make everything the same priority and give it a try. 

The priority thing is a little weird, it doesn't work quite the way one might expect.  It won't kick off a higher priority job until the current running job has completed, so:

- Job 'A' is running with priority 10
- Job 'B' is queued with priority 5

Job 'B' won't execute until Job 'A' has completed.

Something like:

- Job 'A' is running with priority 10
- Job 'B' is queued with priority 5
- Job 'C' is queued with priority 10
- Job 'D' is queued with priority 5

Job 'A' will run until it is complete, then Job 'B' and 'D' will kick off at the same time assuming there's no concurrent limits exceeded, then Job 'C' will kick off once 'B' and 'D' are completed.