Category Status Reports

Bacula Status Report — 7 November 2018

The last Status Report was in June of this year, so I would like to bring you up to date on a few items.

I would like to discuss the following subjects:

1. Bacula Release Status

2. Bacula Binaries

3. Windows Binaries

4. Next Bacula Version

5. New Website

===

1. Bacula Release Status
The latest Bacula version 9.2.2 was released today to Source Forge and to www.bacula.org.  This is a small update to the previous version.

2. Bacula Binaries
Thanks to the build support from Bacula Systems, we now have binaries for a number of popular distributions (the 9.2.2 binaries will be coming shortly).  If you need additional distributions, please notify us on the bacula-users email list.  However, please realize that it takes time to make new distribution releases, and if it is not a platform that is supported by Bacula Systems, it takes even longer for us to install and configure those platforms for the binary build process.

The release format is with standard packaging using debs rpms, … that are specific to each system. However, unlike most Linux distributions, we install the Community Binaries into the directory /opt/bacula as recommended in the Bacula manual and as used by the Bacula Enterprise Edition. This Bacula file release standard is not uncommon and vastly simplifies installation, support, backup and recovery of Bacula itself. Basically, most of the release will be installed into /opt/bacula except for the few system files that must be placed in certain locations such as the start/stop scripts and the man text.

One change is that we ask you to register to get access to the binaries. This is very similar to signing up for the email lists. We have always been interested in who is using Bacula, and provided you supply correct information, this registration will help. You will be asked a few simple questions and also be given an opportunity to receive the Bacula Enterprise Newsletter. If you decline the newsletter, you will not be bothered. The advantage of getting the newsletter is you will be informed what is coming in the next Enterprise releases, which means that most of those features will follow into a subsequent community release.

To register and get access to Bacula pre-built binaries please go to www.bacula.org and on the main menu bar select Downloads -> Bacula Binary Package Download, then fill out the registration.  Note, ultimately you will receive a special download link that will give you access to the binaries.  Please keep that link for future access to the binary repository for updates and new releases.

3. Windows Binaries
Since version 9.0.0, we have re-integrated the Windows File daemon source code, and built Windows Binaries packages. They can be found in www.bacula.org -> Downloads -> Binary Download Center. Version 9.2.2 are currently available.

4. Next Bacula Version
We have begun working on the next version of Bacula. This release will most likely be called version 9.4.0.  Aside from backports of minor new features and bug fixes from Bacula Enterprise, it also includes Cloud drivers that work with Amazon S3.  It will also work with any truly S3 vendor.  Please note: Oracle and Google has so called S3 service but they are not compatible.  Windows, of course, has Azure, which is very different.  Thus, Oracle, Google, and Windows Azure are not compatible with the up coming release 9.4.0.  Hopefully this release will be available before the end of the year or at the latest, early next year.

5. New Website
As many of you have noticed, we now have a new more modern Website. Many thanks to Sasha, Andrei, Davide, and Rob for making this happen. Due to the complexity of current websites that user WordPress as we do, it is a tremendous amount of work to make this kind of change. I also would like to thank all of you who gave your comments on preliminary versions of this new website. We took into account every comment and many of them were extremely helpful.

Thanks for using Bacula — be happy.

Kern

Bacula Status Report — 22 June 2018

We recently released prebuilt binaries on bacula.org, and some of you have downloaded them and had varying degrees of luck installing them. Concerning the installation of Ubuntu 18.04 (Bionic Beaver), I have personally installed, configured and run it, including running with the Aligned plugin, and from the brief testing I did, it works well. However, I did notice a few errors in the installation guide, which I have corrected in version 1.3 of the guide. I expect that all the “debs” packages should work equally well.

On the other hand, we have reproduced some false dependency problems in the rpm builds. This is probably due to the RedHat macro that automatically searches for dependencies, which in my experience is very error prone. We are working to fix those problems, and I will let you know as soon as we are sure they are working.

In the mean time, if you are using deb packaging, I recommend that you try, and please report back your experiences. Also, please check that you are looking at version 1.3 (22 June 2018) of the Installation guide. My Firefox browser caches the display of this document (in the White Papers section), and so often shows an older version. Either clear your cache or use a program such a wget to download the pdf.

Currently we have released binaries for about 10 common distros. If you would like additional platforms, please let us know (bacula-users list), but please allow some time for us to build them.

Many thanks to Davide Franco for building the binaries for the Bacula project.

Best regards,
Kern

Bacula Status Report — 9 June 2018

It has been a while since the last status report, so it is now time.

I would like to discuss the following subjects:

1. Bacula Release Status

2. Bacula Binaries (New)

3. Windows Binaries (more coming)

4. Next Bacula Version

===

1. Bacula Release Status
As probably know, the latest Bacula version 9.0.8 was released recently to Source Forge and will be released to www.bacula.org shortly. Mostly this release corrects some copyright oversights. However, since version 9.0.0, we have had several minor releases, so most of the minor annoyances, including a few long time bugs are behind us. Just the same there are quite a few additional fixes and many new features coming in the next release (see below).

2. Bacula Binaries
We are pleased to announce that Bacula binaries have been built for a few of the most popular platforms. This is thanks to the build support from Bacula Systems. We will start with a small number most popular binaries and over time expand it to include a broader base of OS releases. In this release is the Aligned driver plugin for the Storage daemon, which permits Bacula to write an archive volume that is properly aligned so that it can bee deduplicated by filesystems such as ZFS and NetApp.

Please note that the release format is with standard packaging using debs rpms, … that are specific to each system. However, unlike most Linux distributions, we install the Community Binaries into the directory /opt/bacula as recommended in the Bacula manual and as used by the Bacula Enterprise Edition. This Bacula file release standard is not uncommon and vastly simplifies installation, support, backup and recovery of Bacula itself. Basically, most of the release will be installed into /opt/bacula except for the few system files that must be placed in certain locations such as the start/stop scripts and the man text.

One change is that we ask you to register to get access to the binaries. This is very similar to signing up for the email lists. We have always been interested in who is using Bacula, and provided you supply correct information, this registration will help. You will be asked a few simple questions and also be given an opportunity to receive the Bacula Enterprise Newsletter. If you decline the newsletter, you will not be bothered. The advantage of getting the newsletter is you will be informed what is coming in the next Enterprise releases, which means that most of those features will follow into a subsequent community release.

To register and get access to Bacula pre-built binaries please go to www.bacula.org and on the main menu bar select Downloads -> Bacula Binary Package Download, then fill out the registration.

3. Windows Binaries
Since version 9.0.0, we have re-integrated the Windows File daemon source code, and built Windows Binaries packages. They can be found in www.bacula.org -> Downloads -> Binary Download Center. Version 9.0.8 binaries will be uploaded shortly.

4. Next Bacula Version
We have begun working on the next version of Bacula. It may be released as version 9.2.0 or possibly 11.0.0. The major part of this new release consists of backporting more Bacula Enterprise features — for example, getting the tray-monitor to build correctly as well as many performance improvements.

Thanks for using Bacula — be happy.

Kern

Bacula Status Report — 17 March 2017

The last Status Report was in October 2016, so it is probably time for another one.
I would like to discuss the following subjects:

1. Bacula Release Status

2. Bacula Binaries

3. Next Bacula Version

4. My “retirement”

1. Bacula Release Status
As probably know, the latest release of Bacula version 7.4.7 was released on 16 March 2017. Since version 7.4.0, we have had several minor releases, so most of the minor annoyances, including a few long time bugs are behind us. Just the same there are quite a few additional fixes and many new features coming in the next release (see below).

2. Bacula Binaries
As soon as possible we will be releasing Bacula binaries built for the most popular platforms. This is thanks to the build support from Bacula Systems. We will start with a small number most popular binaries and over time expand it to include a broader base of OS releases.

Please note that the release format will be through standard packaging using debs rpms, … that are specific to each system. However, unlike most Linux distributions, we will install the Community Binaries into the directory /opt/bacula as recommended in the Bacula manual and as used by the Bacula Enterprise Edition. This Bacula file release standard is not uncommon and vastly simplifies installation, support, backup and recovery of Bacula itself. Basically, most of the release will be installed into /opt/bacula except for the few system files that must be placed in certain locations such as the start/stop scripts and the man text.

One change that may be a bit controversial for some of you is that we will ask you to register to get access to the binaries. This will really not be too different from signing up for the email lists. I have always wanted to know who is using Bacula and provided you supply correct information, this will help a lot. You will be asked a few simple questions and also be given an opportunity to receive the Bacula Enterprise Newsletter. If you decline the newsletter, you will not be bothered. The advantage of getting the newsletter is you will be informed what is coming in the next Enterprise releases, which means that most of those features will follow into a subsequent community release.

3. Next Bacula Version
I had expected to release the next major version of Bacula in the March-June time frame. The good news is that I have finished the major part of the backporting (currently almost 600,000 lines of code difference from release 7.4). The new release (probably 9.0.0) will not occur in March but hopefully will occur before the end of June. The backporting now compiles correctly, but getting it to work and pass all the regression tests will be several more months of work.

One of the main changes involved massive changes in the Storage Daemon architecture. Basically this first major step has converted the Storage Daemon device drivers into a class based architecture, which allows us to easily and more reliably add new drivers, such as deduplication and cloud backup.

4. “Retirement”
I have been trying for some time to retire (long overdue), and I think I have now succeeded, which means that I have no fixed outside work obligations. This allows me to devote as much time as I want to the Community version of Bacula, and I am now able to choose which programming projects I work on as well as set my own deadlines. So I am not really retiring (the reason I put the word in quotes), but it is nice to make my own schedules and still have more time for the community.

Thanks for using Bacula — be happy.

Kern

Bacula Status Report — 5 October 2016

The last Status Report was in February 2016, so this one is a bit
overdue. That said, I would like to discuss the following subjects:

1. Bacula Release Status

2. Windows Binaries

3. Next Bacula Version

4. Bacula Forks

5. The Storage, Visualisation, Cloud (SVC) awards 2016

1. Bacula Release Status
As probably know, the latest release of Bacula version 7.4.4 was released on 20 September 2016. Since version 7.4.0, we have had several minor releases, which are in general due to new MySQL and C++ software versions that created incompatibilities with Bacula. Hopefully all those are behind us.

The MySQL problems were:
1. MySQL no longer accepts 0 for a DATETIME default (despite the act that 0 is a perfectly valid Unix time value). This was fixed by removing the DEFAULT for all DATETIME fields.
2. MySQL no longer releases the _r.so version of the library needed by Bacula since they now include the thread safe feature in the standard library. This was fixed by using more modern tools for detecting libraries.

The C++ problems were that the new GCC 6.0 aggressive compiler behavior that elides (deletes) code written by the Bacula developers. There is no benefit to the new GCC aggressive optimization and it breaks a lot of programs including Bacula. This problem showed up on ArchLinux and Fedora 24.

2. Windows Binaries
I have now rebuilt the Enterprise Windows binaries to be compatible with Bacula version 7.4.4. They are currently available in the ww.bacula.org  “Download Center”. If you want them for non-personal usage, please go to the Bacula Systems web site where you will find the binaries at a very reasonable price.

As soon as possible we will be releasing Bacula binaries built for the most popular platforms, so I have decided to split the current Download Center page on www.bacula.org into a Source Download page and a Binaries Download page. Please take note of it, because I will move the Windows binaries from the current single download page into the binary download page.

3. Next Bacula Version
I had expected to release the next major version of Bacula in October or November, but due to recent massive changes in the Storage Daemon architecture, it will take me until the March-June time frame to get everything properly integrated. This will be the first major step in a large rewrite of the Storage Daemon. The second step will come 6-9 months later (if all goes well).

Basically this first major step has converted the Storage Daemon device drivers into a class based architecture, which allows us to easily and more reliably add new drivers, such as deduplication and cloud backup.

4. Bacula Forks
Since Bacula is an Open Source project anyone can take the code and add to it or modify it as they like. However if they then redistribute it, they need to abide by the Open Source license. In the case of Bacula this is GPLv3. When someone forks Bacula, it is a sign that they like to code.

However, in most cases (not all) forking, in my personal opinion, leads to duplication of effort, which is a pity since it is difficult to create a code base such as Bacula. We encourage people to contribute with patches, bug reports, ideas, and feature requests on our bugs site:
http://bugs.bacula.org/

As you probably know there are several known forks of Bacula, but there are also least two others that have forked Bacula without any announcement. One is commercial, and the other seems to be a country sponsored fork.

Concerning one of the known forks, in September there was a post from the the main Bareos developer and by far their most experienced developer announcing that he has quit the project.

This announcement is not a surprise for me as I have been expecting it at some point, simply because it is very difficult or impossible to be the only senior developer for a project the size of Bacula and hence for this particular fork. This announcement reinforces the Bacula position as the world’s most popular and most used Open Source backup software. Unfortunately for Bareos users, (in my personal opinion) it also puts a question mark on the future prospects for the project.

A problem of this type is not a possibility for the Bacula project, because there are multiple senior developers and also Bacula Systems is constantly developing new code that is flowing back to the community version. Thus the Bacula project is assured of having a bright future ahead.

5. The SVC Awards 2016
Bacula has been nominated for the SVC awards. The award is based on the number of votes that the nominee receives. Unfortunately they accept only votes from buisnesses. So if you are a business (or other entity) and like Bacula, you might want to vote (hopefully for Bacula). To do so, please see:

http://www.svcawards.com/

Note, the voting closes 11 November.

Thanks for using Bacula — be happy.

Kern

Bacula Status Report — 4 February 2016

I would like to discuss the following topics:

1. Bacula Release Status

2. Next Release

3. Vacation

1. Bacula Release Status
As probably know, the latest release of Bacula version 7.4.0 was released on 16 January 2016. This will be a quite stable release because it is based on version 7.2.0 (very stable) plus a few Enterprise bug fixes and features, which are well tested. As always the new code has been very well tested on Linux, but there could be a few minor problems on other OS versions such as Solaris.

2. Next Version

I expect that the next Bacula community version will be released in October or November, and as usual, it will have a number of backports from the Enterprise version as well as some new features that have been submitted (see bacula-devel list and bug reports) thanks to devoted community developers :-). There are also some new features that I have been working on and others I have planned.

This next Bacula version will be more significant than the 7.4.0 release, if only because one of the submissions that was held back in the 7.4.0 release requires a database upgrade. In addition, if all works out as I plan, there will be a number of other nice new features. Finally I hope to finally fix some of the outstanding bug reports that are annoying to users, but have been on hold since it takes a large amount of time to duplicate those particular problems.

3. Vacation
You may recall that last year I was away on vacation several months. Because Bacula Systems is doing very well with the means to hire new programmers, that permits me to do two things:

1. Take more vacation time — this time in Australia, Bali, Micronesia, and Japan.

2. Be able to consistently devote far more time to developing features important for the community version, which I have been doing since December of last year and will continue to do indefinitely.

When I have Internet and time, I will monitor the Bacula status and respond in case of a serious problem, while in my absence Eric Bollengier will be ensuring that the bacula.org site continues to function (it has been the target of several DoS attacks since the 7.4.0 release).

Thanks for using Bacula — be happy.

Kern

Bacula Status Report 27 August 2015

I would like to discuss the following topics:

1. Bacula Release Status

2. The FSFE and licenses

3. Vacation

1. Bacula Release Status
As probably know, the latest release of Bacula version 7.2.0 was released on 14 August 2015. This should be a quite stable release because it is based on the latest Enterprise version, which is well tested. However, it also has a some new refactored code. The new code has been very well tested on Linux, but I expect a few compilation problems on other OS versions such as Solaris and FreeBSD where I did not unfortunately have time to test this release (see point 3 below).

2. The FSFE and licenses
In my last Status report of 15 April 2015, I mentioned that the relationship that the FSFE and Bacula have had since 2006 was in the process of changing. The latest status of that change has been published at:

https://fsfe.org/news/2015/news-20150817-01.en.html

I repeat here what I wrote in the last status report in April:

As many of you know in 2006, I signed a Fiduciary License Agreement (FLA) that gave the FSFE the exclusive copyright for the Bacula.org software. That means that they had the responsibility to protect the software. In 2006, I felt that the Bacula project needed protection and guidance of the FSFE and their FLA process, and I was pleased to have their help. As the project has grown and become more global and solid, I feel that I can more efficiently manage this responsibility myself, and I thank the FSFE for their help over the years.

The Bacula.org software that has been released will always remain Free Software, and it is not possible for anyone to change that fact. I have been writing and releasing free software and open source software since 1972, and as I have stated many times, I am and will remain a very strong supporter and creator of open source software, and future Bacula.org community software will always be open source.

The bottom line is: this is a consolidation of the copyright holder, and there is no practical change for Bacula users. From a licensing stand point, we will have most, if not all, the licenses held by a single party (ultimately the Bacula Foundation) rather than held by two different parties (FSFE and myself).

If you have never signed a Fiduciary License Agreement (FLA) with the FSFE, you need do nothing. If you have previously signed an FLA with the FSFE (even if you also signed one with me), then you would do the Bacula project (and me) a big service by going to:

www.bacula.org -> General -> License

and then click on the Copyright Assignment Agreement link at the bottom of that page, print it, fill it out, sign it, and send it to me either by regular mail or as a scanned pdf of all pages.

3. Vacation
Backporting the Enterprise code to the community was a big and hard project because the code bases had significantly diverged, but it is now done. Consequently, I will be on vacation in the USA and Canada between now and the first week in October. There will be a maintenance or bug fix release with at least one new feature probably in November to cleanup any new bugs and the build problems.

Thanks for using Bacula.

Kern

Bacula Status Report 15 April 2015

I would like to discuss the following topics:

1. Bacula Release Status

2. The FSFE and licenses

1. Bacula Release Status
As probably know, the latest release of Bacula is 7.0.5. This release  has proved quite stable but there are a few bugs open on it, and I am working on them. I am also working on back porting bug fixes and new features from the Bacula Enterprise version 8.2.0. I hope this work will be complete sometime in June so that I can make a new release (7.2.0) in June or July of this year.

In addition, Bacula Systems has hired a new IT Administrator who will begin in May. Part of his time will be devoted to improving the Bacula community web site as well as providing binary packages for the community. Providing binary packages for the community has been an ongoing project of mine, which has been delayed due to lack of man-power. By the way, the new IT Administrator has been working with Bacula for a long time and is well known to the community.

2. The FSFE and licenses
I would like to report that the FSFE has posted a notification of changed relations between the FSFE and myself. You can find the statement at the following link:

http://fsfe.org/news/2015/news-20150414-01.en.html

As many of you know in 2006, I signed a Fiduciary License Agreement (FLA) that gave the FSFE the exclusive copyright for the Bacula.org software. That means that they had the responsibility to protect the software. In 2006, I felt that the Bacula project needed protection and guidance of the FSFE and their FLA process, and I was pleased to have their help. As the project has grown and become more global and solid, I feel that I can more efficiently manage this responsibility myself, and I thank the FSFE for their help over the years.

The Bacula.org software that has been released will always remain Free Software, and it is not possible for anyone to change that fact. I have been writing and releasing free software and open source software since 1972, and as I have stated many times, I am and will remain a very strong supporter and creator of open source software, and future Bacula.org community software will always be open source.

My goal is to have the Bacula.org code covered by FLAs (or their equivalent) that are clear and consistent. In fact, due to significant FLA updating work I did last year and early this year with lots of help and understanding from the Bacula contributors (thank you), I believe that all known issues are already resolved and I continue to work FSFE.

If you have any questions or concerns, feel free to either post them to the bacula-users list if they are general or directly to me at kern (at) sibbald (dot) com if they are specific to you or you prefer to keep them private.

Best regards,
Kern

Bacula Mini-Status

On Monday 9 February, Bacula Systems SA and Bareos GmbH & Co KG have reached a settlement concerning the proceedings pending in Lausanne, Switzerland, pursuant to which parties have withdrawn their respective claims. The terms of their settlement agreement are confidential.

Bacula Status Report 30 August 2014

I would like to bring you up to date on the following items:

1. Bacula Release Status
2. Windows Binaries
3. Bacula Enterprise
4. Vacation

1. Bacula Release Status

As you probably are aware, the current version of Bacula is 7.0.5, which appears to be quite stable.  I have seen a few reports of seg faults in the SD, but as of the current time, I have no tracebacks or bug reports so there isn’t anything I can do until users submit something.

There are a few bug reports (relatively minor) that I will work on this month as well as two or three patches that were submitted too late for version 7.0.5.  In addition, I have spent a significant amount of time refactoring the Director backup and restore routines to make them easier to read and maintain, and I hope to release them mid-September.

Before the end of the year, I will make a pass through the Bacula Enterprise version and ensure that all bug fixes are back ported (I believe this is already the case, but better to double check) and that all enhancements possible will be back ported.

As you probably know, I have for some time been trying/planning to resume community binary builds of as many platforms as possible.  This has not been possible for a number of years due to reduced community participation (probably because Bacula is in most distros and they upgrade much more frequently than previously).  If I can pull it off, hopefully before the end of the year, it will be with the help of Bacula Systems.  Since they will be community binaries they will obviously be without charge.

2. Windows Binaries

The latest version of the Enterprise Windows binaries adapted for compatibility with the community version are now posted on the Bacula Systems web page:

http://www.baculasystems.com/windows-binaries-for-bacula-community-users

This version is numbered 7.0.5, but it actually contains code from a prerelease of Bacula Enterprise 8.0.0.  The new Windows binaries contain all bug fixes and enterprise enhancements that we have made to the Windows binaries until present, where I have recently spent a considerable amount of time. A few of the new features/enhancements are:

– All bug fixes such as: silent install, better .conf file security, correct verify file count, …

– Working IPv6

– Support for Windows mount points

– Experimental Windows Storage daemon (disk only)

As you know, these binaries are available from Bacula Systems at a very modest cost which is designed to simply cover the costs incurred by Bacula Systems in producing and distributing them.  If you have purchased these binaries in the past three months, any upgrade will be free of charge.

In addition, Bacula Systems has authorized me to distribute binaries to “my friends”.  Since “my friends” is a bit objective, I have decided to use this permission to give free Windows binaries to all Bacula community contributors that are listed in the AUTHORS file.  So if you name is in that file, simply send me (kern at sibbald dot com) an email with your name and the email address you will use for getting your binaries, and I will notify you how to do it (please allow for a bit of a delay).  If you feel that you have made some significant contribution to the Bacula project, and your name is not in the AUTHORS file, please contact me to correct this.  If you want free binaries and you have not contributed to the project, it is not too late.

3. Bacula Enterprise

The newest release of the Bacula Enterprise Edition was released on 31 August to specific customers.  It will have lots of new features, some of which are already in the community version, but others are entirely new and very significant.   Bacula Systems customers should already be aware of the new features.   Also, shortly the details will be announced on the Bacula Systems web site, until then, you can get information at:

http://www.baculasystems.com/contactus

A few years ago, I informed you that for several years I would be spending more time working with Bacula Systems, which meant less of my personal time for the community, but that in the end, the community would benefit.  I believe that what I said has come true, I spent less time with the community, but there were significantly more total contributions to the community from myself and Bacula Systems.  If you look at the new community feature list, hopefully you will see that this is true.

Now that those few years have passed, and Bacula Systems is well on its way, I have turned my daily management responsibilities over the Bacula Systems R&D manager, Eric Bollengier.  This means, as you may have noticed, that I am able to devote significantly more time to what I love doing — developing the Bacula community version.  This will continue with the help of Bacula Systems.

At the moment, I am spending most of my time improving the Windows version of Bacula, and with the recent work I did to produce the Windows Enterprise binaries for the community, all this work will be available to the community shortly after it is implemented.  Bottom line, you can look forward to additional Windows improvements over the next six months.

Community users can look forward to more advanced Enterprise features being backported into the community version as it always has done.  I expect that by the end of the year or shortly thereafter you will see some significant new community features.

Since Bacula Systems has more and more customers from Eastern Europe, if you are interested in working as a customer support engineer and you live and work in Eastern Europe, please see if this job description fits you.

http://www.baculasystems.com/company/careers

If you are an experienced C or C++ programmer, you might also consider applying.

4. Vacation

I have been invited to give a presentation of Bacula to the Latinoware conference in Iguazu, Brazil (15-17 October) http://2014.latinoware.org/?lang=en so I would be very pleased to see/meet as many of you there as possible.  If you live in South America, please see if it is possible for you to attend as I would enjoy meeting you there.

Since the trip from Switzerland, where I live to Iguazu takes something like 20 hours, I will prolong my trip to include a full vacation, and I will be able to visit a few other countries in South America. In total I will be gone from 30 September until 7 November.  During this time Eric Bollengier will ensure maintenance of the Bacula project.

 

So my message here is that the Bacula community version is destined to evolve significantly in the future.

Thank you for using Bacula.

Kern