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:

====
vsantoantao-fd Version: 5.2.10 (28 June 2012)  VSS Linux Cross-compile Win32
Daemon started 03-Jul-23 10:55. Jobs: run=0 running=0.
Microsoft Windows Server 2003 R2 Standard Edition Service Pack 2 (build 3790)
 Heap: heap=0 smbytes=32,299 max_bytes=34,815 bufs=65 max_bufs=91
 Sizeof: boffset_t=8 size_t=4 debug=0 trace=1
Running Jobs:
Director connected at: 03-Jul-23 11:56
No Jobs running.
====

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?

Universidade de Coimbra • Administração
SGSIIC-Serviço de Gestão de Sistemas e Infraestruturas de Informação e 
Comunicação
Divisão de Infraestruturas de TIC
Rua do Arco da Traição | 3000-056 COIMBRA • PORTUGAL 
Tel.: +351 239 242 870 
E-mail: gina.co...@uc.pt
www.uc.pt/administracao
 




Este e-mail pretende ser amigo do ambiente. Pondere antes de o imprimir! 
This e-mail is environment friendly. Please think twice before printing it!


Attachment: smime.p7s
Description: S/MIME cryptographic signature

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

Reply via email to