Issues During Major Version Upgrade (FreeBSD, Debian)

[Leo L. Schwab]

Last night I upgraded my Bareos director and storage daemons from 19.x to 21.x using the binary packages published on FreeBSD's repositories (i.e. not the ones on download.bareos.org).

Unfortunately, the package installs a default "sample" configuration.  Moreover, these sample entries are live, i.e. they will be read and acted upon when bareos-{dir,fd,sd} are launched.  While the package doesn't overwrite any existing active config, it will add sample entries to it.  In a Bareos config directory tree, it can take considerable work to find and remove these entries.

The Debian packages for bareos-filedaemon and bareos-tray-monitor do the same thing.  When I upgraded the installation on my Linux desktop from v17(!) to v22, it added a new, active entry to the config: /etc/bareos/tray-monitor.d/client/FileDaemon-local.conf, which I had to manually delete.

I respectfully submit it should not be doing this.  All the package should be installing are inactive, sample entries.  Bareos is particularly complicated to configure, and I would venture to say there's no such thing as a "typical" installation.  Every Bareos installation is highly customized.  Dance on the sample files all you like, but don't modify/add to the active config; it just complicates the upgrade process.

Schwab

[Jörg Steffens]

Hello,

I agree that this behavior is far from being optimal. There had reasons
to implement it in this way, but if we had to take the decision anew, we
would implement it similar to what you proposed.
We problem is, that this can not easily be changed without breaking
existing installations, at least not on RPM-based systems. This is still
an open topic on our site, but unfortunately one that requires quite
some effort and we are not sure, when we will come to had.
In the meantime we advice to replace these kind of configuration files
with an empty files instead of deleting them, see
https://docs.bareos.org/Configuration/CustomizingTheConfiguration.html#resource-file-conventions

Sorry for the inconveniences that this causes.

Regards,
Jörg

PS: this problem does not only strike on major upgrades, but on every
update.

On 31.12.22 at 07:50 wrote Leo L. Schwab:

> --
> 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/cffec05e-8df9-43f9-884b-a9cc2ff5b175n%40googlegroups.com <https://groups.google.com/d/msgid/bareos-users/cffec05e-8df9-43f9-884b-a9cc2ff5b175n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz