After installing the agent onto your client, regardless of the operating system, it’s generally a good idea to test the connection. This can be done both ways, the first being from the client to the director. The second test is from the director back to the client. Just because the first test passes, doesn’t mean [...]
After installing the agent onto your client, regardless of the operating system, it’s generally a good idea to test the connection. This can be done both ways, the first being from the client to the director. The second test is from the director back to the client. Just because the first test passes, doesn’t mean the second should work. Here are some things to try.
- Once you’ve installed your agent software, launch the bwc-console, which can be found in Start=>All Programs=>Bacula.
- When the console initializes, it will automatically try to connect to the Director and should display some information such as status. If you wish, you can run status dir to get the status again. The output should look as follows:
Cachengo-104C-dir Version: 3.0.3 (18 October 2009) x86_64-unknown-linux-gnu suse 11
Daemon started 27-Oct-09 15:36, 0 Jobs run since started.
Heap: heap=282,624 smbytes=68,749 max_bytes=69,634 bufs=230 max_bufs=238
- If the console is not connecting to the Director, then chances are good that the bwx-console.conf file is improperly configured. Most of the time the issue is the password is improperly set. But the IP address of the Director could be wrong. Or the Director name may be missing the -dir suffix too. Double check these values.
- To check whether the client is properly configured, type status client. You may have several clients configured. Be sure to select the right one from the menu option. If all is working well, you will see something as follows:
Connecting to Client windemo3-fd at windemo3:9102
windemo3-fd Version: 3.0.2 (18 July 2009) VSS Linux Cross-compile Win32
Daemon started 27-Oct-09 16:29, 0 Jobs run since started.
Heap: heap=0 smbytes=12,906 max_bytes=13,028 bufs=53 max_bufs=54
Sizeof: boffset_t=8 size_t=4 debug=0 trace=1
If the client is not configured properly, then you will very likely see the following:
Connecting to Client windemo3-fd at windemo3:9102
Failed to connect to Client windemo3-fd.
27-Oct 20:19 Cachengo-104C-dir JobId 0: Fatal error: Unable to authenticate with File daemon at “windemo3:9102″. Possible causes:
Passwords or names not the same or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000 for help.
If you’re receiving this message, then chances are very good you’ve mis-configured the bacula-fd.conf file on the client. In this case, the file is configured with the following Director entry:
Name = cachengo-104C-dir
Password = “demo411″
On the surface, everything looks fine with this file. However, the Director name is actually Cachengo-104C. Notice the name has a lower case letter as opposed to the upper case one.
- Assuming these are all set properly, you may have a firewall problem, which is blocking ports 9101 and 9102. You can always try to test this by opening up a telnet program and type telnet [ip address of client] 9102. You should receive some login confirmation such as:
Connected to 10.0.1.16.
Escape character is ‘^]’.
If you don’t, then there’s a good chance your problem is actually firewall related.
Note** any image can be enlarged by simply right clicking on it. When you unpacked your Cachengo Director, you should have received a copy of the Cachengo Media DVD. On that DVD is software for this installation. You’ll find the appropriate agent under Cachengo Media=> Backup Agent=> Win32=> winbacula-3.0.2.exe. Go head and locate this installer [...]
Note** any image can be enlarged by simply right clicking on it.
When you unpacked your Cachengo Director, you should have received a copy of the Cachengo Media DVD. On that DVD is software for this installation. You’ll find the appropriate agent under Cachengo Media=> Backup Agent=> Win32=> winbacula-3.0.2.exe.
- Go head and locate this installer and double click on it.
- Accept the license agreement.
- Do not accept the Automatic installer. Instead, click on custom and then Next.
- By default, the installer will install all program files in C:\Program Files\Bacula. Go ahead and accept the default, unless there’s not enough space on your drive.
- You will be prompted with a screen for properly configuring the client portion of the agent. The name of the client will be automatically generated based on the Computer Name of the system the agent is installed upon. Do not modify this unless you also plan to modify the computer name and DNS records. Also, leave the default port set to 9102. You may have reason to change the maximum number of jobs, but this can also be changed at a later time. For this purpose, just accept the default of 5.
Now, enter the password as “demo411″. The corresponding default password on the Director is already set to this password. If you try to enter anything else, changes will have to be made on the Director as well. Also, leave the default check marks for running Bacula as a service.
- The next screen will be used for configuring the details on the Director. In order to properly work, the client must have the proper information to find and to authenticate with the Director. Most of the information will be blank by default. This information will be filled in now. Also, we will override the hashed password that is automatically generated by the installer.
- Now, enter the proper information for the Director. Every unit has the Director name on top right corner of the server. In this case the Director’s name is Cachengo-104C. The name is case sensitive. Enter this information with the suffix “-dir”. This is very important. If the name is wrong or if the suffix is missing, then client will not properly authenticate. Also, the password must be “demo411″.
The Address is the Director IP address or DNS name. Either is fine to use. In this example, I’ve gone ahead and used the actual IP address of 10.0.1.14 for the Director. Lastly, in the Monitor section, we’ll need to set the password to “demo411″ again.
Now the client software should be fully configured and we can simply select the defaults for the rest of the installation wizard.
- To verify that the Bacula Client service is actually running, we’ll take a look at the Service panel under Administrative Tools.
Once you’ve pulled up the list of services, go ahead and located the one titled Bacula File Services. It should be listed as started. If it isn’t, then try to start it manually. If that fails, then it probably indicates that bacula-fd.exe wasn’t properly installed in C:/Program Files/Bacula/bin/. You may have to repeat the installation process.
- Assuming the service is properly running, it’s time to actually launch the bwx-console program in Programs=>Bacula to check the authentication between the Client and the Director. After launching the console, an input box should appear. Type in the following, but without the quotes: “status dir dir=cachengo-104c-dir”. Please substitute your own Director name. If the client is successful in finding and authenticating with the Director, information will be displayed on it’s version and configuration. If an error message appears, then something is not configured properly and you should contact firstname.lastname@example.org.