Seasons greetings w/ release 22 ;-)
Frank Kohler
Happy
holidays!
So we just had our 10th anniversary as we founded Bareos GmbH on
12-12-12 with two full time developers [1]. Glad you are around and
supportive. Special thanks go out to our community sponsors [2] with
Brock Palen being the very first! Note we change release policy for
community to rolling release [3]. [1] https://www.bareos.com/bareos-10-years/
[2] https://github.com/sponsors/bareos/
[3] https://www.bareos.com/bareos-release-policy/
best regards,
Frank
Bareos 22 released
-
-
Enhanced VMware Plugin
-
I/O Performance Improvements
-
Optimized Ceph Support
-
Tech Preview: Backup Checkpoints
-
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.
Enhanced VMware Plugin
The VMware plugin has been creating full and incremental backups since Bareos 15.2. While the plugin could only restore existing virtual machines (VM) in earlier versions, it is also possible to create new VMs from the backups as of Bareos 22. Administrators can now select folders, hosts, clusters, or datastores for this purpose. To avoid conflicts with other VMs, the VMware UUID and MAC address can be regenerated. In addition, a restore is now also possible via the Bareos WebUI.
The developers have upgraded the VDDK (Virtual Disk Development Kit) to the current version 8.0.0. The plugin now supports vSphere 8 and is backward compatible with vSphere 6.7 and 7.
Increased I/O Performance of Python Plugins
Python plugins for the Bareos File Daemon (FD) now support direct I/O in the Bareos core, instead of having to take a diversion via the Python code for read and write. This may not be possible or useful for every plugin, but appropriately adapted plugins can double their performance. A backup via the Python plugin is now just as fast as a backup directly via the File Daemon.
Optimized Support for Ceph
In future, only the Droplet Storage Backend is used to back up Ceph storage. As described in the Bareos documentation, it backs up Ceph targets via S3 and thus guarantees optimal performance. If Ceph is the source, it’s mounted in the regular file system and the standard File Daemon takes care of the backup.
The developers have removed the deprecated RADOS/Ceph backend and the Cephfs plugin. If previously installed, the packages bareos-storage-ceph and bareos-filedaemon-ceph-plugin need to be removed manually.
New Packages and Features
Bareos 22 consolidates several RHEL platforms and now provides one single package for the derivatives. The developers have also added Ubuntu 22.04, Fedora 36 and 37, RHEL 9 derivatives (Rocky Linux, AlmaLinux, Oracle Linux, CentOS Stream), and openSUSE/SLES 15.4 to the list of supported distributions.
Packages for compatible platforms (RHEL derivatives, openSUSE/SLES, Debian/Univention Corporate Server) are only built once. The automated tests against all platforms remain. As a result, the number of download directories of the repositories is reduced.
The developers have further modernized the Bareos code and revised it to comply with the C++20 standard. Since there are no suitable C++20 compilers for all platforms yet, the code is still compiled with C++17 options.
As a Tech Preview, the developers have introduced a first version of the so-called backup checkpoints. The feature allows restoring from incomplete backup jobs. As of Bareos 22, it is possible to restore already backed up files from backup jobs that have not yet been successfully completed. Future releases will be able to resume failed or incomplete jobs.
For more information, please see our press release. Packages and release notes are now available on our download servers.
- Subscription Repository: https://download.bareos.com/bareos/release/22
- Community repository: https://download.bareos.org/
- Release Notes: https://docs.bareos.org/Appendix/ReleaseNotes.html
- GitHub Repository: https://github.com/bareos/bareos/
-- Frank Kohler Bareos GmbH & Co. KG Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz
Chad William Seys
C.
On 12/22/22 04:26, Frank Kohler wrote:
>
> Happy holidays!
>
> So we just had our 10th anniversary as we founded Bareos GmbH on
> 12-12-12 with two full time developers [1]. Glad you are around and
> supportive. Special thanks go out to our community sponsors [2] with
> Brock Palen being the very first! Note we change release policy for
> community to rolling release [3].
>
> [1] https://www.bareos.com/bareos-10-years/
> [2] https://github.com/sponsors/bareos/
> [3] https://www.bareos.com/bareos-release-policy/
>
>
> best regards,
> Frank
>
>
>
>
> *
> o
>
> Enhanced VMware Plugin
>
> o
>
> I/O Performance Improvements
>
> o
>
> Optimized Ceph Support
>
> o
> Tech Preview: Backup Checkpoints
>
> 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.
>
>
> Enhanced VMware Plugin
>
> The VMware plugin
> the plugin could only restore existing virtual machines (VM) in earlier
> versions, it is also possible to create new VMs from the backups as of
> Bareos 22. Administrators can now select folders, hosts, clusters, or
> datastores for this purpose. To avoid conflicts with other VMs, the
> VMware UUID and MAC address can be regenerated. In addition, a restore
> is now also possible via the Bareos WebUI.
>
> The developers have upgraded the VDDK (Virtual Disk Development Kit) to
> the current version 8.0.0. The plugin now supports vSphere 8 and is
> backward compatible with vSphere 6.7 and 7.
>
>
> Increased I/O Performance of Python Plugins
>
> Python plugins for the Bareos File Daemon (FD) now support direct I/O in
> the Bareos core, instead of having to take a diversion via the Python
> code for read and write. This may not be possible or useful for every
> plugin, but appropriately adapted plugins can double their performance.
> A backup via the Python plugin is now just as fast as a backup directly
> via the File Daemon.
>
>
> Optimized Support for Ceph
>
> In future, only the Droplet Storage Backend
> The developers have removed the deprecated RADOS/Ceph backend and the
> Cephfs plugin. If previously installed, the packages
>
>
> New Packages and Features
>
> Bareos 22 consolidates several RHEL platforms and now provides one
> single package for the derivatives. The developers have also added
> Ubuntu 22.04, Fedora 36 and 37, RHEL 9 derivatives (Rocky Linux,
> AlmaLinux, Oracle Linux, CentOS Stream), and openSUSE/SLES 15.4 to the
> list of supported distributions.
>
> Packages for compatible platforms (RHEL derivatives, openSUSE/SLES,
> Debian/Univention Corporate Server) are only built once. The automated
> tests against all platforms remain. As a result, the number of download
> directories of the repositories is reduced.
>
> The developers have further modernized the Bareos code and revised it to
> comply with the C++20 standard. Since there are no suitable C++20
> compilers for all platforms yet, the code is still compiled with
> C++17 options.
>
> As a Tech Preview, the developers have introduced a first version of the
> so-called backup checkpoints. The feature allows restoring from
> incomplete backup jobs. As of Bareos 22, it is possible to restore
> already backed up files from backup jobs that have not yet been
> successfully completed. Future releases will be able to resume failed or
> incomplete jobs.
>
> For more information, please see our press release
>
> * Community repository: https://download.bareos.org/
> * Release Notes: https://docs.bareos.org/Appendix/ReleaseNotes.html
> * GitHub Repository: https://github.com/bareos/bareos/
>
> --
> Frank Kohler
> Bareos GmbH & Co. KG
> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
> Komplementär: Bareos Verwaltungs-GmbH
> Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, P. Storz
>
> You received this message because you are subscribed to the Google
> Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to bareos-users...@googlegroups.com
> <mailto:bareos-users...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/bareos-users/363ce0d7-23c7-a4c0-dd6e-17af551c5e61%40bareos.com <https://groups.google.com/d/msgid/bareos-users/363ce0d7-23c7-a4c0-dd6e-17af551c5e61%40bareos.com?utm_medium=email&utm_source=footer>.
Christian Reiss
Even with super bad news. There it is, in a sub-sentence:
>> On 12/22/22 04:26, Frank Kohler wrote:
>> Note we change release policy for community to rolling release [3].
This is super bad. Let me explain why.
I am -as a private, non-commercial user- using B* for my backup purposes
with 20+ years of B* knowledge under my belt. In the early 2000s with
Bacula. A some point, Bacula did not really accept any more ideas; well
they did, but they only put those into the commercial product, letting
the open source community die. They would word it in some other way, but
in the end, it was dead in the water.
A fact that really annoyed you guys from Bareos. So much in fact that
you forked Bacula to Bareos. For a looong time I have been using Bareos
as my last line of defense, did a speech in the Open Source Backup
Conference and am/was a B* evangelist, preaching everyone to use it.
Now you do a rolling release for private people. Let's face it: B* is
not for the normal user. My mom, uncle or any of my non-tech savy
friends will ever use it. It's not the use case. So when I say I run
Bareos on 50+ vms for my private usage, well, that's normal business here.
With you new "rolling release" how can I make sure server 13 has the
same version as server 51? How can I blindly type "dnf update" and know
stuff will not break? With a rolling release? I happy stayed 1-2 major
versions behind to have a stable, rock-solid experience.
CentOS did the same. They mission was to provides a stable, non-changing
copy/clone of RedHat with the expressed purpose to be binary compatible
to the RedHat equivalent. They switched to rolling release and killed
their usability and also (pretty much) died. They did not understand
even up to today why this was bad.
But you said so yourself on https://www.bareos.com/bareos-release-policy/:
"not for production"
A... backup solution that is not for production? Maybe I am old
fashioned, but Backups should be reliable, provable working, re-storable
and idempotent. Also, this is a virtual smack in the face for all us
non-paying, private users. Our data is not worth saving. Or at least not
as important as the paid version. Well, we're not producing anything. Or so.
Maybe it's only me. But my data is not a guinea pig.
I guess at some point when you fork for the right reasons and then build
a company around it, you must shed of the deadweight that once helped
you, supported you, carried you to new datacenters and preached.
CentOS did this. Zimbra, too. And now Bareos.
Who is forking next? If you do, please don't start a company on it.
--
Mit freundlichen Grüßen
Christian Reiss
_____________________________________________________________
Christian Reiss
CTO
DALASON GmbH
Im Mediapark 5
50670 Köln
Germany
Tel: +49 221 - 177 396 - 20
christi...@dalason.de
Internet: www.dalason.de www.dcalling.de www.wirecloud.de
Geschäftsführer: Andreas Damek, Chung-U Son
Sitz der Gesellschaft: Köln
Handelsregister: Amtsgericht Köln HRB 60929
____________________________________________________________
Rodrigo Jorge
"Maybe it's only me. But my data is not a guinea pig."
Rodrigo L L Jorge
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/f1017db9-12c4-493b-170f-26063e1b357e%40dalason.de.