The launch of the new version of the multiplatform client-server backup system "Bacula 13.0.0" was presented . This new version omits the 12.x branch to separate the version numbering between the free and commercial editions: the free version uses odd branch numbers, while the commercial version uses even numbers.
For those who are not familiar with Bacula, they should know that this is a collection of backup tools capable of covering the backup needs of equipment under IP networks.
About Bacula
It is based on a client-server architecture that is efficient and easy to use, given the wide range of functions and features it offers, such as copying and restoring damaged or lost files. Furthermore, due to its modular design and structure, Bacula is suitable for both personal and professional use, from a single computer to large server farms.
Bacula is divided into several interconnected parts . These parts can be installed on different machines or on the same machine, giving the option to save backups on a different machine than the one that manages them (for example).
There are three main parts , each of which is a separate installation package: Director, Storage, and File . File is the client machine (the one that needs backups), Storage is the machine that stores those backups, and Director is the machine that orchestrates the entire process.
Of course there can be several client machines (File), several Storage (in case you want to separate the copies) and Director (although the logical thing would be one, several can be specified).
It is worth mentioning that the code of the free edition of Bacula is distributed under the AGPLv3 license, but excessive control over the development process and cutting functionality in favor of the commercial version a few years ago led to the creation of a fork: Bareos , which is actively developed and competes with Bacula.
Main new features of Bacula 13.0.0
This new version of the utility highlights the addition of a new backup catalog format, which requires simultaneous updates to the Director process and the Storage Daemon, which is responsible for providing the resources to save backups.
It is mentioned that File Daemon must be updated if it is running on the same system as the new Director or Storage, and that the necessary tools to automate the conversion of the old catalog format to the new one are included, but the upgrade process will require approximately twice the disk space of the current backup catalog.
Another notable change in the new version is the implemented support for "storage pools", as well as the addition of a Kubernetes plugin.
In addition, it is also noted that an option was added to save only the ACLs and the file metadata separately, and that support for Windows CSV (Cluster Shared Volumes) was added.
On the other hand, it is mentioned that the object catalog now offers the possibility of using labels, FileSet allows SHA256 and SHA512 hashes and that the ability to authenticate through LDAP has been added.
Other notable changes include:
- Windows Installer 'Silent Mode' Options
- Added PriorJob to bconsole 'llist job' output
- Added MaximumJobErrorCount FileDaemon directive
- In bsmtp the possibility of adding emails separated by a comma as a list of recipients is added
- SDPacketCheck FileDaemon used to control network flow
- Director crash fix for client initiated backup
- Director crash fix for migration job
- Fix wrong output for .status client command
- Fix for deadlock when starting Director with an incorrectly configured catalog
- Solution to the reloading problem when a job does not have a group defined
- Skip storage daemon detection if information is not available in the BSR
Finally, if you are interested in learning more about this , you can find the details at the following link.
Download and get
Those interested in obtaining the new version can do so via the following link. Those interested in installing and learning more about this utility can consult the documentation at this link.