X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=bacula%2Fprojects;h=2ef8fcf575ceb9d7821557b11c451c9d1cdddd81;hb=66dee6a3c21f9523b8149b15a9b2014f952c3ca0;hp=fca2ed9e96f22e689cfdbb4e2036f8e7ff95eb46;hpb=9a656a099eb63f7fde30c28e543c51b704208e80;p=bacula%2Fbacula diff --git a/bacula/projects b/bacula/projects index fca2ed9e96..2ef8fcf575 100644 --- a/bacula/projects +++ b/bacula/projects @@ -1,181 +1,191 @@ Projects: Bacula Projects Roadmap - Status updated 18 August 2007 - After removing items completed in version - 2.2.0 and renumbering - -Items Completed: + Status updated 26 April 2009 Summary: -Item 1: Accurate restoration of renamed/deleted files -Item 2: Allow FD to initiate a backup -Item 3: Merge multiple backups (Synthetic Backup or Consolidation) -Item 4: Implement Catalog directive for Pool resource in Director -Item 5: Add an item to the restore option where you can select a Pool -Item 6: Deletion of disk Volumes when pruned -Item 7: Implement Base jobs -Item 8: Implement Copy pools -Item 9: Scheduling syntax that permits more flexibility and options -Item 10: Message mailing based on backup types -Item 11: Cause daemons to use a specific IP address to source communications -Item 12: Add Plug-ins to the FileSet Include statements. -Item 13: Restore only file attributes (permissions, ACL, owner, group...) -Item 14: Add an override in Schedule for Pools based on backup types -Item 15: Implement more Python events and functions -Item 16: Allow inclusion/exclusion of files in a fileset by creation/mod times -Item 17: Automatic promotion of backup levels based on backup size -Item 18: Better control over Job execution -Item 19: Automatic disabling of devices -Item 20: An option to operate on all pools with update vol parameters -Item 21: Include timestamp of job launch in "stat clients" output -Item 22: Implement Storage daemon compression -Item 23: Improve Bacula's tape and drive usage and cleaning management -Item 24: Multiple threads in file daemon for the same job -Item 25: Archival (removal) of User Files to Tape - - -Item 1: Accurate restoration of renamed/deleted files - Date: 28 November 2005 - Origin: Martin Simmons (martin at lispworks dot com) - Status: Robert Nelson will implement this - - What: When restoring a fileset for a specified date (including "most - recent"), Bacula should give you exactly the files and directories - that existed at the time of the last backup prior to that date. - - Currently this only works if the last backup was a Full backup. - When the last backup was Incremental/Differential, files and - directories that have been renamed or deleted since the last Full - backup are not currently restored correctly. Ditto for files with - extra/fewer hard links than at the time of the last Full backup. - - Why: Incremental/Differential would be much more useful if this worked. - - Notes: Merging of multiple backups into a single one seems to - rely on this working, otherwise the merged backups will not be - truly equivalent to a Full backup. - - Note: Kern: notes shortened. This can be done without the need for - inodes. It is essentially the same as the current Verify job, - but one additional database record must be written, which does - not need any database change. - - Notes: Kern: see if we can correct restoration of directories if - replace=ifnewer is set. Currently, if the directory does not - exist, a "dummy" directory is created, then when all the files - are updated, the dummy directory is newer so the real values - are not updated. - -Item 2: Allow FD to initiate a backup - Origin: Frank Volf (frank at deze dot org) - Date: 17 November 2005 - Status: +Item 1: Allow FD to initiate a backup +Item 2: Ability to restart failed jobs +Item 3: Port bat to Win32 +Item 4: Convert Bacula existing tray monitor on Windows to a stand alone program +Item 5: Ability to import/export Bacula database entities +Item 6: Ability to defer Batch Insert to a later time +Item 7: List InChanger flag when doing restore. +Item 8: Deletion of disk Volumes when pruned +Item 9: Implement Base jobs +Item 10: Scheduling syntax that permits more flexibility and options +Item 11: Reduction of communications bandwidth for a backup +Item 12: Bacula Dir, FD and SD to support proxies +Item 13: Message mailing based on backup types +Item 14: Ability to reconnect a disconnected comm line +Item 15: Include timestamp of job launch in "stat clients" output +Item 16: Add an override in Schedule for Pools based on backup types +Item 17: Automatic promotion of backup levels based on backup size +Item 18: Allow inclusion/exclusion of files in a fileset by creation/mod times +Item 19: Archival (removal) of User Files to Tape +Item 20: Include all conf files in specified directory +Item 21: Implement an interface between Bacula and Amazon's S3. +Item 22: Enable/disable compression depending on storage device (disk/tape) +Item 23: Add EFS support on Windows +Item 24: Data encryption on storage daemon +Item 25: "Maximum Concurrent Jobs" for drives when used with changer device +Item 26: Add MaxVolumeSize/MaxVolumeBytes statement to Storage resource +Item 27: Start spooling even when waiting on tape +Item 28: Enable persistent naming/number of SQL queries +Item 29: Implementation of running Job speed limit. +Item 30: Restore from volumes on multiple storage daemons +Item 28:'restore' menu: enter a JobId, automatically select dependents +Item 31: Backup and Restore of Windows Encrypted Files using Win raw encryption +Item 32: Possibilty to schedule Jobs on last Friday of the month +Item 33: Add Minumum Spool Size directive +Item 34: Cause daemons to use a specific IP address to source communications +Item 35: Add ability to Verify any specified Job. +Item 36: Automatic disabling of devices +Item 37: An option to operate on all pools with update vol parameters +Item 38: Implement Storage daemon compression +Item 39: Improve Bacula's tape and drive usage and cleaning management +Item 40: Multiple threads in file daemon for the same job + + +Item 1: 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. +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. - Why: Makes backup of laptops much easier. +Item 2: Ability to restart failed jobs + Date: 26 April 2009 + Origin: Kern/Eric + Status: + What: Often jobs fail because of a communications line drop or max run time, + cancel, or some other non-critical problem. Currrently any data + saved is lost. This implementation should modify the Storage daemon + so that it saves all the files that it knows are completely backed + up to the Volume -Item 3: Merge multiple backups (Synthetic Backup or Consolidation) - Origin: Marc Cousin and Eric Bollengier - Date: 15 November 2005 - Status: + The jobs should then be marked as incomplete and a subsequent + Incremental Accurate backup will then take into account all the + previously saved job. - What: A merged backup is a backup made without connecting to the Client. - It would be a Merge of existing backups into a single backup. - In effect, it is like a restore but to the backup medium. - - For instance, say that last Sunday we made a full backup. Then - all week long, we created incremental backups, in order to do - them fast. Now comes Sunday again, and we need another full. - The merged backup makes it possible to do instead an incremental - backup (during the night for instance), and then create a merged - backup during the day, by using the full and incrementals from - the week. The merged backup will be exactly like a full made - Sunday night on the tape, but the production interruption on the - Client will be minimal, as the Client will only have to send - incrementals. - - In fact, if it's done correctly, you could merge all the - Incrementals into single Incremental, or all the Incrementals - and the last Differential into a new Differential, or the Full, - last differential and all the Incrementals into a new Full - backup. And there is no need to involve the Client. - - Why: The benefit is that : - - the Client just does an incremental ; - - the merged backup on tape is just as a single full backup, - and can be restored very fast. - - This is also a way of reducing the backup data since the old - data can then be pruned (or not) from the catalog, possibly - allowing older volumes to be recycled - -Item 4: Implement Catalog directive for Pool resource in Director - Origin: Alan Davis adavis@ruckus.com - Date: 6 March 2007 - Status: Submitted - - What: The current behavior is for the director to create all pools - found in the configuration file in all catalogs. Add a - Catalog directive to the Pool resource to specify which - catalog to use for each pool definition. - - Why: This allows different catalogs to have different pool - attributes and eliminates the side-effect of adding - pools to catalogs that don't need/use them. - - Notes: Kern: I think this is relatively easy to do, and it is really - a pre-requisite to a number of the Copy pool, ... projects - that are listed here. + Why: Avoids backuping data already saved. -Item 5: Add an item to the restore option where you can select a Pool - Origin: kshatriyak at gmail dot com - Date: 1/1/2006 - Status: + Notes: Requires Accurate to restart correctly. Must completed have a minimum + volume of data or files stored on Volume before enabling. + +Item 3: Port bat to Win32 + Date: 26 April 2009 + Origin: Kern/Eric + Status: + + What: Make bat run on Win32/64. + + Why: To have GUI on Windows + + Notes: + +Item 4: Convert Bacula existing tray monitor on Windows to a stand alone program + Date: 26 April 2009 + Origin: Kern/Eric + Status: + + What: Separate Win32 tray monitor to be a separate program. + + Why: Vista does not allow SYSTEM services to interact with the + desktop, so the current tray monitor does not work on Vista + machines. - What: In the restore option (Select the most recent backup for a - client) it would be useful to add an option where you can limit - the selection to a certain pool. + Notes: Requires communicating with the FD via the network (simulate + a console connection). - Why: When using cloned jobs, most of the time you have 2 pools - a - disk pool and a tape pool. People who have 2 pools would like to - select the most recent backup from disk, not from tape (tape - would be only needed in emergency). However, the most recent - backup (which may just differ a second from the disk backup) may - be on tape and would be selected. The problem becomes bigger if - you have a full and differential - the most "recent" full backup - may be on disk, while the most recent differential may be on tape - (though the differential on disk may differ even only a second or - so). Bacula will complain that the backups reside on different - media then. For now the only solution now when restoring things - when you have 2 pools is to manually search for the right - job-id's and enter them by hand, which is a bit fault tolerant. - Notes: Kern: This is a nice idea. It could also be the way to support - Jobs that have been Copied (similar to migration, but not yet - implemented). +Item 5: Ability to import/export Bacula database entities + Date: 26 April 2009 + Origin: Eric + Status: + What: Create a Bacula ASCII SQL database independent format that permits + importing and exporting database catalog Job entities. -Item 6: Deletion of disk Volumes when pruned - Date: Nov 25, 2005 + Why: For achival, database clustering, tranfer to other databases + of any SQL engine. + + Notes: Job selection should be by Job, time, Volume, Client, Pool and possibly + other criteria. + + +Item 6: Ability to defer Batch Insert to a later time + Date: 26 April 2009 + Origin: Eric + Status: + + What: Instead of doing a Job Batch Insert at the end of the Job + which might create resource contention with lots of Job, + defer the insert to a later time. + + Why: Permits to focus on getting the data on the Volume and + putting the metadata into the Catalog outside the backup + window. + + Notes: Will use the proposed Bacula ASCII database import/export + format (i.e. dependent on the import/export entities project). + + +Item 7: List InChanger flag when doing restore. + Origin: Jesper Krogh + Date: 17 Oct 2008 + Status: + + What: When doing a restore the restore selection dialog ends by telling stuff + like this: + The job will require the following + Volume(s) Storage(s) SD Device(s) + =========================================================================== + 000741L3 LTO-4 LTO3 + 000866L3 LTO-4 LTO3 + 000765L3 LTO-4 LTO3 + 000764L3 LTO-4 LTO3 + 000756L3 LTO-4 LTO3 + 001759L3 LTO-4 LTO3 + 001763L3 LTO-4 LTO3 + 001762L3 LTO-4 LTO3 + 001767L3 LTO-4 LTO3 + + When having an autochanger, it would be really nice with an inChanger + column so the operator knew if this restore job would stop waiting for + operator intervention. This is done just by selecting the inChanger flag + from the catalog and printing it in a seperate column. + + + Why: This would help getting large restores through minimizing the + time spent waiting for operator to drop by and change tapes in the library. + + Notes: [Kern] I think it would also be good to have the Slot as well, + or some indication that Bacula thinks the volume is in the autochanger + because it depends on both the InChanger flag and the Slot being + valid. + + +Item 8: Deletion of disk Volumes when pruned + Date: Nov 25, 2005 Origin: Ross Boylan (edited by Kern) - Status: + Status: - What: Provide a way for Bacula to automatically remove Volumes + What: Provide a way for Bacula to automatically remove Volumes from the filesystem, or optionally to truncate them. Obviously, the Volume must be pruned prior removal. - Why: This would allow users more control over their Volumes and + Why: This would allow users more control over their Volumes and prevent disk based volumes from consuming too much space. - Notes: The following two directives might do the trick: + Notes: The following two directives might do the trick: Volume Data Retention =