Re: [Bacula-users] Getting Authorization key rejected by Storage daemon

Hello,

This response applies to a previous email about a "bad hello from director ...", which Dan Langille already answered.

Bacula has a few well defined rules regarding compatibility of components:

1. The DIR and all SDs whether on the same or different machines must be on the same version.

2. All Bacula components on the same machine must be the same version (unless you are careful to do the FD install in a different set of directories, but rule #1 still applies).

3. Bacula does not support FDs of a higher version (in the either the first two digits) than the DIR and SD. That is a DIR and SD on 5.2.5 will work with an FD version 5.2.13, but not with an FD version 7.0.x.

4. In general Bacula supports all FDs on older versions than the DIR and SD. However, attempting to use a newer DIR/SD feature will fail.

Resumé:

- The DIR and all SDs must be on the same version.
- All components must be the same version for a given machine.
- Bacula accepts older FDs (i.e. you can upgrade without upgrading *all* your FDs) but only with the features the old FD has).
- With the exception of permitting older FDs mixing of Bacula components of different versions is very likely to fail or cause unexpected problems.

By the way, newer versions of Bacula from 5.2.x on are much more aware of what functionality FDs have, so new Directors are better at adapting to or detecting the reduced feature sets of older FDs support.

Best regards,
Kern

On 06/25/2014 10:09 PM, Frank Schima wrote:

Hi all,

Here is my situation. We have an existing bacula director and SD running on Debian 6 Linux with ~50 clients. The director is running version 5.0.2. This has been working great for many years.

My machine is a Mac running OS X Mavericks with bacula client 5.2.13 from Macports. This always backs up just fine - and very fast.

I just updated my bacula client to version 7.0.4 (with Macports). But I see the following errors on the server every time:

Fatal error: Authorization key rejected by Storage daemon.

and
Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
I am using the exact same bacula-fd.conf file which works with 5.2.13. No changes on the server either. Going back to client version 5.2.13 works fine again.
Any ideas what the problem could be with my 7.0.4 client? Does something need to change either on the client or server config file(s)?

Thank you,

Frank
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Getting Authorization key rejected by Storage daemon on Bacula 7.0.4 OS X