I have the following schedule at a site I deal with: Full on the first saturday of every month. Incremental on non-full saturdays plus sun-fri.
The problem: When the first incremental backup is run, Bacula promotes it to a full as expected since there is no prior full. However, this backup is roughly 1TB being compressed and written to an NFS share at approx. 1.5MB/s. Thus, the full backup takes over 48 hours to complete. While that is running, the Bacula scheduler kicks-in on the next day and the day after, queueing-up those day's backups. However, because the full that those backups depend on is still running and has not been committed to the catalog, those jobs are likewise promoted to fulls. When the initial backup completes, it is immediately followed by 2 more full backups which exceeds the space available. Although this can be worked around by temporarily disabling the incremental schedules, it is not ideal since the problem will only occur again when the 50-day retention period is exceeded. Is it possible for Bacula to determine whether or not an incremental job should be promoted to a full at the time the job starts running rather than at the time the job gets queued by the scheduler? That would solve my problem since any incremental jobs that were queued while their dependent full was still running would not get promoted to fulls themselves. I suspect this is a corner-case since backups, even fulls, that take longer than 24 hours (let alone 48 hours) are rare. --PLB ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
