The size of the backups are normal.  Their shared web servers so
customers can upload just about anything they want.  We have a few
customers that take advantage of all the disk space so they upload
tons of video and large images.

Anyhow, my "solution" is to create a separate schedule for the
stragglers aptly named "bigdogs".  I'll just allow for a 3 days break
in between the full and next incremental.  It's probably not ideal for
every situation but I think it works in mine.

This really should be something that gets addressed in a newer
version.  I don't think it should be forced that the next incremental
be upgraded to a full and start running but at least have an option to
change this behavior.

Maybe we can put a bounty on this request.  I'm sure I could get some
funds from my company to get this feature added.

Regards,

Seth



On Mon, Apr 7, 2008 at 7:04 AM, Drew Bentley <bacula.user AT gmail DOT com> 
wrote:
>

>  One way you could get around this is to make it so only 1 job can run
>  at a time for a particular client. This will allow the full backup to
>  complete and the incremental queued to not actually start until such
>  job is completed.
>
>  But I'd have to agree, what are you backing up that is taking more
>  than two days? I hope you say you've got terabytes of data streaming
>  along or there is something else you should be worried about.
>
>  -Drew

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users