interoperability of versions

Asked by Chip Williams

My production system at the moment consists of a number of machines that are running bacula 1.3.8. Old. I am in the process of upgrading the systems to something newer, either 2.2.8 (in Ubuntu 8.04LTS) or 2.4.2 (in Ubuntu 8.10) as I upgrade the systems on the machines. When I'm done with the upgrade they will all be the same version, whatever it is. Leaving out the obvious issues with the database, can the versions interoperate between machines or do all daemons on all machines have to be the same version? All of the other machines besides the one with the director have only the file daemon or the storage daemon. The configuration files look the same. It would be much easier to incrementally get all the machines that have only one daemon updated and deal with the director last. Is this workable?

If I upgrade the storage daemon on a linux machine will it pick up with the pools as they are and run with it? Or, what kind of problems might I run into?

Thanks for the answers!

Question information

English Edit question
Bacula Edit question
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Kern Sibbald (kern) said :

Sorry, I am not the right person to ask these questions. In general, as documented in the manual, Bacula components are compatible only if the first two digits correspond. Sometimes version 2.4.x will be compatible with the previous 2.2.x releases (this is the case). To know you must read the release documentation. It is unlikely that 1.3.8 is compatible with any of the later versions.

I suggest you ask the above question on the bacula-users email list. They have the time and are much better at answering these things than I am.

Can you help with this problem?

Provide an answer of your own, or ask Chip Williams for more information if necessary.

To post a message you must log in.