I read the release notes for version 13.0.4, and 15.x. Based on that, I
believe that a 15.0.2 dir and SD should be able to collaborate with a
13.0.4 FD. There was a bug present on 13.x (but fixed in 13.0.4) that
harmed FD backwards compatibility for bacula versions >=13.x, but <13.0.4.
So in theory, you should be able to use version 15.0.2 to interact with FD
versions <13, 13.0.4, and 15.0.2. Please note that the FD compatibility
issue was not a total communication failure, but a more subtle issue. I
believe some messages from the FD, perhaps warnings of some sort, were not
being communicated to the 13.x version directors. Again, as of 13.0.4, this
bug should be fixed.

Upgrading bacula from 13.0.4 to 15.0.2 - I am not familiar with the upgrade
process so I cannot say for certain. Based on the release notes for 15.0.2,
I believe that bacula version 15.x uses a new catalog format. As such, the
catalog will be upgraded as part of the upgrade process. I think you won't
be able to downgrade this catalog to the older version once upgraded.

Go to the 15.0.2 repository in a web browser using your repository link and
read the release notes and installation instructions present in the 15.0.2
repository directory. I believe more information is available there.

There may not be explicitly clear upgrade instructions in the release
notes. In general, I think you would need to update your bacula repository
link to refer to the bacula version you want (15.0.2), and then direct your
package manager to upgrade the bacula packages, however that is done.

I believe the release notes may explain how to upgrade the bacula catalog
after an upgrade is complete, regardless of how you performed the upgrade.
Probably need to run a script, iirc.

Prior to upgrading, I would:
Take a full backup of your bacula catalog and restore that backup file
(bacula.sql) somewhere safe.
Copy your bacula installation folder (default: /opt/bacula/) and
configuration files (default: /opt/bacula/etc/) somewhere safe.
Ensure that these safe places for these files aren't anywhere in the bacula
directory or a sub directory of that directory.

This gives you a fighting chance of rolling back if something goes wrong. I
don't expect it will go wrong, but just in case...

Robert Gerber
402-237-8692
r...@craeon.net

On Sun, Jun 2, 2024, 9:15 AM <d...@bornfree.org> wrote:

>
> Are the Bacula CE 15.0.2 director and storage daemons backward
> compatible with 13.0.4 agents (file daemons) ???
>
> Also, where can I find information on upgrading from 13.0.4 to 15.0.2 ???
>
> ---
>
>
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to