Blog

Recent Topics

Bacula Status Report — 17 March 2017

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 […]

More

Bacula Release 7.4.7

16 March 2017

We are pleased to announce that we have just released Bacula version 7.4.7 to Source Forge and to the Bacula.org website. This version is a minor bug fix release that hopefully finally corrects the seg fault on OpenBSD due to the new ACL/XATTR code, and it also fixes most build problems on Solaris 10 as […]

More

Archives

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 Release 7.4.7

We are pleased to announce that we have just released Bacula version 7.4.7 to Source Forge and to the Bacula.org website.

This version is a minor bug fix release that hopefully finally corrects the seg fault on OpenBSD due to the new ACL/XATTR code, and it also fixes most build problems on Solaris 10 as well as EPROTO on OpenBSD.

There is one minor new feature that allows you to specify the query item number on the bconsole query command line.

If you are already running Bacula version 7.4.0 or greater, it is not urgent to upgrade unless you find a problem you are experiencing on the list of fixes (see ReleaseNotes below). There is no database update required from any prior 7.4.x version, but as usual all Storage Daemons must be updated to the same version as your Director (presumably 7.4.7).

As a reminder, the Windows File Daemon is available for download on the www.bacula.org web site for personal use. Since there are no updates to the Windows FD, version 7.4.7 does not exist. Consequently, please use the Windows FD version 7.4.4.

15Mar17
– Permit specifying query item number on bconsole query command line
– Fix Solaris 10 problems reported by Phil Stracchino
– Fix EPROTO on OpenBSD

Thank you for using Bacula.

Bacula Release 7.4.6

We are pleased to announce that we have just released Bacula version 7.4.6 to Source Forge and to the Bacula.org website.

This version is a minor bug fix release that fixes a number of bugs in the prior release as well as some long standing bugs.

If you are already running Bacula version 7.4.0 or greater, it is not urgent to upgrade unless you find a problem you are experiencing on the list of fixes (see ReleaseNotes below). There is no database update required from any prior 7.4.x version, but as usual all Storage Daemons must be updated to the same version as your Director (presumably 7.4.5).

As a reminder, the Windows File Daemon is available for download on the www.bacula.org web site for personal use. Since there are no updates to the Windows FD, version 7.4.6 does not exist. Consequently, please use the Windows FD version 7.4.4.

I have now found a replacement for WPDM (WordPress Download Manager), which suddenly stopped working, and the Windows binaries for 7.4.4 are loaded as well as the source for 7.4.6. In the next few days, I will also reload a few older Bacula versions.

Thank you for using Bacula.

===================================================

Release Notes for Bacula 7.4.6

Release Version 7.4.6

This is a bug fix release, which hopefully corrects a seg fault on OpenBSD due to the nex ACL/XATTR code, and it also fixes the large number of tape mount messages that are repeated at 5 minute intervals due to a bug in the poll code. Various small fixes for FreeBSD.

Please note, the signature hash files (.sig) for the source code was previously SHA1. For this and future releases we have changed it to be SHA256.

10Mar17
– Fix bug #2271 where poll interval causes tape mount message to repeat
– Attempt to fix IPV6 not configured
– Possible fix for acl seg fault on OpenBSD where no acl code defined
– Change release digest from SHA1 to SHA256
– Fix getnameinfo() for FreeBSD fixes bug #2083

Bugs fixed/closed since last release:
2083 2271

Release 7.4.5 to Source Forge

We are pleased to announce that we have just released Bacula version 7.4.5 to Source Forge.

This version is a minor bug fix release that includes a rewrite of the  ACL and XATTR code by Radoslaw Korzeniewski.  It also corrects the btape fill command to work properly (tape testing prior to use).

If you are already running Bacula version 7.4.0 or greater, it is not urgent to upgrade unless you find a problem you are experiencing on the list of fixes (see ReleaseNotes below). There is no database update required from any prior 7.4.x version, but as usual all Storage Daemons must be updated to the same version as your Director (presumably 7.4.5).

As a reminder, the Windows File Daemon is available for download on the www.bacula.org web site for personal use. Since there are no updates to the Windows FD, version 7.4.5 does not exist. Consequently, please use the Windows FD version 7.4.4.

You may feel that not much is happening with Bacula, but that is far from being the case.  Since last April, we have been working very hard to rewrite the Storage Daemon device drivers.  This work is not totally complete, but it has advanced to a stage where it can be released.  One benefit of it is that there is now in the Bacula Enterprise Edition a Cloud backup driver for S3 compatible clouds.  In addition, we have fixed a number of long standing subtle but annoying bugs in Bacula particularly in the Storage daemon.  Finally, we have added a number of other new features.

Beginning immediately, I (Kern) am working full-time to backport the very latest Bacula Enterprise code to the community version.  Hopefully this will be completed in the next couple of months, then within a short time (less than a year), I will backport the Cloud driver.

Unfortunately, there are currently no 7.4.5 source code packages in the download area on the bacula.org web site.  This is because the WPDM download manager plugin, which I paid for and have relied on, no longer works with the most recent version of WordPress, nor am I able to submit a support request.   I have never been satisfied with this package because the upload procedure is extremely manual and many of the features they promise never worked (e.g. tree style browsing of downloads).  As you can imagine, I am not very pleased with WPDM and would not recommend it.

Once I find a replacement for WPDM, I will upload the source code.  In the mean time, please go to the Bacula download area of Source Forge to get the latest version of the Bacula source code.

Thank you for using Bacula.

===================================================

Release Notes for Bacula 7.4.5

This is a minor bug fix plus a significant total rewrite of the
ACL and XATTR code by Radoslaw Korzeniewski.

07Feb17
– Correct wrong word in message
– Remove restriction on using the scratch pool that can
cause restore failures
– Remove debug code that breaks btape fill
– Initialize freespace_mutex fixes bug 2207
– baculum: Update AUTHORS file
– baculum: Enable Japanese language on web interface
– baculum: Implement Japanese language support
– XACL – refactoring an ACL and XATTR codes.
– Revert “Warn of Storage Daemon version incompatibility if
label fails. Bug #2193”
– Make another attempt to resolve bug #2176
– Apply patch to list more pool info
– Fix status alignment output reported by Wanderlei Huttel

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

Release 7.4.4

We are pleased to announce that we have just released Bacula version 7.4.4

This version is a minor bug fix release.

If you are a packager, I strongly advise you to take the 7.4.4 version since it corrects a number of problems related to packaging and installation. If you are already running Bacula version 7.4.0, it is not urgent to upgrade unless you find a problem you are experiencing on the list of fixes (see ReleaseNotes below). There is no database update required from any prior 7.4.x version, but as usual all Storage Daemons must be updated to the same version as your Director (presumably 7.4.4).

As a reminder, the Windows File Daemon is available for download on the www.bacula.org web site for personal use. Since there are no updates to the Windows FD, version 7.4.4 does not exist. Consequently, please use the Windows FD version 7.4.0.

Work is progressing on the next major version, which will have several major new features. It will probably be ready in the spring of 2017.

Thank you for using Bacula.

===================================================

Release Notes for Bacula 7.4.4

– Fix #2085 About director segfault in cram-md5 function
– Attempt to fix bug #2237
– Recompile configure.in
– Fix systemd installation
– If using readline reset terminal at bconsole exit
– Fix compilation without SMARTALLOC
– Fix #2060 about SQL false error message with “update volume fromallpools” command
– Fix spurious MD5 update errors when nothing changed should fix   bug #2237 and others
– Fix small memory leak with the restart command
– baculum: Update language files
– Fix #335 Avoid backups going to the scratch pool
– Minor modifications to Ubuntu packaging
– Check if the ScratchPool points to the current Pool and print a warning message in such case
– Fix #1968 print the ScratchPool name instead of just ‘Scratch’
– Display PrefixLinks in “show job” output
– Add explicit LL to big integers to appease older compilers
– Enable the plugin directory for the FileDaemon by default
– Allow multiple mailcommand+operatorcommand in Messages. Fixes bug #2222
– Handle NULL pointers in smartdump() and asciidump()
– Modify status to include Admin and Restore in Level field — clearer
– Ensure that zero JobMedias are written for labelling
– Fix error message about the stream 26 (PLUGIN_NAME) in bextract

Bugs fixed/closed since last release:
1968 2060 2085 2222 2237 335

Bacula Release 7.4.3

We are pleased to announce that we have just released Bacula version 7.4.3.

This is a bug fix release. Primarily to correct the GCC 6.0 bug (for more see below).

As a reminder, the Windows File Daemon is available for download on the www.bacula.org web site for personal use. Since there are no updates to the Windows FD, version 7.4.2 does not exist. Consequently, please use the Windows FD version 7.4.0.

Work is progressing on the next major version, which will have several major new features. It will probably take another couple of months to complete the work and ensure that it is stable. I will let you know as it progresses.

Thank you for using Bacula.

=====================================================================

Release Notes for Bacula 7.4.3

Release version 7.4.3

This is a bug fix release. Most importantly, it fixes 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 agressive optimization and it breaks a lot of programs including Bacula. This problem showed up on ArchLinux and Fedora 24.

17Jul16
– Add LICENSE and LICENSE-FOSS files to the documentation
– Add shortcut to RunScript console commands. Submitted by Wanderlei Huttel.
Fixes bug #2224
– Fail when multiple mailcommand and other strings are specified in .conf. Fixes
bug #2222
– Add support for terabytes in sizes. Submitted by Wanderlei Huttel. Fixes bug
#2223
– Add error message for truncate command when actiononpurge not set. Fixes bug
#2221
– Fix optimization error with GCC 6.1
– Fix compilation warnings with GCC 6.1
– Explicitly create MySQL user in grant_mysql_privileges.in

Bugs fixed/closed since last release:
2221 2222 2223 2224

New feature:
– There are two new Director directives that simplify doing
console commands rather than using RunScripts. They are
ConsoleRunBeforeJob = “console-command”
ConsoleRunAfterJob = “console-command”

Release 7.4.2

We are pleased to announce that we have just released Bacula version 7.4.2.

This version consists of mainly bug fixes. The most important fix is for
MySQL 5.7, which no longer is distributed with a libmysqlxx_r (thread-safe
or reentant) file. This caused Bacula linked for MySQL to fail at startup.

If you are a packager, I strongly advise you to take the 7.4.2 version since
it corrects a number of problems related to packaging and installation. If
you are already running Bacula version 7.4.0, it is not urgent to upgrade
unless you find a problem you are experiencing on the list of fixes (see
ReleaseNotes below). There is no database update required from 7.4.0 or
7.4.1, but as usual all Storage Daemons must be updated to the same version
as your Director (presumably 7.4.2).

As a reminder, the Windows File Daemon is available for download on the
www.bacula.org web site for personal use. Since there are no updates to the
Windows FD, version 7.4.2 does not exist. Consequently, please use the
Windows FD version 7.4.0.

Work is progressing on the next version, which will have several major new
features. It will probably take another couple of months to complete the
work and ensure that it is stable. I will let you know as it progresses.

Thank you for using Bacula.

=====================================================================

Release Notes for Bacula 7.4.2

Release version 7.4.2

This is an important bug fix release to version 7.4.1 mainly
fixes detection of MySQL 5.7 (as found in Ubuntu 16.04). Certain bug
fixes contributed by Bacula Systems.

06Jul16
– Fix #1926 about wrong duplicate job detection with Copy/Migration and
Backup jobs
– Recompile configure after db.m4 change
– Fix batch insert for MySQL 5.7
– Fix zero level debug output — now at 100
– Fix #766 about Job logs displayed with unneeded linefeed
– Fix #1902 about a segfault with the “cancel inactive” command
– Fix bug where MySQL 5.7 is improperly linked on Ubuntu 16.04

Bugs fixed/closed since last release:
1902 1926 766

Release 7.4.1

We are pleased to announce that we have just released Bacula version 7.4.1.

This version consists of mainly bug fixes, most of which are minor, but some are annoying. If you are a packager, I strongly advise you to take the 7.4.1 version as opposed to 7.4.0 since version 7.4.1 corrects a number of problems related to packaging and installation. If you are already running Bacula version 7.4.0, it is not urgent to upgrade unless you find a problem you are experiencing on the list of fixes (see ReleaseNotes below). There is no database update required from 7.4.0, but as usual all Storage Daemons must be updated to the same version as your Director (presumably 7.4.1).

As a reminder, the Windows File Daemon is available for download on the www.bacula.org web site for personal use. Since there are no updates to the Windows FD, version 7.4.1 does not exist. Consequently, please use the Windows FD version 7.4.0.

We had hoped to release the next major version of Bacula about now, but four points have come up:

1. I (Kern) took a long deserved lengthy vacation for several months beginning in February.

2. There is now a huge amount of fixes (some included in 7.4.1) and nice new features in Bacula Enterprise that need backporting to the community version. The Bacula Enterprise developers have really been busy.

3. We decided to implement backup to the cloud, and that is much more work than I had initially imagined. Now I have the architecture well defined and a nice test program that works very well so I am currently integrating parts of the test program into Bacula (the community version).

4. Before, during and after my vacation, there were a number of nice patches that were submitted that must be integrated into the code.

It will probably take another couple of months to complete the work and ensure that it is stable. I will let you know as it progresses.

Rather than wait for the next version, we are releasing this minor bug fix version.

Thank you for using Bacula.

=====================================================================

Release Notes for Bacula 7.4.1

Release version 7.4.1

Changes summary:
This is a minor bug fix release to version 7.4.0. Most of the
fixes have been kindly contributed by Bacula Systems SA.

1Jun16
– Fix bug #1849 MySQL does not accept 0 for DATETIME default
– Modify the alist object to be reused after a destroy()
– baculum: Fix setting invalid timezone value for PHP
– Fix compilation for AIX
– Fix the restore termination string in the job report to take in account
JobErrors and SDErrors
– baculum: Show jobs for client
– Fix bconsole “llist job=” output
– Fix #146 about update volume command line usage
– bat: Fix #1066 about bad update pool command
– Fix #1653 about make_catalog_backup default user name
– baculum: Show jobs stored on volume
– Fix update Volume=x Slot=nn when Slot > MaxVols
– Set exit code for create_postgresql_database.in
– Fix bug #2197 — build failure with –disable-libtool
– Fix bug #2204 — superfluous END-OF-DATA in update_mysql_tables.in
– Convert a Migration job with errors into a Copy job
– Remove exporting add_mtab_item — fixes bug #2198
– Fix possible problem of show multiple resources
– Comment out tools/smtp-orig.c as it is for reference only

Baculum – official rpm and deb package repositories

We have prepared the Baculum official packages and repositories for the following distributions:

– CentOS

– Fedora

– Debian

– Ubuntu

The repositories contain the latest version of Baculum (7.4.0-1) and they will be updated after each new version release.

Full installation instructions for the rpm and deb packages from the official repositories are available in the Bacula Console documentation chapter here:

http://www.bacula.org/7.4.x-manuals/en/console/Baculum_WebGUI_Tool.html

A baculum online demo is hosted here:

http://baculum.baculus.pl/

Login : admin

Password : admin

The demo environment is recreated from scratch each two hours.

 

Bacula Admin l & ll Training’s 2016

Bacula Admin l

The Bacula Admin l training helps new or existing administrators of Bacula (community or Enterprise Edition) acquire the knowledge they need to install, configure and operate the solution in a production environment, quickly and effectively.

After completing the course, you will be able to perform the following tasks:

  • Obtain the Bacula code
  • Build, install and configure Bacula on your own system
  • Design and run a backup scheme
  • Configure backup jobs for disks and auto-changers
  • Diagnose and debug problems
  • Learn to monitor day-to-day operations
  • Set up and perform restore operations

 

Schedule for 2016

Month Date Location
February 23-24-25 Kortenberg - Belgium
March 22-23-24 Paris La Défense - France
April 19-20-21 Yverdon-les-Bains - Switzerland
April 26-27-28 Kortenberg - Belgium
May 17-18-19 Kortenberg - Belgium
June 14-15-16 Paris La Défense - France
September 13-14-15 Yverdon-les-Bains - Switzerland
September 20-21-22 Rutherford - NJ - USA
September 20-21-22 Paris La Défense - France
December 6-7-8 Paris La Défense - France

Bacula Admin ll

The Bacula Admin ll training is the next natural step to acquire the highest level of expertise to design an Enterprise Backup and Recovery Solution, dealing with scalability, security, performance and other vital topics, critical in complex or dynamic environments.

After completing the course, you will be able to perform the following tasks:

  • Obtain the Bacula code
  • Plan an Enterprise Backup & Restore System
  • Manage scalability, security, and performance objectives
  • Implement an Enterprise Backup & Restore System with Bacula
  • Understand retention times
  • Manage configurations
  • Develop scripting within Bacula

 

Schedule for 2016

Month Date Location
June 14-15-16-17 Yverdon-les-Bains - Switzerland
October 11-12-13-14 Paris la Défense - France

For more information:

Belgium

Admin l: https://www.open-future.be/content/bacula-administrator-i-training-0

France

Admin l: http://www.teicee.com/informatique/sauvegarde-donnees/bacula-la-solution-open-source-de-sauvegarde-reseau/formation-administrateur-bacula.html

Admin ll: http://www.teicee.com/informatique/sauvegarde-donnees/bacula-la-solution-open-source-de-sauvegarde-reseau/formation-administrateur-ii-bacula.html

Switzerland and USA

Admin l: http://www.baculasystems.com/bacula-administrator-i-training-course

Admin ll: http://www.baculasystems.com/bacula-administrator-ii-training-course

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

Release 7.4.0

We have just released Bacula version 7.4.0.

This version consists of more backports from Bacula Enterprise 8.4 as well quite a few bug fixes (28) as a number of new features.  For your convenience, I have included selected parts of the ReleaseNotes below.

Upgrading should be easy since there is no database change and all older File Daemons should remain compatible with Bacula 7.4.0.

As with the last release, I would like to thank Bacula Systems for providing the bug fixes and new features. Since the development process in Bacula Systems is going faster (more programmers), we can expect even more features in future versions.

In addition to releasing the files to Source Forge as usual, I have added a new download area on the bacula,.org web site that will permit you to download all the files for the new version 7.4.0.

Bacula Systems has agreed to permit the personal use of the Bacula Enterprise Windows binaries, so I have included the Bacula Enteprise Windows binaries on the bacula.org web site (see Downloads -> Download Center on the main menu).  If you wish to use the Enterprise Windows binaries for other than personal use, please download them from: http://www.baculasystems.com/windows-binaries-for-bacula-community-users

Thank you for using Bacula.

=====================================================================

Release Notes for Bacula 7.4.0

Release version 7.4.0

For the most part the changes were contributed to the Bacula project by Bacula Systems SA.

This is a new release with a new version number. It has been very thourouly tested, but as always, the new features may not always work as expected.

The Catalog database format has not changed since version the prior release (7.2.0).

Compatibility:
————–
As always, both the Community Director and Storage daemon(s) must be upgraded at the same time. Any File daemon unning on the same machine as a Director or Storage daemon must be of the same version.

Older File Daemons should be compatible with the 7.4.0 Director and Storage daemons. There should be no need to pgrade older File Daemons.

New features and changes:
Please see the New Features chapter of the manual for documentation on the new features. The new features are currently only in the New Features chapter and have not et been integrated into the main chapters of the manual.

New Features and changes summary:
– Support for KFREEBSD OS
– Improved support for Clang
– Configure SSL connection to MySQL
– New chio-changer-freebase in examples/autochangers
– New directives in bacula-dir.conf in Catalog{} resource for the MySQL backend (not currently implemented for Postgresql or SQLite).
dbsslkey
dbsslcert
dbsslca
dbsslcapath
dbsslcipher
– examples/autochangers/rc-chio-changer removed
– examples/devices/DVD.conf removed
– updated copyrights
– Add “Expires in” to list and llist volumes
– Implement a more efficient Volume selection algorithm between DIR and SD
– Implement new list/llist command keywords:
order=asc|ascending
order=desc|decending
limit=nn
jobstatus=
Client=
JobErrors
– Implement new bconsole @tall command that outputs input and output to console and terminal. Note, this also outputs bconsole input commands.
– Implement MaxVirtualFullInterval
– Implement VirtualFullPool override
– Pool overrides work better
– Automatic selection of catalog from client where possible.
– Implement VerifyData level type for Verify jobs.

Bugs fixed/closed since last release:
1131 1360 1362 1368 1382 1412 1414 1449 1470 1524 1545 1548 1882 2083 2090 2103 2115 2117 2151 2153 2156 2165 2180 2182 2183 2192 804 898

Baculum 7.2.1-0 Release

We have released a new Baculum version – 7.2.1-0.

This release is focused on performance improvements. Despite the fact that it is a minor release, in this version we have included numerous features.

Source tar archive: http://bacula.org/downloads/baculum/baculum-7.2.1-0.tar.gz
Signature: http://bacula.org/downloads/baculum/baculum-7.2.1-0.tar.gz.sig
PGP public key: http://bacula.org/downloads/baculum/baculum.pub

Changes:
– Add run job again button
– Add session cache
– Search field works for all table cells
– Remember sort order for data grids
– Remove temporary Bvfs table when restore starts
– Add example Nginx config
– Add jobbytes and jobfiles columns in job list
– Split configuration windows into two tabs: actions and console
– Set default job attributes (level, client, fileset, pool, storage, priority) in Run job panel
– Do not refresh window lists if toolbar is open or elements are checked
– Fix working with php-fpm
– Fix sorting formatted values in tables
– Improve formatted size precision.
– Fix jobs count in job list
– Fix end-of-file warning in bconsole calls. Patch from Ulrich Leodolter
– Show jobid in job configuration window
– Get system timezone for PHP if possible
– Fix restore when a lot of jobids are given
– Show copy job label in job list
– Get job show result by job name or jobid
– Set half size window as default window size
– Does not save controls state in jobs window
– Fix showing table header
– Update SELinux policy module
– Fix update pool action when no volumes in pool
– Change default elements limit to 500 elements
– Add drive parameter to bconsole release command execution
– Fix expectation failed error during restore
– Switch to debug mode only when debug is enabled in config
– Fix remove users file during upgrade deb packages
– Fix default values in Makefile
– Change Makefile to using also for deb packages template
– Add deb template files and deb configs examples

In version 7.2.1-0 We prepared binary packages for: CentOS, Fedora, Ubuntu and Debian. Below you can find the installation descriptions for each of the distributions.

=== Fedora packages ===

1. Add Baculum repository:

# dnf config-manager –add-repo http://download.opensuse.org/repositories/home:/ganiuszka/Fedora_23/home:ganiuszka.repo

2. Install base Baculum package

# dnf install baculum

3. If SELinux enabled then it is required additional baculum-selinux package:

# dnf install baculum-selinux

4. Install Baculum web server configuration and Baculum start

a) For Apache web server

# dnf install baculum-httpd
# service httpd restart

b) For Lighttpd web server

# dnf install baculum-lighttpd
# service baculum-lighttpd start

5. In web browser go to: http://localhost:9095

First time login: admin
First time password: admin

NOTE!
If bconsole is accessible to Baculum via sudo then your are required to create a file:

# vi /etc/sudoers.d/baculum

add the following content to the file:

a) For Apache web server:

Defaults:apache !requiretty
apache ALL= NOPASSWD: /usr/sbin/bconsole

b) For Lighttpd web server

Defaults:lighttpd !requiretty
lighttpd ALL= NOPASSWD: /usr/sbin/bconsole
=== CentOS packages ===

1. Add Baculum repository:

# yum-config-manager –add-repo http://download.opensuse.org/repositories/home:/ganiuszka/CentOS_7/home:ganiuszka.repo

2. Install base Baculum package

# yum install baculum

3. If SELinux enabled then is required additional baculum-selinux package:

# yum install baculum-selinux

4. Install Baculum web server configuration and Baculum start

a) For Apache web server

# yum install baculum-httpd
# service httpd restart

b) For Lighttpd web server

Because Lighttpd binary packages default does not exist in CentOS repository, you are required to install epel repository with the following command:

# yum install epel-release

and then install Lighttpd configuration for Baculum:

# yum install baculum-lighttpd
# service baculum-lighttpd start

5. In web browser go to: http://localhost:9095

First time login: admin
First time password: admin

NOTE!
If bconsole is accessible to Baculum via sudo then you are required to create a file:

# vi /etc/sudoers.d/baculum

and add the following content to the file:

a) For Apache web server:

Defaults:apache !requiretty
apache ALL= NOPASSWD: /usr/sbin/bconsole

b) For Lighttpd web server

Defaults:lighttpd !requiretty
lighttpd ALL= NOPASSWD: /usr/sbin/bconsole
=== Ubuntu packages ===

1. Add Baculum PPA repository:

# add-apt-repository ppa:ganiuszka/baculum

2. Update packages index

# apt-get update

3. Install base Baculum package

# apt-get install baculum

4. Install Baculum web server configuration end Baculum start

a) For Apache web server:

# apt-get install baculum-apache2

Enable mod_rewrite module in Apache

# ln -s /etc/apache2/mods-available/rewrite.load /etc/apache2/mods-enabled/rewrite.load

Enable Baculum configuration in Apache

# ln -s /etc/apache2/sites-available/baculum.conf /etc/apache2/sites-enabled/baculum.conf

Start Baculum

# service apache2 restart

b) For Lighttpd web server:

# apt-get install baculum-lighttpd
# service baculum-lighttpd start

5. In web browser go to: http://localhost:9095

First time login: admin
First time password: admin

NOTE!
If bconsole is accessible to Baculum via sudo then you are required to create a file:

# vi /etc/sudoers.d/baculum
and add the following content to the file:

Defaults:www-data !requiretty
www-data ALL= NOPASSWD: /usr/sbin/bconsole

The above sudo configuration is common for both Apache and Lighttpd web servers.

=== Debian packages ===

For Baculum 7.2.1-0 in Debian there does not exist any special packages repository, the recommended method to install Baculum packages is to download packages for Ubuntu Vivid manually and then to install them.

1. Download base Baculum package and install it

# wget https://launchpad.net/~ganiuszka/+archive/ubuntu/baculum/+files/baculum_7.2.1-0ppa1~vivid1_all.deb
# gdebi baculum_7.2.1-0ppa1~vivid1_all.deb

2. Download and install web server configuration for Baculum.

a) For Apache web server

# wget https://launchpad.net/~ganiuszka/+archive/ubuntu/baculum/+files/baculum-apache2_7.2.1-0ppa1~vivid1_all.deb
# gdebi baculum-apache2_7.2.1-0ppa1~vivid1_all.deb

Enable mod_rewrite module in Apache

# ln -s /etc/apache2/mods-available/rewrite.load /etc/apache2/mods-enabled/rewrite.load

Enable Baculum configuration in Apache

# ln -s /etc/apache2/sites-available/baculum.conf /etc/apache2/sites-enabled/baculum.conf

Start Baculum

# service apache2 restart

b) For Lighttpd web server

# wget https://launchpad.net/~ganiuszka/+archive/ubuntu/baculum/+files/baculum-lighttpd_7.2.1-0ppa1~vivid1_all.deb
# gdebi baculum-lighttpd_7.2.1-0ppa1~vivid1_all.deb

3. In web browser go to: http://localhost:9095

First time login: admin
First time password: admin

NOTE!
If bconsole is accessible to Baculum via sudo then you are required to create a file:

# vi /etc/sudoers.d/baculum

and add the following content to the file:

Defaults:www-data !requiretty
www-data ALL= NOPASSWD: /usr/sbin/bconsole

The above sudo configuration is common for both Apache and Lighttpd web servers.

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

Release 7.2.0

We have just released Bacula version 7.2.0.

This version has quite a number of difficult and important bug fixes
since version 7.0.5 as well as a good number of new features.

Some of the new features are:

– Job Edit Codes %E  number of non-fatal error messages and %R bytes read from the disk.

– Enable/Disable of Clients, Schedules and Storage devices.

– Snapshot Management

– Snapshot Backends

– Improvements to Status Storage

– New option M for accurate jobs (compare Modification time of a file)

– Read Only Disk storage

– Restarting of Incomplete or Failed jobs (Restart, Resume, and Stop commands)

– Truncate command for truncating volumes

– Prune Expired Volumes

– Job edit codes %P for process id and %C for cloned jobs

– Maximum Concurrent Read Jobs (directive)

– Job Bandwidth Limitations

– Always Backup a File in Accurate mode

– Set Accurate mode at Runtime

– Purge Migration Job

This version has not been tested in production yet, so please test it
carefully. That said, it is largely based on Bacula Enterprise version
8.2, which is extremely stable and it also has a number of fixes and
features from the next, yet unreleased, Enterprise version as well as
*all* the Enterprise bug fixes.

For certain of the new features, and a couple more yet to come, this
version has a new catalog layout, which means that you must do a catalog
upgrade (it is relatively simple). As always, please backup your
database prior to applying the upgrade procedure.

Previously we supplied an update script for only one version. To avoid
the proliferation of upgrade scripts in the future, we have settled on a
single script (update_bacula_tables), which will upgrade from version
3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format. So
the procedure much simpler.
As soon as we can update the bacula.org web site to have a sort of more
automated download area, we will move our source release to the
bacula.org web site and begin furnishing binaries.

Many thanks to Bacula Systems for providing the bug fixes and new
features. Since the development process in Bacula Systems is going
faster (more programmers), we can expect even more features in future
versions.

You may notice a few license/copyright changes, but these are all very
positive for the community version and its future. I will go into it in
more detail on this point in a Status Report that will follow this
announcement in a few days.

Thanks for using Bacula.

Baculum – Current and upcoming features

1. Baculum Ubuntu/Debian packages

Preparing Baculum to use from bacula-gui source archive requires going
through a few steps as manual web server configuration, PHP installation
with dependencies, setting up authentication to Baculum. These actions
may need a few attempts and may take a little time.

For this reason, we have prepared Baculum binary packages for
Ubuntu/Debian distributions. Packages are available in Lauchpad.net
service here:

https://launchpad.net/~ganiuszka/+archive/ubuntu/baculum

Please note that it is an unofficial repository nevertheless the repository
is maintained by Baculum author.

2. Baculum online demo version

You will find the Baculum online demo version available here:

http://baculum.baculus.pl

login: admin, password: admin

The running version of the demo is based on a git snapshot that comes from the Bacula GUI repository and is rebuilt on a hourly basis (database, volumes, etc.)

3. Upcoming features

Within almost one year, a lot of new features have been introduced into Baculum (available from Bacula GUI repository)

Here below are listed the major changes:

– Stability and performance improvements
– Jobs graphs
– Running jobs are refreshed in real time
– Verify Jobs support
– Execute action on multiple volumes (prune, purge, delete) and jobs (delete) at a time
– Polish translation
– Enabled support to run Baculum in web server document root sub-directory

vchanger release 1.0.0 is out

Vchanger implements the Bacula Autochanger Interface to provide a virtual disk autochanger targeting the use of removable disk drives, such as USB external drives and RDX cartridge systems, as storage media. As compared to Bacula’s native virtual disk autochanger, vchanger has the following advantages:

– May simultaneously use volume files on an unlimited number of different filesystems, any of which may be simultaneously mounted.
– Simultaneously mounted storage space can be easily scaled by adding additional filesystems, requiring no change in Bacula’s configuration
– All volumes on all filesystems have the same Media Type and can be moved between filesystems arbitrarily with no need for updating volume information in the catalog and requiring no configuration changes.
– Filesystems can be specified by UUID, allowing any type of automounting to be used and filesystems to be mounted at arbitrary paths
– All filesystems needed for a restore can be mounted simultaneously, eliminating the need for operator intervention when volumes needed for a restore are spread across multiple filesystems.

Additional features include:

– Udev rule generator and scripts provided to implement automounting via udev
– Automatically issues an ‘update slots’ command via bconsole when needed
– Automatically issues a ‘label barcodes’ command when new volume files are created
– Allows plug-n-play attachment and detachment of removable drives
– Extended command LISTMAGS allows listing assigned filesystems and their status
– Extended command CREATEVOLS allows adding and automatically labeling volume files at any time

Source code, documentation, and RPM packages for RHEL/Centos 6 and 7 are available from SourceForge at http://sourceforge.net/projects/vchanger/files/?source=navbar.

A vchanger HowTo is available at http://sourceforge.net/projects/vchanger/files/vchangerHowto.html/download.


 

Release Notes for vchanger 1.0.0 2015-04-14

Release 1.0.0

This is a major release adding several features and a change in the
structure of magazines and the way volume files are “loaded” into
virtual drives. These changes allow for an unlimited and variable
number of volume files on each magazine, and allow adding and deleting
volumes to/from magazines, as well as moving volume files from one
magazine to another. Virtual drives are now symlinks dynamically
created by the LOAD command. An unlimited number of virtual drives per
autochanger is supported without requiring a vchanger configuration
change. The number of virtual drives used is determined solely by the
Device resources defined in bacula-sd.conf.

Also, vchanger will now automatically issue ‘update slots’ and
‘label barcodes’ commands to Bacula via bconsole when it detects a
change in the availability of any of its defined magazines or when
volume files are created with the CREATEVOLS command. Together with
an automounting mechanism, this makes the attachment and detachment
of removable drives a plug-n-play operation.

To aid in using removable drives on systems having udev, vchanger now
includes a udev rules generator and helper scripts to enable the
automatic mounting of magazine filesystems triggered by udev hotplug
events. The advantage to using this automounting method, as opposed to
autofs or window manager automounters using dbus, etc., is that these
scripts will invoke vchanger with a new REFRESH command that will issue
an ‘update slots’ command via bconsole whenever removable drives
are attached or detached.

Change Summary:

The concept of a ‘magazine’ has changed. A magazine remains a
directory, usually the mountpoint of a filesystem, however no metadata
files are now stored on the magazines and volume files are not renamed
when loading and unloading virtual drives. There is now no requirement
that all magazines have the same number of volumes, and volume files
may have any filename. New volume files can be created on a magazine
at any time. A new extended interface command, CREATEVOLS, has been
implemented for this purpose. A magazine is now simply a filesystem
(or directory) containing some variable number of volume files. Any
directory containing volume files can be used as a magazine in
vchanger, including for example volumes created using Bacula’s
built-in disk storage handling. Volume files may be deleted from
magazines or moved between magazines. The only caveat is that the
volume’s Media Type must match that of the autochanger’s Storage
resource.

Virtual drives are now simply a symlink in the autochanger’s work
directory. The drive number is the name of the symlink. For example,
if the autochanger’s work directory is /var/spool/vchanger/changer1,
then virtual drive 0 is a symlink at the path
/var/spool/vchanger/changer1/0. The symlink’s path is then specified as
the Archive Device in the Device resource defined in bacula-sd.conf for
the autochanger’s drive 0. Vchanger implements the LOAD command by
creating this symlink pointing at the volume file mapped to the slot
requested to be loaded. A subsequent UNLOAD command deletes the
symlink. In previous versions, a LOAD created a symlink pointing to the
mountpoint of the magazine and then renamed the volume file on the
magazine to ‘drive0’, ‘drive1’, etc. This was because the original
design criteria, (dating to before the release of Bacula 2.0.0),
required that vchanger run on Windows Server 2003, which did not have
the capability of file-level symlinks. However, file-level symlinks is
a much more robust method, handling any “out of space” conditions in a
clean, expected way. For that reason, use of vchanger on versions of
Windows without file-level symlinks is no longer supported.

An autochanger’s magazines are assigned in its vchanger configuration
file. An unlimited number of magazines is supported and the storage space used
by an autochanger can be scaled at any time by simply adding additional
magazines and creating volume files on them. Expansion of the storage
space does not require any change to Bacula’s configuration. Any
combination of one or more of the assigned magazines can be attached
(mounted) at any time.

When a magazine is attached or detached there is of course a change in
which volumes are available for reading and writing. Bacula must be
instructed to update its database to reflect the change. This is
analogous to swapping tapes in a tape autochanger library. Bacula has a
bconsole command used for this purpose, the ‘update slots’ command. In
general, one would insert or remove tapes and then issue an ‘update slots’
command in bconsole to inform Bacula of the change. With vchanger,
attaching or detaching a magazine also requires that the ‘update slots’
command be issued, however vchanger now detects changes to the currently
available volume files and automatically issues the ‘update slots’
command when needed. This allows swapping magazines to be a true
plug-n-play operation.

The scripts directory in the vchanger source tree contains a script to
generate the udev rules needed to automatically mount the magazines
filesystems defined in the vchanger configuration file. These rules will
cause udev to launch scripts, also included in the scripts directory, to
handle a “hot add” event by mounting the magazine filesystem and invoking
vchanger with the REFRESH command to issue an ‘update slots’ command to
Bacula. Likewise, a “hot delete” event will launch a script to unmount
the filesystem and again invoke vchanger with the REFRESH command.

If vchanger is compiled on a system supporting udev, then libudev will be
used to determine the device node of magazine partitions specified by
UUID. If compiled on a system without udev, the older method of using
libblkid and libuuid will be used if available. For Windows builds,
win32 API functions are used to map filesystem UUID to device node. If
the getmntent() function is not available on the target system for
determining a filesystem’s mountpoint, then vchanger will use the
getfsstat() function, allowing magazines to be specified by UUID on many
BSD and OSX systems. A build for a minimal system having neither libudev
nor libblkid will succeed, however specifying magazines by UUID will not
function and result in an error, meaning that such minimal systems must
only specify magazines by directory path. These changes should alleviate
many of the problems people have had in the past building vchanger for
non-Linux systems.

Bugs Fixed:
5 Compile errors on Debian or Ubuntu
6 Broken libblkid returns wrong device for UUID
7 Limitation on number of virtual drives
8 Compile errors under Solaris 10

 

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

Baculum Overview

Baculum is a Bacula web based interface, which enables several Bacula administration functions.
These include:
  •  Running Bacula jobs (backup, restore, verify…)
  •  Monitor Bacula services
  •  Bacula console available via web interface
  •  Support for customised and restricted consoles (Console ACL functionality)
  •  Multiple Directors support
  •  Volumes management including labeling new volumes
  •  User friendly graphs Basic storage daemon operations on volumes (mount, unmount, release actions)
  •  Easy in use configuration and restore wizards
  •  Many other features…
Baculum general operating system environment requirements

The Baculum installation should have the following components:

  • Web Server – with mod_rewrite module loaded. Baculum has been tested on Apache HTTP Server and Lighttpd.
  • PHP 5.3 or higher – as web server module or as FastCGI, with the following modules installed:

* PDO PHP support – depending on your catalog database: PDO PostgreSQL, PDO MySQL or PDO SQLite.
Note: If Bacula uses MySQL catalog backend, Baculum requires to install MySQL php native drivers. (often called php-msqlnd, and not php-msql)
* BCMath PHP module.
* cURL PHP module.
* MB String PHP module.
* JSON PHP module.

  • Bconsole – configured Bacula text based console
  • Access to Bacula catalog database – A computer with a Baculum installation should be able to connect to the Bacula catalog database

There is no need to install Baculum on the server with a Bacula Catalog database because Baculum can communicate with the Bacula database located on a remote server.

Above requirements are validated during Baculum’s initial startup. You will be informed if any components are missing in the installation environment.

Installation

Detailed information about manual installation of Baculum is available in the Baculum INSTALL file located in bacula-gui tar archive.

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 Admin I & II Trainings in 2015

The ever-growing program of certified Bacula Training courses kicks off in January with Open-Future presenting the official “Bacula Admin I” training next week in Belgium, 13-15th January 2015.
This is followed by téïcée‘s “Bacula Admin II” training in France, 20-23rd January 2015.

Here are more details on the certified Bacula Admin I & II classes and 2015’s schedule:

Bacula Admin I

The Bacula Admin I training helps new or existing administrators of Bacula (community or Enterprise Edition) acquire the knowledge they need to install, configure and operate the solution in a production environment, quickly and effectively.

After completing the course, you will be able to perform the following tasks:

– Obtain the Bacula code (version 7.0)
– Build, install and configure Bacula on your own system
– Design and run a backup scheme
– Configure backup jobs for disks and auto-changers
– Diagnose and debug problems
– Learn to monitor day-to-day operations
– Set up and perform restore operations

2015’s Bacula Admin I schedule

Admin_I

Bacula Admin II

The Bacula Admin II training is the natural next step to acquire the highest level of expertise to design an Enterprise Backup and Recovery Solution, dealing with scalability, security, performance and other vital topics, critical in complex or dynamic environments.

After completing the course, you will be able to perform the following tasks:

– Obtain the Bacula code
– Plan an Enterprise Backup & Restore System
– Manage scalability, security and performance objectives
– Implement an Enterprise Backup & Restore System with Bacula
– Understand retention times
– Manage configurations
– Develop scripting within Bacula

2015’s Bacula Admin II schedule

Admin_II

For more information:

Belgium
Admin I: https://www.open-future.be/bacula-administrator-i-training-13th-till-15th-january

France
Admin I: http://www.teicee.com/informatique/sauvegarde-donnees/bacula-la-solution-open-source-de-sauvegarde-reseau/formation-administrateur-bacula.html
Admin II: http://www.teicee.com/informatique/sauvegarde-donnees/bacula-la-solution-open-source-de-sauvegarde-reseau/formation-administrateur-ii-bacula.html

Switzerland and USA
Admin I: http://www.baculasystems.com/bacula-administrator-i-training-course
Admin II:  http://www.baculasystems.com/bacula-administrator-ii-training-course

Thank you

Kern Sibbald, speaker at Latinoware 2014

LatinoWare2014

Today on 15th of October, Kern Sibbald will be speaking at Latinoware in Foz do Iguaçu, Brasil.

Latinoware 2014 is a Latin American Open Source Software Conference which takes place 15-17th October 2014.

More than 4300 people, including students, professionals and specialists from the area, are expected for the eleventh edition of the event.

Promoted by Itaipu Binacional, Foundation Itaipu Technological Park – Brazil, The State of Paraná Informatics Company (CELEPAR) and the Federal Data Processing Service (SERPRO), Latinoware is an event that opens up space for discussion and reflection on the deployment of open source software in Latin America, in addition to promoting the integration and valuing for Latin America.

As in previous editions, Latinoware is expected to break the audience record and, once again, be the stage for a number of international celebrities and representatives from public and private agencies of different countries of Latin America to present their solutions in Open Source Software.

To this end, the Latinoware 2014 program will include lectures, roundtables and workshops around themes linked to information and communication technologies, supported by open source software systems developed in the continent.

Kern Sibbald Wins 2014 CH Open Source Award

 

2014_CH_Open_Source_Awards

Kern Sibbald Wins the 2014 CH Open Source Award

Leading prize “Champions in Open Source” awarded to Kern Sibbald for his achievements with Bacula, Bacula Systems and Open Source

October 10, 2014, Yverdon les Bains, Switzerland: – Bacula Systems’ CTO and Chairman, Dr. Kern Sibbald has won the 2014 CH Open Source award for his long-term achievements with Bacula, Bacula Systems and Open Source. On Wednesday evening, October 8, 2014 the OSS Awards 2014 were presented as part of the Open Source Business Forum in Berne. This conference brought together computer science experts from the likes of Deutsche Telekom, Swiss Re, Swisscom, green.ch, Visana, Rieter and other companies discussing how best to use Open Source software in a professional environment. Dr. Sibbald was recognized for his outstanding contributions to open source, including that of founding Bacula Systems. “Receiving this award is exciting” said Dr. Sibbald. “I am particularly happy to know people and companies around the world protect their data with Bacula.”

“This award to Kern is further industry affirmation of what our customers have been telling us for years,” said Frank Barker, CEO of Bacula Systems. “Kern’s contribution to Bacula Systems has essentially enabled some of the world’s most demanding technical IT environments to deploy cutting edge backup and restore technology, while escaping proprietary solutions and their high costs. This has always been the promise of open source, and this is what Bacula Systems successfully delivers.”

Companies around the world rely on open source technology to enable and enhance their business operations and deliver on their business strategies. The CH Open Source Awards recognize the best companies, public entities, open source communities and individuals who have acted boldly and with innovation by developing or using open source software in a variety of ways. Additional information on the 2014 CH Open Source Award winners can be found at on the www.opensource.ch website.

Kern_Sibbald

The prize ceremony can be viewed here:

Social Media Content

Find out what’s new at Bacula Systems and join the conversation on Facebook, LinkedIn, Twitter and the Bacula Systems blog

Training Session Admin I 28th, 29th and 30th of October 2014

Please be informed that Bacula Systems is organizing its next Admin I training session 28th, 29th and 30th of October, in Yverdon-les-Bains, Switzerland.

The Administrator I Training Course is designed to help new or existing administrators of Bacula acquire the knowledge they need to install, configure and operate the solution in a production environment quickly and effectively.

This high-quality training course is held under the personal guidance of Kern Sibbald, leader of the Bacula Project. After completing the course, you will be able to perform the following tasks:

  •     Obtain the Bacula code (version 7.0)
  •     Build, install and configure Bacula on your own system
  •     Design and run a backup scheme
  •     Configure backup jobs for disks and auto-changers
  •     Diagnose and debug problems
  •     Learn to monitor day-to-day operations
  •     Set up and perform restore operations

All Bacula community users are eligible for a discount!

For more information, please visit: http://www.baculasystems.com/bacula-administrator-i-training-course
To register, please visit: http://www.baculasystems.com/contactus

Thank you

Why Forking is Bad

I have always felt that forking an open source project is mostly a waste of energy because for the most part you get 1, 1 rather than 1+1, in other words the synergy of working together is lost by forking. Secondly forking divides the community.  Today, there are a lot of advocates of forking, and on the side of forking, I have even written a blog on why not all forks are bad:

http://blog.bacula.org/all-project-forks-are-not-bad/

On the side of forks are bad, it is important to understand what experts such as Eric S Raymond have to say about it.  I quote:

The three taboos we observed above make perfect sense under this analysis. One’s reputation can suffer unfairly if someone else misappropriates or mangles one’s work; these taboos (and related customs) attempt to prevent this from happening. (Or, to put it more pragmatically, hackers generally refrain from forking or rogue-patching others’ projects in order to be able to deny legitimacy to the same behavior practiced against themselves.)

  • Forking projects is bad because it exposes pre-fork contributors to a reputation risk they can only control by being active in both child projects simultaneously after the fork. (This would generally be too confusing or difficult to be practical.)
  • Distributing rogue patches (or, much worse, rogue binaries) exposes the owners to an unfair reputation risk. Even if the official code is perfect, the owners will catch flak from bugs in the patches (but see [RP]).
  • Surreptitiously filing someone’s name off a project is, in cultural context, one of the ultimate crimes. Doing this steals the victim’s gift to be presented as the thief’s own.

Of course, forking a project or distributing rogue patches for it also directly attacks the reputation of the original developer’s group. If I fork or rogue-patch your project, I am saying: “you made a wrong decision by failing to take the project where I am taking it”; and anyone who uses my forked variation is endorsing this challenge. But this in itself would be a fair challenge, albeit extreme; it’s the sharpest end of peer review. It’s therefore not sufficient in itself to account for the taboos, though it doubtless contributes force to them.

The full  quote can be found in following section:

http://catb.org/~esr/writings/homesteading/homesteading/ar01s09.html

and the full text of “Homesteading the Noosphere”, by Eric Steven Raymond is at:

http://catb.org/~esr/writings/homesteading/homesteading/index.htm

As project manager of the Bacula open source backup and restore program, I have experience with two open source forks and at least one closed source fork.  All three were made by former Bacula developers.  The first open source fork was Burp and is what I call a friendly non-commercial fork and was the subject of the first blog I cite above.  The second fork was Bareos. The Bareos fork was created by the four directors of DassIT, which is a commercial company and one former Bacula developer.

The third closed source fork is where a former Bacula developer created a backup appliance based on Bacula and the web site now stated that the code is proprietary.  This fork will be the subject of another blog one day and is not really in the category of open source forks that I am discussing here.

What Eric Raymond exposes in his article is that reputation in an open source project is more important than one would imagine.

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

Release 7.0.5

This is a bug fix release to version 7.0.4.   Since it fixes several
major problems, we recommend that everyone upgrade to this version.

As usual, the source code has been uploaded to the Bacula project of Source Forge.

         http://sourceforge.net/projects/bacula

28Jul14
– Fix #547 by adding .schedule command
– Update AUTHORS
– Fix bug #2079 with patch from Robert Oschwald
– Fix orphaned file descriptors during errors
– Yet another client==NULL
– Improve FD and SD cancel
– Jim Raney’s TLS patch
– Fix bug #1679 pool overrides not shown in manual run display
– Attempt to avoid client==NULL
– Fix for bug #2082 (hopefully)
– Fix seg fault in jobq.c
– make stop after first error
– Increase status schedule days from 500 to 3000
– Remove bad cherry-pick
– Fix compiler warning
– Allow options create_postgresql_database from patch in bug #2075 by roos
– Fix bug #2074 crashes when no conf file present
– Set pthread id in jcr at beginning so the job can be cancelled.
– Fix possible heartbeat interval timing problems
– Fix some errors reported by valgrind. May fix the problem with bsmtp command.
– Ensure b_sterror() is using the correct size of input buffer
– Fix possible seg fault
– Fix segfault when trying to stop the bnet_server thread in terminate_stored()
– Fix bad link bug #2076
– Fix compilation of bsock.c when TLS is not available
– Correct L suffix to be LL
– Fix bad copy/migrate data header
– On termination shutdown thread server
– baculum: Updated README file
– baculum: Update English language texts
– baculum: Saving auth file for web server HTTP Basic auth
– baculum: Added directory for web server logs
– baculum: Added example Lighttpd configuration for Baculum and sample web
server auth file
– Expanded auth error message
– baculum: Support for web servers which do not provide direct info about HTTP
Basic auth
– Fix limit bandwidth calculation
– Eliminate strcpy() from bsmtp
– Fix for configuring sudo option for bconsole access
– Display correct NextPool overrides + use Job NextPool in restore if available
– Fix Bacula to work with newer Windows pthreads library
– Fix bug #180 ERR=success in btape when tape error

Bugs fixed/closed since last release:
1679 180 2074 2075 2076 2079 2082 547

All Project Forks Are Not Bad

In general, I believe that project forks are not good. I wouldn’t really say that forks are bad, but they do tend to duplicate effort and split the community. They certainly are justified if the particular project is stalled or is not willing to meet the needs of a community or if the new project has a different goal.

In 2011, there was a fork of Bacula started by Graham Keeling, called Burp (burp.grke.org).  In the past, Graham had contributed some interesting features  to Bacula.  What is clear is that Graham and his fork are not at all hostile towards the Bacula project, in fact it is just the opposite.  Graham does have different ideas of backup or different goals, which are nicely explained on his site.

I have been aware of this fork since its inception, and when looking at the source code, I noticed a few minor problems with the copyrights, but decided that it was not significant enough to mention.

However, recently Graham asked a question on the Bacula web, and I did my best to respond to it.  In my response, I mentioned that I found a few issues with his fork.  Graham immediately contacted me, and off-list, I explained that I felt that few of the file headers should really include the Bacula FSFE copyright.  The next day, Graham posted a commit that in my view fixed all the problems and in exactly the right way.

I must say that this surprised me in a very positive way, because I just mentioned the problem and Graham fixed it.

I asked Graham if Bacula and Bacula Systems could include some of his code in the bacula.org and Bacula Enterprise versions, and Graham,  stated that any of the burp code can be used in bacula.org (they are licensed the same) and anything that goes into bacula.org can also be used in Bacula Enterprise — the mark of a real gentleman.

Conclusion: Burp is a fork of Bacula that has implemented something different and both projects can benefit from the other.

Release 7.0.4

This is a bug fix release to version 7.0.3.  We recommend that
everyone upgrade to this version.

As usual, the source code has been uploaded to the Bacula project of Source Forge.

         http://sourceforge.net/projects/bacula

The main fixes are to make copy/migration to a second SD work, and
to cleanup some of the inconsistencies in the cancel command which
could confuse the user.

02Jun14
– Better error handling for cancel command
– Fix compiler warning + simplify some #ifdefs
– Fix copy/migration to second SD
– Fix calls to sl.set_string()
– Improve sellist code

Release 7.0.3

This is a bug fix release to version 7.0.2. We recommend that everyone using version 7.0.2 upgrade to this version.  As usual, the source code has been uploaded to the Bacula project of Source Forge.

http://sourceforge.net/projects/bacula

Major points:
There are a number of bug fixes, some of them very important. In addition we have worked on improving error handling for the new selection lists (used in cancel) as there are a few serious problems reported, but we are unable to reproduce them. Hopefully the changes have corrected these problems.

12May14
– Fix error handling in do_alist_prompt
– Tighten error condition handling in sellist
– Add new cancel test
– Update LICENSE and LICENSE-FAQ
– Also update autoconf/aclocal.m4
– Reschedule on error caused EndTime to be incorrect — fixes bug #2029
– Flush console queued job messages — should fix bug #2054
– Attempt to fix FreeBSD echo/printf, bug #2048
– Update to newer libtool + config.guess
– Recompile configure
– Apply fix supplied for acl.c in bug #2050
– Fix a SD seg fault that occurs with over committed drives
– Clear bvfs cache and set debug options available only for admin
– Moved auth params to curl opts
– Filtred single results for restricted consoles
– Removed unnecessary debug
– Changed e-mail address in gettext file
– Support for customized and restricted consoles
– Misc changes for rpm building (made by Louis)
– Updated requirements for Baculum
– Apply fix for bug 2049: wrong drive selected
– Fix #2047 about bthread_cond_wait_p not declared
– Fix Bacula bug #2044 — fix Makefile for bplugininfo linking
– Fix Bacula bug #2046 — sellist limited to 10000
– Fix Bacula bug #2045 — multiply defined daemon_event
– Fix Bacula bug #2020 overflow in btape — Andreas Koch

Bugs fixed/closed since last release:
2020 2029 2044 2045 2046 2047 2048 2050 2054

Release 7.0.2

We have released Bacula version 7.0.2 to Source Forge.

This is a minor bug fix since version 7.0.1, but it does have one significant bug fix.   If you use shell expansion characters in any of your configuration files, we recommend that you download and install this version.  Otherwise if you have already installed version 7.0.0 or 7.0.1 and experiencing no problems, there is no need to upgrade.

For packagers this version has a number of cleanups of old files, and corrects a few problems of building the documentation from scratch. Please note that the release documentation contains prebuilt English pdf and html files.

Thank you for using Bacula 🙂

Release 7.0.0

We have released version 7.0.0 to Source Forge.

Please be aware that this is a major new version and thus please test it carefully before putting it into production. Since there are so many changes (mostly backports from the Enterprise version), I expect to have a few problems even though we have done very heavy testing. Note, this code has a very large number of bug fixes.

Please note that we have done a good deal of cleanup so many of the old, unused directories such as gnome-console, tray-monitor, wx-console, and win32 are removed from the bacula directory. In addition, we have removed everything from the gui directory as it contained only old programs that were no longer maintained. There is one new addition to the gui directory, which is the new baculum web gui program. In addition, a number of directories have been removed from the docs release (but not yet from the docs git repository).

The new version 7.0.0 source code is published on Source Forge as well as in Branch-7.0 of the bacula git public repository. The docs are also available in the docs git public repository, and are also in Branch-7.0. Since there were a number of significant changes with the documentation build process the upload of the docs to the website does not yet totally work. There is a strange layout problem with the main page of the pdf that does not show up in directly reading the downloaded pdf, and there seem to be a number of missing icons for the html documents (annoying but apparently not critical) that I will correct in the coming days.

In addition the new website has been activated. If you experience problems, please do not hesitate to signal them to me at: kern at sibbald dot com. If you want to get to the old website it can be accessed at old.bacula.org, but will in the long term be eliminated.

We are still working on new Windows binaries as well as releasing a full set of binaries for many platforms. Hopefully that will be finished before the end of April.

Thank you for your ongoing support and your patience in waiting for this release. I hope that you will find it satisfactory.

About Us

Open Source Backup, Enterprise ready, Network Backup Tool for Linux, Unix, Mac, and Windows

Recent tweets by Bacula Systems

Testimonials

Astrium Ltd

“We are using Bacula to backup a number of elements. One of them is the data from the SCOS 2000 application (the generic mission control system software of ESA). We also backup multiple environments related to the deployment of the satellite ground segments. Aside from that, we have a lot of projects being backed up via Bacula: R D and RADAR projects, FOC (Flight Operation Control, i.e. satellite operation planning, as well as command and control of satellites), and more… We do both full and incremental backup, as well as archives. All in all, we re very satisfied with Bacula. The software offers us a consistent, reliable, and powerful platform, and all of this without licensing costs.

NFanjeau and CCovemaeke, 25/08/2011

Copyright © 2009-2015 Bacula.org All rights reserved.