I've noticed a no strange behavior when i start a new job.
Bacula verify if there is a Full backup in catalog when the job is add to
the queue but not when the job really start.
It could be a problem if i have already an identical (full) backup in
progress. In this case, when i add the new job in the queue, it doesn't
detect the actually full backup and do another full backup for this job (ok
two equals jobs in queue, it's not often :p). I would prefer have a
differential backup for the second job.
So, maybe, you could move the test at the moment where the job really
starts, no?
Franck
French User
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
