Tag Archives: Bacula Systems

Major Contributions to Bacula since 2008


Those of you who have been with the Bacula project for some time, will recall that I (Kern) publicly stated that my primary purpose in creating Bacula Systems was to ensure the long-term growth of Bacula (the community version). I also stated that my personal involvement with the community would decrease for several years so that I could concentrate on getting Bacula Systems running, but that would not at all decrease the pace of development of Bacula.  This is indeed the case.

To show that the above statements are false, please review the following list of major contributions to Bacula from 2008 until today.  I think you will see that Bacula has been largely and substantially supported by Bacula Systems SA (which includes me).

    Major Community Features added 2008 to 20 February 2013

– The letters BEE mean the Bacula Enterprise Edition by Bacula Systems SA
– Information herein is pulled from public records:
   – New Features Chapter in main Document
   – ReleaseNotes file in the source releases
   – ChangeLog file in the source releases
   – git repository
– This is not meant to be exhaustive
– Some author’s names may be missing

  New Feature or work done                     Contributor
  =====================================        ==========================

5.2.13: 20Feb13
– Many Bug Fixes (21 bug reports closed)    — Bacula Systems SA and others
– Several new minor enhancements            — Bacula Systems SA
– Backport code from BEE                    — Bacula Systems SA

5.2.12: 14Sep12
– New bpluginfo utility                     — Inteos
– Bug fixes (13 bug reports closed)         — Bacula Systems SA and others
– Backport code from BEE                    — Bacula Systems SA

5.2.10: 28Jun12
– Significant fixes (6 bug reports closed)  — Bacula Systems SA and others
– Rudimentary AFS support — now depreciated
– Backport Windows code from BEE            — Bacula Systems SA

5.2.9: 12Jun12
– Bug fixes (5 bug reports closed)          — Bacula Systems and others

5.2.7: 02Jun12
– Many code cleanups and rewrites           — Bacula Systems SA and others
– Closed 12 bug reports
– Backport StorageId code from BEE          — Bacula Systems SA

5.2.6: 18Feb12
– Exchange plugin work with Accurate mode   — Bacula Systems SA
– Add wild card to restore cd command       — Bacula Systems SA
– Many important fixes (closed 1 bug report)
– Backport debug for sd plugins from BEE    — Bacula Systems SA

5.2.4: 18Jan12
– Significant improvement to spec files     — Bacula Systems SA
– Fix versioning of share objects           — Bacula Systems SA
– Many bug fixes (9 bug reports closed)
– Many smaller enhancements                 — Bacula Systems SA

5.2.2 24Nov11
– Additions to RunScript variables
– Add -t option on Bat
– Backport plugin code from BEE             — Bacula Systems SA
– 4 bug reports closed
– Backport from BEE                         — Bacula Systems SA

5.2.1 30Oct11
5.2.0rc1 08Jul11
– Major Version Release with many
     new features and lots of new code
– Many Bug Fixes (88 bug reports closed)    — mostly Bacula Systems SA
– LZO Compression                           — Laurent Papier
– New Qt Based Tray Monitor                 — Bacula Systems SA
– Purge Migration Job                       — Bacula Systems SA
– Changes in Bvfs (Bacula Virtual FS)       — Bacula Systems SA
– Changes in the Pruning Algorithm          — Bacula Systems SA
– Additions to RunScript variables
– Additions to the Plugin API               — Bacula Systems SA
– ACL Enhancements                          — Planets Communications B.V. and
                                               ELM Consultancy B.V.
– Class Based Database Backend Drivers      — Planets Communications B.V. and
                                               ELM Consultancy B.V.
– Many backports from BEE                   — Bacula Systems SA

5.0.3 04Aug10
– Truncate Volume after Purge               — Bacula Systems SA
– Many Bug Fixes                            — Bacula Systems SA

5.0.0 22Jan10
– Maximum Concurrent Jobs for Devices       — Bacula Systems SA
– Restore from Multiple Storage Daemons     — Bacula Systems SA and
                                               Equiinet, Ltd.
– File Deduplication using Base Jobs        — Bacula Systems SA
– AllowCompression                          — Collaborative Fusion, Inc.
– Accurate Fileset Options                  — Bacula Systems SA
– Tab-completion for Bconsole               — Bacula Systems SA
– Pool File and Job Retention               — Bacula Systems SA
– Read-only File Daemon using capabilities  — AltLinux
– Bvfs API                                  — Bacula Systems SA
– Testing Tape Drive Speed Command          — Bacula Systems SA
– Block Checksum Device Directive           — Bacula Systems SA
– Significant New Bat Features              — Bacula Systems SA
– Port Bat to Windows                       — Bacula Systems SA
– Linux Bare Metal Recovery USB Key         — Bacula Systems SA
– bconsole Timeout Option                   — Bacula Systems SA
– Many Important Changes                    — Bacula Systems SA and others
– Big backport from Bacula Enterprise       — Bacula Systems SA

3.0.0 28Dec08
– Accurate Backup                           — Bacula Systems SA
– Copy Jobs                                 — Bacula Systems SA
– ACL Updates and Extended Attributes
– Virtual Backup                            — Bacula Systems SA
– Implement 64 bit Windows Client           — Bacula Systems SA
– Duplicate Job Control                     — Bacula Systems SA
– TLS Authentication                        — Bacula Systems SA
– bextract non-portable Win32 data          — Bacula Systems SA
– State File updated at Job Termination
– MaxFull/DiffInterval                      — Bacula Systems SA
– Honor NoDumpFlag & ExcludeDirContaining
– Bacula Plugins                            — Bacula Systems SA
– Microsoft Exchange 2003/2007 Plugin       — Bacula Systems and
                                               Equiinet, Ltd.
– Many Additional Smaller Features          — Bacula Systems SA

Bacula Status Report


I would like to speak to you about the following points:

1. The rumors of the death of Bacula (the Community version)
2. Bacula Systems and the FSFE (Free Software Foundation Europe)
3. The future of Bacula (the Community version)

1. The rumors of the death of Bacula (the Community version):

I borrow words from a quote of Mark Twain : The rumors of the death of Bacula are highly exaggerated!

I began working on Bacula 14 years ago (in January 2000), and it has been Open Source from the time it was publicly released in April 2002, and it will remain Open Source. I have been and am fully devoted to Open Source, and in particular to Bacula, which is like my “baby”.

I did inform the Bacula Community several years ago that my personal participation in Bacula would decrease a bit for several years to allow me to focus more on getting Bacula Systems started. In my opinion, that has not been a serious disadvantage for the Bacula project since Bacula Systems over that period has contributed far more code to Bacula than I could have alone over the same period, and as you will see a bit later in this status report, Bacula Systems contributions are absolutely guaranteed to continue in the long run, and even increase.

2. Bacula Systems and the FSFE:

If you have been a long time Bacula user you may recall that I discussed the possibility in 2006-2007 of creating a company, now called Bacula Systems, to ensure the continuation of Bacula when I will no longer be able to personally contribute – say in 10 or 20 years, as well as to provide the financial means to add high-end features to Bacula (a fibre channel network costs about $50K to set up). Much to my surprise 95% or more of the responses I got were very positive. Bacula Systems was created in July 2008, and for the first two years, the Enterprise code base and the Community code base were identical. Unfortunately, that didn’t work financially for Bacula Systems. Companies willing to pay, were willing to pay for features and support but not support alone, so Bacula Systems embarked on development to continue maintenance and improvement of Bacula while at the same time creating mostly plugins to add differentiation to the Enterprise version.

Now this may not sound very Open Source to you, and I understand, because I feel the same way. Were it at all possible, I would give you all of Bacula Systems code, unfortunately, that is not economically feasible at the current time, and yet without Bacula Systems, I fear the Bacula project will die or worse yet fall into the hands of someone incapable of maintaining the high quality we have created.

In mid-2013, Bacula Systems and I began discussions with the FSFE on how to guarantee the long-term survival of Bacula. These discussions, extremely positive on both sides and all points, recently lead to a formal written agreement between myself, Bacula Systems, and the FSFE. There are a number of points in the agreement, but probably the most important of all is that Bacula Systems has now put in writing that it is an Open Source company (at its heart), as it has always proclaimed, and will contribute all the Enterprise code it creates to the Bacula Community code base within at most a 5 year period. One exception is that Bacula Systems is legally unable to contribute certain code encumbered by third-party proprietary license. The 5 year delay gives Bacula Systems the chance to develop Enterprise features that differentiate it, but ensures the continual growth of the Bacula Community code. This model can possibly be used across the industry to ensure the future of open source software in an environment where development costs, particularly for hardware to do testing, are prohibitive to the standard models of today.

5. The future of Bacula (the Community version):

If you have read section 4 above, hopefully if you were not already convinced that Bacula is alive that you can now see that it will have a long and successful future ahead of it. If you have any doubts, please do not hesitate to either send me an email on the bacula-users list or directly to me (if you want it private). Hopefully, by mid-December I will have a blog setup (need a major upgrade of bacula.org to do so), and I will then fill you in on what next to expect in Bacula.

Thank you for contributing to and/or using Bacula …

Best regards,