> I have few backups over network, which are quite big (50GB and 250GB for > example). I do not consider this a huge backup. I have done 2TB+ backups successfully with bacula.
>I'm expecting them to be quite long jobs, and I'm working on > getting SD in same cabinet for them, but that ideal solution is not there > yet. Anyway, I've noticed something which is considered by me as bug. > Director is scheduling jobs every night, full once a month, differential once > a week, incremental every day. This is working fine, but every month we > having problems with full backup. It seems that it runs for ages and that is > still expected as they big, but every next job for that client seems to be > upgraded to full regardless that full is running just now. Does the first job take more than 1 day? > So, even if full > job finishes fine, we have still full job in queue, and it runs for ages > again, causing cascade of full jobs. Anything I'm missing in config to > prevent this ?? Any 2.4.2 bug ?? > > Bacula on server : > > Version: 2.4.2 (26 July 2008) i686-pc-linux-gnu redhat > > Bacula on clients : > > Version: 2.2.8 (26 January 2008) i686-pc-linux-gnu redhat Enterprise release > Version: 2.2.8 (26 January 2008) i686-pc-linux-gnu redhat Enterprise release > > I can upgrade all to 2.4.3, if you think this will change anything. > John ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
