[Bacula-users] Project Voting
Hello, As you know, we recently did the voting for future projects. The results were tallied by Arno (may thanks) and then reported. I've re-numbered the projects file in the vote order so that the project with the most votes is #1 and with the least is #40. This file is now in the CVS and will be distributed with version 2.0.2, which I hope to release early next week. Many thanks for voting -- we had 50% more votes this time than last, so that is very encouraging. In case you are interested, I have included the updated file at the end of this email. Best regards, Kern Projects: Bacula Projects Roadmap Status updated 26 January 2007 After re-ordering in vote priority Items Completed: Item: 18 Quick release of FD-SD connection after backup. Item: 40 Include JobID in spool file name Summary: Item: 1 Accurate restoration of renamed/deleted files Item: 2 Implement a Bacula GUI/management tool. Item: 3 Allow FD to initiate a backup Item: 4 Merge multiple backups (Synthetic Backup or Consolidation). Item: 5 Deletion of Disk-Based Bacula Volumes Item: 6 Implement Base jobs. Item: 7 Implement creation and maintenance of copy pools Item: 8 Directive/mode to backup only file changes, not entire file Item: 9 Implement a server-side compression feature Item: 10 Improve Bacula's tape and drive usage and cleaning management. Item: 11 Allow skipping execution of Jobs Item: 12 Add a scheduling syntax that permits weekly rotations Item: 13 Archival (removal) of User Files to Tape Item: 14 Cause daemons to use a specific IP address to source communications Item: 15 Multiple threads in file daemon for the same job Item: 16 Add Plug-ins to the FileSet Include statements. Item: 17 Restore only file attributes (permissions, ACL, owner, group...) Item: 18* Quick release of FD-SD connection after backup. Item: 19 Implement a Python interface to the Bacula catalog. Item: 20 Archive data Item: 21 Split documentation Item: 22 Implement support for stacking arbitrary stream filters, sinks. Item: 23 Implement from-client and to-client on restore command line. Item: 24 Add an override in Schedule for Pools based on backup types. Item: 25 Implement huge exclude list support using hashing. Item: 26 Implement more Python events in Bacula. Item: 27 Incorporation of XACML2/SAML2 parsing Item: 28 Filesystem watch triggered backup. Item: 29 Allow inclusion/exclusion of files in a fileset by creation/mod times Item: 30 Tray monitor window cleanups Item: 31 Implement multiple numeric backup levels as supported by dump Item: 32 Automatic promotion of backup levels Item: 33 Clustered file-daemons Item: 34 Commercial database support Item: 35 Automatic disabling of devices Item: 36 An option to operate on all pools with update vol parameters Item: 37 Add an item to the restore option where you can select a pool Item: 38 Include timestamp of job launch in stat clients output Item: 39 Message mailing based on backup types Item: 40* Include JobID in spool file name 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. 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. 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: Implement a Bacula GUI/management tool. Origin: Kern Date: 28 October 2005 Status: What: Implement a Bacula console, and management tools
[Bacula-users] Project voting.
Here are my project votes: Priority Project Number = 124 2 1 325 4 3 510 -- Erik P. Olsen, Civilingeniør, MSc Solsortvej 30, DK-2000 Frederiksberg, Denmark Phone: +45 38346480, Fax: +45 32106480, Mobil: +45 40765300 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Project Voting
Hello, As many of you know, when a new version is released, we vote on the items in the official projects list, which is kept in the main source directory. This voting provides valuable feedback to the developers about which projects are considered the most important. Having a high priority does not automatically guarantee that the project will be implemented in the next version because what is needed is a programmer or someone to submit the code and do the documentation. Just the same, more votes do improve the chances that someone will take an interest in the project. Also, during developement, items that are not on the projects list can be implemented and integrated into the code providing they pass the gatekeeper (me). I'm including below, the current list which includes (hopefully) all the items not completed from the last list and all the items that have been submitted to me since the last vote (05 November 2005). Please look over this list and if you have anything you would like please email it to the bacula-users and bacula-devel list using the same formatting. All new items (that are reasonable) received before 1 January 2007 will be included in the subsequent vote, which will last one or two weeks. Before voiting, you will receive the full list and voting instructions. Best regards, Kern Projects: Bacula Projects Roadmap Status updated 15 December 2006 Summary: Item 1: Accurate restoration of renamed/deleted files from Item 2: Implement a Bacula GUI/management tool. Item 3: Implement Base jobs. Item 4: Implement from-client and to-client on restore command line. Item 5: Implement creation and maintenance of copy pools Item 6: Merge multiple backups (Synthetic Backup or Consolidation). Item 8: Deletion of Disk-Based Bacula Volumes Item 9: Implement a Python interface to the Bacula catalog. Item 10: Archival (removal) of User Files to Tape Item 11: Add Plug-ins to the FileSet Include statements. Item 12: Implement more Python events in Bacula. Item 13: Quick release of FD-SD connection after backup. Item 14: Implement huge exclude list support using hashing. Item 15: Allow skipping execution of Jobs Item 16: Tray monitor window cleanups Item 17: Split documentation Item 18: Automatic promotion of backup levels Item 19: Add an override in Schedule for Pools based on backup types. Item 20: An option to operate on all pools with update vol parameters Item 21: Include JobID in spool file name Item 22: Include timestamp of job launch in stat clients output Item 23: Message mailing based on backup types Item 24: Allow inclusion/exclusion of files in a fileset by creation/mod times Item 25: Improve Bacula's tape and drive usage and cleaning management. Item 26: Implement support for stacking arbitrary stream filters, sinks. Item 27: Allow FD to initiate a backup Item 28: Directive/mode to backup only file changes, not entire file Item 29: Automatic disabling of devices Item 30: Incorporation of XACML2/SAML2 parsing Item 31: Clustered file-daemons Item 32: Commercial database support Item 33: Archive data Item 34: Filesystem watch triggered backup. Item 35: Implement multiple numeric backup levels as supported by dump Below, you will find more information on future projects: Item 1: Accurate restoration of renamed/deleted files from Incremental/Differential backups Date: 28 November 2005 Origin: Martin Simmons (martin at lispworks dot com) Status: 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. 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. 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
Re: [Bacula-users] Project Voting
Summary:
Item new: Add a scheduling syntax that is friendly for weekly rotations
Item new: Add a scheduling syntax that is friendly for weekly rotations
Date: 28 November 2005
Origin: Gregory Brauer (greg at wildbrain dot com)
Status:
What: Currently, Bacula only understands how to deal with weeks of the
month or weeks of the year in schedules. This makes it impossible
to do a true weekly rotation of tapes. There will always be a
discontinuity that will require disruptive manual intervention at
least monthly or yearly because week boundaries never align with
month or year boundaries.
A solution would be to add a new syntax that defines (at least)
a start timestamp, and repetition period.
Why:Rotated backups done at weekly intervals are useful, and Bacula
cannot currently do them without extensive hacking.
Notes: Here is an example syntax showing a 3-week rotation where full
Backups would be performed every week on Saturday, and an
incremental would be performed every week on Tuesday. Each
set of tapes could be removed from the loader for the following
two cycles before coming back and being reused on the third
week. Since the execution times are determined by intervals
from a given point in time, there will never be any issues with
having to adjust to any sort of arbitrary time boundary. In
the example provided, I even define the starting schedule
as crossing both a year and a month boundary, but the run times
would be based on the Repeat value and would therefore happen
weekly as desired.
Schedule {
Name = Week 1 Rotation
#Saturday. Would run Dec 30, Jan 20, Feb 10, etc.
Run {
Options {
Type = Full
Start = 2006-12-30 01:00
Repeat = 3w
}
}
#Tuesday. Would run Jan 2, Jan 23, Feb 13, etc.
Run {
Options {
Type = Incremental
Start = 2007-01-02 01:00
Repeat = 3w
}
}
}
Schedule {
Name = Week 2 Rotation
#Saturday. Would run Jan 6, Jan 27, Feb 17, etc.
Run {
Options {
Type = Full
Start = 2007-01-06 01:00
Repeat = 3w
}
}
#Tuesday. Would run Jan 9, Jan 30, Feb 20, etc.
Run {
Options {
Type = Incremental
Start = 2007-01-09 01:00
Repeat = 3w
}
}
}
Schedule {
Name = Week 3 Rotation
#Saturday. Would run Jan 13, Feb 3, Feb 24, etc.
Run {
Options {
Type = Full
Start = 2007-01-13 01:00
Repeat = 3w
}
}
#Tuesday. Would run Jan 16, Feb 6, Feb 27, etc.
Run {
Options {
Type = Incremental
Start = 2007-01-16 01:00
Repeat = 3w
}
}
}
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Project voting
On Wed, 07 Dec 2005 17:06:19 -0500, Ryan Novosielski [EMAIL PROTECTED] said: Ryan I don't really understand the description of the red/black binary Ryan tree... I'd appreciate it if you could just explain this a little better Ryan (if you're not too busy, it's clearly not urgent). It's just a way of storing values so they can be retrieved again efficiently. The classic binary tree doesn't guarantee efficiently in all cases. Goggle finds lots of references to it. __Martin --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Project voting
Quoting Martin Simmons [EMAIL PROTECTED]: On Wed, 07 Dec 2005 17:06:19 -0500, Ryan Novosielski [EMAIL PROTECTED] said: Ryan I don't really understand the description of the red/black binary Ryan tree... I'd appreciate it if you could just explain this a little better Ryan (if you're not too busy, it's clearly not urgent). It's just a way of storing values so they can be retrieved again efficiently. The classic binary tree doesn't guarantee efficiently in all cases. Goggle finds lots of references to it. Red/black trees are the data structure used by C++ STL maps (associative containers). Any recent data structure text will cover it. IIRC, they are a way to store B-trees in fixed size nodes. HTH, Jeffrey --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Project voting
On Thursday 08 December 2005 22:39, Martin Simmons wrote: On Wed, 07 Dec 2005 17:06:19 -0500, Ryan Novosielski [EMAIL PROTECTED] said: Ryan I don't really understand the description of the red/black binary Ryan tree... I'd appreciate it if you could just explain this a little better Ryan (if you're not too busy, it's clearly not urgent). It's just a way of storing values so they can be retrieved again efficiently. The classic binary tree doesn't guarantee efficiently in all cases. Exactly. The nice property of red/black binary trees is that they are always optimally balanced, which means that searches and inserts are fast. This comes at the expense of a good amount of extra logic during inserts. The red/black binary tree classes are now implemented in Bacula, but replacing the current restore in-memory tree code with red/black binary trees is another story. Basically the in-memory tree would become a separate binary tree for each directory. For small directories, it simply costs more space, but for huge directories, one could have huge savings ... Goggle finds lots of references to it. __Martin -- Best regards, Kern ( /\ V_V --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Project voting
Hello,
I closed the voting on Monday and have tallied the votes. Thank you to
everyone who participated in this vote, both in defining the Feature Requests
and in submitting votes. In total, 61 votes were submitted and counted with
one that came in too late and was not counted (sorry).
The final order with the items renumbered is:
Item 1: Implement data encryption (as opposed to comm encryption)
Item 2: Implement Migration that moves Jobs from one Pool to another.
Item 3: Accurate restoration of renamed/deleted files from
Item 4: Implement a Bacula GUI/management tool using Python.
Item 5: Implement Base jobs.
Item 6: Allow FD to initiate a backup
Item 7: Improve Bacula's tape and drive usage and cleaning management.
Item 8: Implement creation and maintenance of copy pools
Item 9: Implement new {Client}Run{Before|After}Job feature.
Item 10: Merge multiple backups (Synthetic Backup or Consolidation).
Item 11: Deletion of Disk-Based Bacula Volumes
Item 12: Directive/mode to backup only file changes, not entire file
Item 13: Multiple threads in file daemon for the same job
Item 14: Implement red/black binary tree routines.
Item 15: Add support for FileSets in user directories CACHEDIR.TAG
Item 16: Implement extraction of Win32 BackupWrite data.
Item 17: Implement a Python interface to the Bacula catalog.
Item 18: Archival (removal) of User Files to Tape
Item 19: Add Plug-ins to the FileSet Include statements.
Item 20: Implement more Python events in Bacula.
Item 21: Quick release of FD-SD connection after backup.
Item 22: Permit multiple Media Types in an Autochanger
Item 23: Allow different autochanger definitions for one autochanger.
Item 24: Automatic disabling of devices
Item 25: Implement huge exclude list support using hashing.
Since OpenOffice seems to be pretty terrible in exporting a spreadsheet, I
have posted my original OpenOffice file at
http://www.sibbald.com/download/1.39-wishlist-votes.sxc
for those of you who want to see detailed tallying of the votes.
As I have previously stated, this vote provides very important user feedback
on the direction that Bacula should take in the future. The top 5 projects
are encryption, migration, accurate restoration, a nice GUI, and Base jobs
(more efficient backups). I cannot guarantee that those will be the first
projects implemented, but at least we now have a good idea what is important
and what is less important.
By the way, work on items 1, 2, 4, 14, 16, and 22 is currently underway. For
item #1 (data encryption), Landon has recently merged his branch into the
main CVS tree for version 1.39. Nice work, concidering the complexity and the
fact that all the regression scripts pass. Item 4 (GUI) is progressing nicely
thanks to Lucus (see the bacula-devel list), and for item 16 (extraction of
Win32 data), Thorsten completed the implementation several weeks ago.
If you would like to see the detailed current list of projects reordered by
priority, please see:
http://www.sibbald.com/download/projects
It is also in the developer's CVS but will take a few hours to be transferred
into the public CVS ...
--
Best regards,
Kern
(
/\
V_V
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Project voting
I don't really understand the description of the red/black binary tree... I'd appreciate it if you could just explain this a little better (if you're not too busy, it's clearly not urgent). Thanks. _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - User Support Spec. III |$| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
