>
> hi everyone,
>
> i have a question about bacula job scheduling. I have a pretty simple
> schedule for my backup: do a full backup at the beginning at the month
> and then incremental ones every day:
>
>
> Schedule {
> Name = "DefaultCycle"
> Run = Incremental mon-sun at 23:05
> Run = Full 1st sun at 23:05
> }
>
> now, the problem with this schedule is that full backups often take
> several days to complete. during that period if (for various reasons)
> no previous full backup is available, new incremental backups get
> scheduled and automatically promoted to full backups since no full
> backup exists. is there a way to tell bacula not to schedule new jobs
> unless the previous job from the same schedule has finished?
>
You can add a setting to disallow duplicate jobs (see the manual) on a
per job basis, although when the duplicate tries to run Bacula logs an
error which can be a bit annoying. It works fine apart from that though.
James
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
