Good morning:
I'm having a problem for quite some time with Bacula. I'm backing up about
30 servers (> 1Tb of info), and despite it all works, this problem is
breaking my head a couple of times a month.
I'm planning a scheme of jobs as follows: 1 Full on the first Sunday of each
month, 1 Differential on the others Sundays, and 1 Incremental every other
days.
It has happened on more than one occasion for various reasons, that some of
the backups took longer than expected (especially on a weekend when
differentials are made). This produces a chain reaction as a task that took
more than a day keeps the remaining tasks of the day and late start, and the
next day tasks still later and everything is delayed until manually cancel
all tasks that in my opinion are useless.
One consequence of this is that the next Monday at time when all servers are
in critical use, bacula continues making delayed copies, significantly
reducing the performance of servers, therefore the quality of service, and
producing simultaneously the backup tasks take longer to complete (further
fueling the chain reaction).
My question is whether there is any configuration parameter, allowing Bacula
automatically cancel a daily job, if it is not executed within 24 hours
following initial planned time.
I hope you understand me.
Thank you very much.
Federico D. Torres
División Servicios Tecnológicos
Secretaría de Sistemas de Información
Universidad Blas Pascal
ftorres at ubp.edu.ar
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
