Hi folks,
I think I have got it tracked down. The backup box is a multi-homed
server and the Autochanger had got the wrong address. After changing the
address, it's working.
I will however, post a new question about configuration on a multi-homed
backup server.
Best regards,
Peter
On 17.01.2023 15:35, Peter Milesson via Bacula-users wrote:
Hi folks,
After changing a FileSet definition, removing one of the lines in
bacula-dir.conf, and increasing the maximum number of volumes in the
Pool, backups are no longer working.
The messages I get are:
17-Jan 14:30 Server1Fd JobId 837: Fatal error: Authorization key rejected by
Storage daemon.
For help, please
seehttp://www.bacula.org/rel-manual/en/problems/Bacula_Frequently_Asked_Que.html
17-Jan 14:30 Location1Dir JobId 837: Fatal error: Bad response to Storage
command: wanted 2000 OK storage
, got 2902 Bad storage
17-Jan 15:00 Location1Dir JobId 838: Error: Director's connection to SD for
this Job was lost.
When running bconsole, status for the director, the following line is
displayed:
838 Back Full 0 0 Server1 is waiting for Client
Server1Fd to connect to Storage File1
No changes to names, passwords and similar have been made. When
checking on the client with netstat, I can see that there is an
established connection between the director and the file daemon.
There are no firewalls involved.
The versions:
Backup server - Debian Bullseye 11.6 with Bacula 11.0.5
Backup client 1 - CentOS 7.9 with Bacula 9.0.6-3.el7.centos
Best regards,
Peter
_______________________________________________
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
