Upgrading Bareos 18.2 but repos are blocked
agenttank
We are using Bareos 18.2 for a few older/legacy physical hosts and VMs. Some clients use Bareos 16/17, some clients use CentOS 5 or even 4. We did not keep track of any news regarding paywalling the repositories. We honestly did not expect this to happen.
It will take us a while to upgrade the clients (or move the services that run there to more modern platforms/OSs), so we still have to make sure, that backups (and restores!) work.
Turns out we could potentially also run into problems, when trying to restore from the server, because we can’t download those old Bareos versions!
I tried upgrading the Bareos server (18.2) to the most recent version 22, but it turns out, since version 21 or so only PostgreSQL is supported as catalog driver, so we’d need version 20 or so to convert the database (which I don’t get either).
We are thinking about switching to the paid version of Bareos, but we’d have to be very sure, that this all works out.
Does Bareos 22 (client) work with CentOS 4 or 5?
Can Bareos 16/17 connect to Bareos 22 server?
I’d be very happy to read suggestions!
Thank you!
Best regards
Stefan Pinter
Frank Kohler
Hi Stefan,
Hi!
We are using Bareos 18.2 for a few older/legacy physical hosts and VMs. Some clients use Bareos 16/17, some clients use CentOS 5 or even 4. We did not keep track of any news regarding paywalling the repositories. We honestly did not expect this to happen.
Not the only channel for communication:
https://www.bareos.com/bareos-release-policy/
I tried upgrading the Bareos server (18.2) to the most recent version 22, but it turns out, since version 21 or so only PostgreSQL is supported as catalog driver, so we’d need version 20 or so to convert the database (which I don’t get either).
We are thinking about switching to the paid version of Bareos, but we’d have to be very sure, that this all works out.
Does Bareos 22 (client) work with CentOS 4 or 5?
Can Bareos 16/17 connect to Bareos 22 server?
I’d be very happy to read suggestions!
Thank you!
best,
Frank
Best regards
Stefan Pinter
--
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/beb99931-0563-445a-ae53-5bdf8feddc8cn%40googlegroups.com.
-- 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, J. Steffens, P. Storz
agenttank
Hi Frank!
Thank you for taking the time to answer me!
Not the only channel for communication: https://www.bareos.com/bareos-release-policy/
I am not sure what you mean, but yes, I've read this already.
https://www.bareos.com/end-of-life-mysql/
I've seen this, yes. But I don't have bareos-dbcopy on the Bareos 18.2 installation - and also not on a fresh 22 installation (from what I understand it doesn't support MySQL at all, so no bareos-dbcopy there as well)
Drop me a line via PM.
Thank you for the offer, I will at some point!
There's probably a good reason for running OSes which went EOL way before Bareos was founded.
You know there isn't ;)
From security perspective it might be a consideration to ssh payload into current OSes with currently maintened Bareos components.
You mean using a installation with a current OS as a "ssh / bareos-fd proxy" for this? like this:
OLD SERVER -> RSYNC cronjob -> bareos-fd proxy -> bareos-dir
Is it known, if Bareos 16 clients can connect to Bareos 22 clients? I am sure that you don't recommend any of this.
Thanks again!
Ruth Ivimey-Cook
Folks,
Can I just remind people that it is quite possible -- even fairly
simple -- to build bareos from source on the distro you have to
hand. I did so not so long ago for my Raspberry Pi (armv7) and it
was painless, took about 20 mins, and works just fine. In my case,
install & run debbuild was the thing to do. I guess CentOS
will use a different method, but it's all there.
If your answer is 'but it's not guaranteed to work' ... well, the community versions were never *guaranteed* to work and came without *any* formal level of support. In other words, your own build is just as likely to work as the build the Bareos team made.
On the other hand, even if Bareos itself is bug-free the
libraries (eg for tls) that old versions use have many well known
critical CVEs and so I would suggest that using old versions of
Bareos is a significant security risk -- and remember that not all
malware needs to traverse a firewall.
Regards,
Ruth
--
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/beb99931-0563-445a-ae53-5bdf8feddc8cn%40googlegroups.com.
-- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/
Frank Kohler
You mean using a installation with a current OS as a "ssh / bareos-fd proxy" for this? like this:
OLD SERVER -> RSYNC cronjob -> bareos-fd proxy -> bareos-dir
yes, one way to implement it
Is it known, if Bareos 16 clients can connect to Bareos 22 clients? I am sure that you don't recommend any of this.
(and we didn't intentionally break any compatibility).
Thanks again!
nice we!
Frank
Knauf Steffen
Gesendet: Freitag, 13. Oktober 2023 15:01
An: bareos-users <bareos...@googlegroups.com>
Betreff: Re: [bareos-users] Upgrading Bareos 18.2 but repos are blocked