I have configured a copy job on my primary backup server. The copy
volumes will be on a secondary system running another storage daemon.
Both systems are running Bacula 7.4.4 on Debian 9.
From the primary console, this command:
status storage=Remote-File
successfully returns version, daemon, job, device and volume data about
the secondary system. I assume this would fail if there were a password
problem, but when I attempt to run the copy job, I get:
06-Sep 10:39 backup-dir JobId 0: Fatal error: authenticate.c:122
Director unable to authenticate with Storage daemon at "[Secondary
server IP]:9103". Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the SD or
SD networking messed up (restart daemon).
I've looked through past threads about similar error messages. As far
as I can tell, my names, passwords and port numbers are configured
correctly. Concurrent job limit on the secondary SD is higher than on
the primary. SD was restarted after the most recent update to the
bacula-sd.conf file to get the status command to work.
Suggestions? Any conf file excerpts I need to post?
Thanks,
Brendan
--
*Brendan E. Martin* | Systems Administrator II
Department of Physics and Astronomy | Texas A&M University
4242 TAMU | College Station, Texas 77843-4242
979.845.7717 main | 979.845.2590 fax | bren...@physics.tamu.edu
<mailto:bren...@physics.tamu.edu>
http://physics.tamu.edu
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
