I had a issue with one of my new servers today, if i do ping to my director server at-farbck01 it responds. Our network is running IPv4 and all the other bareos clients (FD) is running fine.
I thougt bareos was running on wrong network card (since there is a Idrac card in my server) so i did disable the idrac networkcard but it did not solve my problem.
Copy of the error message:
2015-10-21 19:35:56 at-farbck01-dir JobId 113: Start Backup JobId 113, Job=at-farapis01-fd.2015-10-21_19.35.54_16
2015-10-21 19:35:56 at-farbck01-dir JobId 113: Using Device "backup.baf.filestorage" to write.
2015-10-21 19:35:59 at-farapis01-fd JobId 113: Error: lib/bsock.c:208 bnet_host2ipaddrs() for host "at-farbck01" failed: ERR=No such host is known.
2015-10-21 19:35:59 at-farapis01-fd JobId 113: Fatal error: Failed to connect to Storage daemon: at-farbck01:9103
2015-10-21 19:35:59 at-farbck01-dir JobId 113: Fatal error: Bad response to Storage command: wanted 2000 OK storage
, got 2902 Bad storage
What solved my issue was to add my server and ip adress to the host file:
C:\Windows\System32\drivers\etc\host
sounds like you have a DNS problem for that server...
Does your DNS resolve both the directors and clients FQDN forward and reverse on both servers without the entry in your host file?
Your test should look like that.
1. deactivate the entry you did in your host file
2. Copy the used FQDN out of your configuration files to be sure that you don't have a typo
3. Resolve the FQDN with nslookup on windows or dig on linux on the director for the director it self the SD and the client.
4. Resolve the FQDN with nslookup on windows or dig on linux on the client for the director SD and the client
5. Optional: if your SD runs on an separate server do the resolving on that server too.
If resolving your FQDN on any of your server is not working you should fix that problem and bareos will work as expected.
Regards, Marco