The following Backup Job log error message is one of the most common in new Bacula installations:
xxx-fd JobId x: Error: lib/bsockcore.c:285 gethostbyname() for host "xxx" failed: ERR=No such host is known. xxx-fd JobId x: Fatal error: filed/job.c:2138 Failed to connect to Storage daemon: srvbacula2:9103 xxx-dir JobId 12: Fatal error: Bad response to Storage command: wanted 2000 OK storage
In this case, the function gethostbyname() indicates the exact problem. The standard Bacula installation uses the hostname of the machine as network addresses. If these cannot be resolved by the Client machines, which initiate the connection by default to the Storage Daemon, the error will occur.
Change the Address of your Autochanger/Storage in bacula-dir.conf to a local network IP or a name that your Clients can resolve.
In addition to these tips, Bacula Brazil and Latin America also provides support for all versions of Bacula, as well as Bacula Enterprise Edition Licenses.
Disponível em: Português (Portuguese (Brazil))EnglishEspañol (Spanish)