Re: [bareos-users] Way to prevent from cumulating jobs

2020-06-09 Thread Spadajspadaj



On 09.06.2020 11:30, Andrei Brezan wrote:

On 09/06/2020 11:24, Spadajspadaj wrote:

Hi there.

I'm wondering whether there is a reasonable way to prevent bareos 
from scheduling jobs from same client in quick succession.


Here's what I mean. We have a bareos setup with a single tape drive. 
The jobs are scheduled daily with Inc/Diff/Full schedule. If we fail 
to change tape as requested (sometimes there's noone on site for few 
days), the jobs are getting queued and if we finally do put a new 
tape in, all queued jobs are getting executed. The optimal solution 
would be to execute just one job for each client from the period that 
we had no tape available (of course with highest job level in case of 
different levels queued through few days). But I don't see a nice way 
to do that.


I wouldn't want the jobs to have short timeout and fail quickly (I 
suppose that would work, finally job on lower levels would get 
promoted if there was no appropriate higher level job available, 
right?) but that would mess job status with many failed jobs. But if 
it's the only way...




You can use the Cancel options from 
https://docs.bareos.org/Configuration/Director.html#job-resource. 
Something like:

  Allow Duplicate Jobs = false
  Cancel Lower Level Duplicates = true
  Cancel Queued Duplicates = true



That's exactly what I needed.

Thank you!

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/bb772b07-8b20-75c5-9c68-c28f6a9d13bc%40gmail.com.


Re: [bareos-users] Way to prevent from cumulating jobs

2020-06-09 Thread Andrei Brezan

On 09/06/2020 11:24, Spadajspadaj wrote:

Hi there.

I'm wondering whether there is a reasonable way to prevent bareos from 
scheduling jobs from same client in quick succession.


Here's what I mean. We have a bareos setup with a single tape drive. The 
jobs are scheduled daily with Inc/Diff/Full schedule. If we fail to 
change tape as requested (sometimes there's noone on site for few days), 
the jobs are getting queued and if we finally do put a new tape in, all 
queued jobs are getting executed. The optimal solution would be to 
execute just one job for each client from the period that we had no tape 
available (of course with highest job level in case of different levels 
queued through few days). But I don't see a nice way to do that.


I wouldn't want the jobs to have short timeout and fail quickly (I 
suppose that would work, finally job on lower levels would get promoted 
if there was no appropriate higher level job available, right?) but that 
would mess job status with many failed jobs. But if it's the only way...




You can use the Cancel options from 
https://docs.bareos.org/Configuration/Director.html#job-resource. 
Something like:

  Allow Duplicate Jobs = false
  Cancel Lower Level Duplicates = true
  Cancel Queued Duplicates = true

--
Andrei

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/174f0816-33c3-1f60-47af-60a9d19c4b4a%40gmail.com.


[bareos-users] Way to prevent from cumulating jobs

2020-06-09 Thread Spadajspadaj

Hi there.

I'm wondering whether there is a reasonable way to prevent bareos from 
scheduling jobs from same client in quick succession.


Here's what I mean. We have a bareos setup with a single tape drive. The 
jobs are scheduled daily with Inc/Diff/Full schedule. If we fail to 
change tape as requested (sometimes there's noone on site for few days), 
the jobs are getting queued and if we finally do put a new tape in, all 
queued jobs are getting executed. The optimal solution would be to 
execute just one job for each client from the period that we had no tape 
available (of course with highest job level in case of different levels 
queued through few days). But I don't see a nice way to do that.


I wouldn't want the jobs to have short timeout and fail quickly (I 
suppose that would work, finally job on lower levels would get promoted 
if there was no appropriate higher level job available, right?) but that 
would mess job status with many failed jobs. But if it's the only way...


--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/63fb2302-c4e0-e5fb-a84d-e72d1a16efdb%40gmail.com.