X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=bacula%2Fprojects;h=c007947ba051a3acc9f5fa9a96b99e42c237e436;hb=5f07e231e263958d8486a3291b0a1c0ccd3634a9;hp=ef0dd3ec838b998a4cf9da65aa512658a4cfd9f6;hpb=3412603cac830c60ea20eddcaae08d1a2b8bff6c;p=bacula%2Fbacula diff --git a/bacula/projects b/bacula/projects index ef0dd3ec83..c007947ba0 100644 --- a/bacula/projects +++ b/bacula/projects @@ -1,7 +1,7 @@ Projects: Bacula Projects Roadmap - Status updated 22 February 2008 + Status updated 19 March 2008 Items Completed: @@ -1274,6 +1274,28 @@ Item 1: Backup and Restore of Windows Encrypted Files through raw encryption fun Run = pool=Monthly last Day of the Month at 23:50 + Date: 20 March 2008 + + Origin: Frank Sweetser + + What: Add a new SD directive, "minimum spool size" (or similar). This + directive would specify a minimum level of free space available for + spooling. If the unused spool space is less than this level, any new + spooling requests would be blocked as if the "maximum spool size" + threshold had bee reached. Already spooling jobs would be unaffected + by this directive. + + Why: I've been bitten by this scenario a couple of times: + + Assume a maximum spool size of 100M. Two concurrent jobs, A and B, are + both running. Due to timing quirks and previously running jobs, job A + has used 99.9M of space in the spool directory. While A is busy + despooling to disk, B is happily using the remaining 0.1M of spool + space. This ends up in a spool/despool sequence every 0.1M of data. + In addition to fragmenting the data on the volume far more than was + necessary, in larger data sets (ie, tens or hundreds of gigabytes) it + can easily produce multi-megabyte report emails! + ========== Already implemented ================================ Item n: make changing "spooldata=yes|no" possible for