------- Original Message ------- On Monday, July 3rd, 2023 at 05:09, Gina Costa <gina.co...@uc.pt> wrote:
> Hi, > I have a windows client which backup always run fine. A few days ago, the > backup doesn’t work. > The comunication between diretor and client is OK, as shown in this log > message: > [...snip...] > > When the backup job ran, the following error occurs: > > ========== > 03-Jul 11:27 vsantoantao-fd JobId 6989: Fatal error: lib/bsock.c:138 Unable > to connect to Storage daemon on 192.168.0.164:9103. ERR=The operation > completed successfully. > 03-Jul 11:27 vsantoantao-fd JobId 6989: Fatal error: Failed to connect to > Storage daemon: 192.168.0.164:9103 > 03-Jul 11:31 bacula-dir JobId 6989: Fatal error: Bad response to Storage > command: wanted 2000 OK storage, got 2902 Bad storage > ========== > > Can anyone help me? Hello Gina, The problem here is that the Windows FD cannot connect to the Storage daemon @ 192.168.0.164 on port 9103/TCP... Please make sure that a Storage daemon is actually running on the server at that address. Also check that there are no firewall rules or TCP Wrappers rules on the SD preventing this client from connecting. Also, make sure that address is the correct address for the storage daemon. What I mean is check the `Address = xxxx` line in the Director's configuration for this storage resource. And, that FD is quite old. Any chance you can upgrade it to match what the Director and SD are at? Best regards, Bill
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
