Hi, I had a problem with space in my bacula server in May 2 so the jobs
had to stay in the queue. In May 3 bacula should do a full backup but due
to the space the job stayed in the queue and then failed. The next jobs
starting to entering the queue too ending up in a long queue.
I solved the problem with space in May 23 and then the queue started to run
again and in May 23 it started an incremental job scheduled to run on May
6. Since the full backup job failed and left the queue on May 3 then this
incremental was upgraded to full. When the job finished the next one in the
queue started, an incremental one that was scheduled to run on May 7.
Now the problem:
This new incremental backup was upgraded to full too even that the previous
one was full. It appears that bacula considered the date of the jobs in the
queue to decide if it should upgrade and not the date of the last full job.
This ending up in bacula upgrading every incremental backup in the queue to
full until May 23 (when I solved the space problem and the full backup was
done) resulting in about 17 full backups in the same month.
Is this normal behaviour? Shouldn't bacula consider the date of the last
full backup since the date the job is running instead of the date the job
was scheduled?
Thanks
--
Rodrigo Abrantes Antunes
Instituto Federal Sul-rio-grandense
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
