We are pleased to announce Bareos 23.1.0, a release featuring essential bug fixes, system improvements, and exciting new technical preview features:
New Features (Technical Previews): • Dedupable Storage Backend to save space: This allows smart storages to deduplicate Bareos volumes. • WORM-Tape Support for better resistance: Write Once, Read Many (WORM) support ensures that once data is written, it cannot be modified. • Just-In-Time Device Reservation for fewer idle tape drives: Optimizes storage device use by reserving them only when data is ready to be written.
We’ve just released Bareos 23.0.4 , Bareos 22.1.6 and Bareos 21.1.11 with security responses to a CVE published in parallel, and launched support for Ubuntu 24.04 and Fedora 40.
Bareos 24 will be released in November 2024. The following features are planned to be part of the release:
Dedupable Storage Backend
This new storage backend stores the backup data in a format optimized for deduplication. This allows Bareos volumes to be deduplicated by storages and filesystems with deduplication support (like ZFS, VDO, btrfs and others). The new command line tool bdedupestimate can estimate the deduplication potential of existing backup volumes, helping users optimize their storage use.
We’ve just released Bareos 23.0.3 with a security response to CVE-2023-4807 and others, a premiere of aarch64 Universal Linux Client, support for FreeBSD 14, improvements for VMware as well as several bugfixes.
The Bareos project will use GitHub Issues (instead of Mantis).
In 2012, the Bareos project was launched with a commitment to fostering close integration with the community and leveraging advanced automation services. However, a span of 10 years provides ample opportunity for evolution and innovation. Over the course of this decade, we have continuously adapted and modernized our infrastructure.
Among other changes, we have made significant advancements in the following areas:
Code: Since the beginning, we have relied on git and GitHub as our code repository. Initially, we accepted contributions in the form of emails and patches. However, for some time now, we have exclusively transitioned to using Pull Requests, automated tests, and a structured review process.
Package Building: Originally, our package building process relied heavily on the powerful https://openbuildservice.org/ for Linux packages. However, we had to resort to different approaches for other platforms. Therefore we have transitioned to using Jenkins, Build-Worker, and Docker containers for all platforms. This transition has been seamless for end-users, but it allows us to create packages for all our platforms within the same streamlined process. Additionally, this optimized process tailored for Bareos operates much faster.
Bugtracker: Since our inception in 2012, we have utilized Mantis as our bug tracker, and for the most part, we were satisfied with its performance. However, due to a tighter integration with our other processes, we have decided to migrate to Github Issues in April 2024. We anticipate that this transition will result in a better integration of error reporting, development, and pull requests.
Support: In addition to our internal processes, we utilize https://zammad.org as a ticketing system for customers with support contracts.
Three month after the release of Bareos 22 we have just published bugfix releases 22.0.3 and 21.1.7. to our subscription and to our GitHub repository. We recommend to update your installations accordingly.
We have just published a new major version of our Open Source backup solution. Among other things, the Bareos 22 release contains an enhanced VMware plugin, major performance improvements, and a technical preview of the new Checkpoints feature.
Bareos was founded ten years ago to continue the Open Source nature of this enterprise grade project for backup, archiving and recovery. We are strongly committed to continuing our work in the very same spirit, and working jointly with our community. Starting with the new release (Bareos 22), we’re updating our release policy to enhance user experience, and streamline project efforts.
In November 2022, we released Bareos 21.1.5 and 20.0.8. The two maintenance releases are available for download in the repositories for subscription customers. As always, the source code is available in our GitHub repository.
Even though there will be no Bareos update for UCS 5 in the Univention App Center, you can still install our backup solution on this distribution. We will also be happy to create an individual support offer for anyone who wants to switch.
We’ve released Bareos 21.1.4, 20.0.7, and 19.2.13 on August, 5, 2022. All three maintenance releases are available for download in the repositories for subscription customers. As always, the source code is available in our GitHub repository.
We’ve released Bareos 21.1.0, 20.0.6, and 19.2.9. All three maintenance releases are available for download in the repositories for subscription customers. As always, the source code is available in our GitHub repository.
Starting with Bareos 21 (released on December 22, 2021), our Open Source backup solution no longer supports MySQL as Bareos catalog database. It has been marked as deprecated since Bareos 19.2, and in Bareos 20, it was only available when updating existing installations.
With 2021 coming to an end, we are announcing one last major release for Bareos (Backup Archiving Recovery Open Sourced). Bareos 21 includes, among other things, a new Universal Linux Client, packages for the EL8 platform, and enhanced IPv6 support.
We’re happy to announce Bareos 20.0.4. The release includes some new features as well as bug fixes. It’s available for download in the repositories for subscription customers. As usual, all sources are available in our GitHub repository.
As previously announced, the latest link on the Bareos download servers will be removed soon. For several months now, it has been pointing to version 19.2 as a temporary solution, but will shortly be deleted. Read on to find out what’s changing for the Bareos repositories.
We’ve released Bareos 20.0.3, 19.2.11, and 18.2.12. All three maintenance releases are available for download in the repositories for subscription customers. As always, the source code is available in our GitHub repository.
We’ve just released a new Bareos version with some bug fixes, changes and new features. It’s the second point release of Bareos 20. Packages for Bareos 20.0.2 are available for download in the subscription repository. As always, all sources are available via our GitHub repository.
We’ve just released a new version: Bareos 20 includes, among other things, a new plugin to back up cloud storage objects directly via the S3 interface, a modernized Python API and a preview of the new REST API.
What’s going on in the Bareos universe? Above all, we have a new Security Policy. In addition, we’ve released some new plugins for the Bareos File Daemon, we’ve improved the Storage Daemon and the WebUI.
We’ve just published three Bareos point releases: 19.2.8, 18.2.9, and 17.2.10. The updates fix two security issues, which – especially in combination with each other – can become a serious problem.
Our backup solution has a new feature: bareos-filedaemon-postgres-python-plugin implemented in Python. The PostgreSQL plugin for Bareos uses the standard API PostgreSQL backup routines.
The Bareos team has released new versions of the Open Source backup solution: Bareos 19.2.7, 18.2.8, 17.2.9, and 16.2.10 are available for download on our servers.
With new plugins for oVirt and Percona XtraBackup and a new tool for converting the Bareos catalog database from MySQL to PostgreSQL, the final version of Bareos 19.2.5 is available.
A new oVirt plug-in, client-initiated backups on connection, an improved restore feature for the WebUI and more. Take a look at the first release candidate of the up-coming Bareos 19.2.4.!
Only a few days now until we will release Bareos 19.2 – stay tuned for more information! In the meantime, we have some other news to share. We’ve just released Bareos 18.2.7, 17.2.8, and 16.2.9 with some bug fixes and improvements.
We use cookies to enhance your experience by storing and accessing information on your device. By consenting, you allow us to process data like your browsing behavior. Opting out may affect site functionality.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Vorlieben
Die technische Speicherung oder der Zugriff ist für den rechtmäßigen Zweck der Speicherung von Präferenzen erforderlich, die nicht vom Abonnenten oder Benutzer angefordert wurden.
Statistics
Die technische Speicherung oder der Zugriff, der ausschließlich zu statistischen Zwecken erfolgt.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
