Update projects

git-svn-id: https://bacula.svn.sourceforge.net/svnroot/bacula/trunk@2625 91ce42f0-d328-0410-95d8-f526ca767f89

diff --git a/bacula/projects b/bacula/projects
index fde0368db2fb4f12ea5aac1a5cbd54514fa95da1..544fc660cd124453fc3c9b39574a867f41e548b8 100644 (file)
--- a/bacula/projects
+++ b/bacula/projects
@@ -1,7 +1,7 @@
                 
 Projects:
                      Bacula Projects Roadmap 
-                       22 November 2005
+                       24 November 2005
 
 Below, you will find more information on future projects:
 
@@ -25,12 +25,15 @@ Item 1:   Implement a Migration job type that will move the job
           freed up for current backups while maintaining older
           data on tape drives.
 
-  Notes:  Migration could be triggered by:
+  Notes:   Riege Software have asked for the following migration
+           triggers:
+           Age of Job
+           Highwater mark (stopped by Lowwater mark?)
+                            
+  Notes:  Migration could be additionally triggered by:
            Number of Jobs
            Number of Volumes
-           Age of Jobs
-           Highwater size (keep total size)
-           Lowwater mark
+
 
 Item 2:   Implement extraction of Win32 BackupWrite data.
   Origin: Thorsten Engel <thorsten.engel at matrix-computer dot com>
@@ -96,6 +99,7 @@ Item 5:   Implement more Python events in Bacula.
   Notes:  Recycle event
           Scratch pool event
           NeedVolume event
+          MediaFull event
 
 
 Item 6:   Implement Base jobs.
@@ -490,14 +494,13 @@ Item 19:  Implement new {Client}Run{Before|After}Job feature.
   Notes:  By Kern: I would prefer to have a single new Resource called
           RunScript. More notes from Phil:
 
-            RunsWhen = Before|After
+            RunBeforeJob = yes|no
+            RunAfterJob = yes|no
             RunsAtJobLevels = All|Full|Diff|Inc
 
           The AbortJobOnError, RunsOnSuccess and RunsOnFailure directives
           could be optional, and possibly RunsWhen as well.
 
-          If omitted, RunsWhen would default to Before.
-
           AbortJobOnError would be ignored unless RunsWhen was set to Before
           (or RunsBefore Job set to Yes), and would default to Yes if
           omitted.  If AbortJobOnError was set to No, failure of the script
@@ -509,6 +512,45 @@ Item 19:  Implement new {Client}Run{Before|After}Job feature.
           RunsOnFailure would be ignored unless RunsWhen was set to After,
           and default to No.
 
+          Allow having the before/after status on the script command
+          line so that the same script can be used both before/after.
+          David Boyes.
+
+Item 20:  "Maximum Rewrite (Recycle) Times" for a tape
+    Date: 8 November 2005
+  Origin: Adam Thornton <athornton at sinenomine dot net>
+  Status: 
+
+    What: The ability to use a Volume for at most N re-write times, marking  
+          it unavailable after that.
+
+     Why: I was working with a customer this morning who mentioned that it
+          would be useful to automatically age out tapes that had been
+          rewritten enough times that the media lifespan was becoming
+          questionable (his old backup system supported saying "rewrite this
+          tape 50 times at most." Neither Maximum Volume Jobs nor Volume Use
+          Duration quite does this, because you can have multiple jobs per
+          volume, and it's not entirely guaranteed that time and number of
+          write cycles map linearly (although they probably do in actual
+          usage), and also because "Used" volumes can be recycled, and the
+          status we want here is something like "full and now unwriteable."
+          I haven't looked but I suspect this would require a change in the
+          database format, to keep track of how many cycles a volume has
+          been through, and maybe an additional Status type.
+
+
+Item 21:  Allow FD to initiate a backup
+  Origin: Frank Volf (frank at deze dot org)
+  Date:   17 november 2005
+  Status:
+
+   What:  Provide some means, possibly by a restricted console that
+          allows a FD to initiate a backup, and that uses the connection
+          established by the FD to the Director for the backup so that
+          a Director that is firewalled can do the backup.
+
+   Why:   Makes backup of laptops much easier.
+
 
 ============= Empty RFC form ===========
 Item n:   One line summary ...