问题描述
- 使用bacula服务器备份，客户端在win,服务端为linux，备份失败的问题
-
06-7月 19:29 saas-dir JobId 101: Start Backup JobId 101, Job=FullBackup.2015-07-06_19.29.16_24
06-7月 19:29 saas-dir JobId 101: Using Device "FileStorage" to write.
06-7月 19:19 saas-fd JobId 101: Warning: lib/bsock.c:132 Could not connect to Storage daemon on 192.168.8.170:9103. ERR=B2D9D7F7B3?A6CDEAB3ɡA3Retrying ...
06-7月 19:35 saas-fd JobId 101: Warning: lib/bsock.c:132 Could not connect to Storage daemon on 192.168.8.170:9103. ERR=B2D9D7F7B3?A6CDEAB3ɡA3Retrying ...
06-7月 19:48 saas-fd JobId 101: Fatal error: lib/bsock.c:138 Unable to connect to Storage daemon on 192.168.8.170:9103. ERR=B2D9D7F7B3?A6CDEAB3ɡA306-7月 19:48 saas-fd JobId 101: Fatal error: Failed to connect to Storage daemon: 192.168.8.170:9103
06-7月 19:59 saas-dir JobId 101: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage06-7月 19:59 saas-dir JobId 101: Error: Bacula saas-dir 7.0.5 (28Jul14):
Build OS: x86_64-unknown-linux-gnu redhat (Core)
JobId: 101
Job: FullBackup.2015-07-06_19.29.16_24
Backup Level: Full
Client: "saas-fd" 5.2.10 (28Jun12) Microsoft Windows Home ServerEnterprise Edition Service Pack 2 (build 3790),Cross-compile,Win32
FileSet: "Full Set" 2015-07-06 11:16:12
Pool: "Default" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "saas-sd" (From command line)
Scheduled time: 06-7月-2015 19:29:16
Start time: 06-7月-2015 19:29:18
End time: 06-7月-2015 19:59:22
Elapsed time: 30 mins 4 secs
Priority: 10
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):Volume Session Id: 3
Volume Session Time: 1436168494
Last Volume Bytes: 20,672 (20.67 KB)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
Termination: *** Backup Error ***
解决方案
Fatal error: lib/bsock.c:138 Unable to connect to Storage daemon on 192.168.8.170
这几台daemon机器连接不上
解决方案二：
搞定了，原来是我的服务端防火墙没关，导致客户端无法连接存储端。以前的centos 6的防火墙是 service iptables命令，而现在的centos 7却是firewall，所以会犯这种低级错误。。。也是因为基础不够扎实吧