I recently rebuilt my workstation from Fedora 20 to 21 and am now having issues with Bacula that may stem from incompatibilities between Bacula versions.  I’m hoping somebody can confirm my suspicion.  At present, I have:

 

Dir and SD are on the same Fedora 20 host with:

 

bacula-client-5.2.13-18.fc20.x86_64

bacula-common-5.2.13-18.fc20.x86_64

bacula-console-5.2.13-18.fc20.x86_64

bacula-director-5.2.13-18.fc20.x86_64

bacula-libs-5.2.13-18.fc20.x86_64

bacula-libs-sql-5.2.13-18.fc20.x86_64

bacula-storage-5.2.13-18.fc20.x86_64

 

My Fedora 21 workstation has:

 

bacula-client-7.0.5-2.fc21.x86_64

bacula-common-7.0.5-2.fc21.x86_64

bacula-libs-7.0.5-2.fc21.x86_64

 

If I try to run a simple incremental backup job for my workstation, the log emits:

 

07-Jan 11:35 mdct-bacula-dir JobId 32287: Start Backup JobId 32287, Job=Florian_Workstation.2015-01-07_11.35.23_23

07-Jan 11:35 mdct-bacula-dir JobId 32287: Using Device "FileStorage" to write.

07-Jan 11:35 mdct-dev12.dartcontainer.com- JobId 32287: Fatal error: Authorization key rejected by Storage daemon.  Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000 for help.

07-Jan 11:35 mdct-bacula-dir JobId 32287: Fatal error: Bad response to Storage command: wanted 2000 OK storage, got 2902 Bad storage

 

I am quite familiar with Bacula’s authorization requirements and have confirmed everything is correct.  (In fact, I’ve had puppet managing these aspects for years to reduce the probability of human error.)  It’s for these reasons I suspect there must be a version compatibility issue here.  I’ve checked the release notes but find them lacking detail in this regard.  (The last time “compat” is mentioned goes all the way back to the 5.2.11 release and that only talks about having older FDs – nothing about newer FDs.)

--

John Florian