Re: [Bacula-users] Limit job rescheduling
Mandi! Andrea Venturoli In chel di` si favelave... > That's something I had seen and pondered. > However, it will stop a job that is already running, won't it? Yep. ;-) > So, in my case, if a job started late in the afternoon it wouldn't be > allowed to complete. Right? Right. I know my users, so i've simply setup two schedule, one that start at 8.00 and one that start at 13.00: i assign the diferent schedule to different habits of users. Not perfect but... -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Limit job rescheduling
On 6/21/24 14:44, Lionel PLASSE wrote: Hello, Hello and thanks for answering. And maybe you can study those options behavior and adjust in your case: Duplicates and priorities AllowMixedPriority: AllowDuplicateJobs: CancelLowerLevelDuplicates: CancelQueuedDuplicates: CancelRunningDuplicates: I've seen those options and I use some of them: I already cancel duplicate jobs. However, I'm perplexed... Either I'm missing somehing or they can't achieve what I'm trying to get. bye & Thanks av. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Limit job rescheduling
Hello, I read your post : > > > i set 'Max Run Sched Time = 8 hours' to prevent conflicts). > > That's something I had seen and pondered. > However, it will stop a job that is already running, won't it? > So, in my case, if a job started late in the afternoon it wouldn't be > allowed to complete. Right? And maybe you can study those options behavior and adjust in your case: Duplicates and priorities AllowMixedPriority: AllowDuplicateJobs: CancelLowerLevelDuplicates: CancelQueuedDuplicates: CancelRunningDuplicates: -Message d'origine- De : Andrea Venturoli Envoyé : vendredi 21 juin 2024 10:42 À : bacula-users@lists.sourceforge.net Objet : Re: [Bacula-users] Limit job rescheduling On 6/20/24 17:05, Marco Gaiarin wrote: > Ciao Andrea. Ciao. > i set 'Max Run Sched Time = 8 hours' to prevent conflicts). That's something I had seen and pondered. However, it will stop a job that is already running, won't it? So, in my case, if a job started late in the afternoon it wouldn't be allowed to complete. Right? > So i've moved most client on static ip. I always use static DHCP entries for clients I know about :) bye & Thanks av. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Limit job rescheduling
On 6/20/24 17:05, Marco Gaiarin wrote: Ciao Andrea. Ciao. i set 'Max Run Sched Time = 8 hours' to prevent conflicts). That's something I had seen and pondered. However, it will stop a job that is already running, won't it? So, in my case, if a job started late in the afternoon it wouldn't be allowed to complete. Right? So i've moved most client on static ip. I always use static DHCP entries for clients I know about :) bye & Thanks av. ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Limit job rescheduling
Mandi! Andrea Venturoli In chel di` si favelave... > At a site, I'm backing up several machines, most of which are clients > that are not powered on every day. Ciao Andrea. I use roughly the same schedule: Allow Duplicate Jobs = no Cancel Lower Level Duplicates = yes Reschedule On Error = yes Reschedule Interval = 30 minutes Reschedule Times = 8 Max Run Sched Time = 8 hours and effectively jobs, starting at the same time, tent to 'clog' the director (but i run that when i've no 'main' backup job, and i set 'Max Run Sched Time = 8 hours' to prevent conflicts). Also, i've noted that for client on dynamic IP, timout are longer: eg bacula fail immediately if client are not reachable, but fail more slowly if client does not exist in DNS. So i've moved most client on static ip. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Limit job rescheduling
Hello.
At a site, I'm backing up several machines, most of which are clients
that are not powered on every day.
I've set up the following schedule and jobs:
Schedule {
Name="DailyFDI"
Run=Full 1st sun at 09:30
Run=Differential 2nd-5th sun at 09:30
Run=Incremental mon-sat at 09:30
}
Job {
Name=example
Client=example
Schedule=DailyFDI
Reschedule On Error=yes
Reschedule Interval=3600
Reschedule Times=11
Max Start Delay=36000
...
}
The intention is that:
_ jobs are scheduled at 9:30;
_ if the clients does not respond, they are rescheduled one hour later
and so on, up to 19:30;
_ after 19:30 the job should fail in order to free the queues for
servers/always-on devices which are backed up at night;
_ N.B. If a job starts at 19:29 I don't want to stop it, but let it finish.
However, it does not work like that.
Since there are many clients, they delay each other, and it seems "Max
Start Delay" starts over at each reschedule, so these jobs stay
scheduled all the night through and even the day after (when duplicate
jobs are cancelled).
Is there a settings similar to "Max Start Delay", but which counts from
the first schedule of the job (in my case 9:30)?
Thanks in advance
av.
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
