Installing the 64Bit Bacula Client on 64Bit Windows 7 1. The default download folder is the ‘Downloads’ folder under Favorites, next launch the installer. And click next to begin. Agree to the License Terms by clicking ‘I Agree’ 2. Next you need to select custom install…this will allow you to add your director and [...]
Installing the 64Bit Bacula Client on 64Bit Windows 7
1. The default download folder is the ‘Downloads’ folder under Favorites, next launch the installer. And click next to begin.
Agree to the License Terms by clicking ‘I Agree’
2. Next you need to select custom install…this will allow you to add your director and client information now during the install instead of later.
For the components screen make no changes as the defaults are ok.
3. The default location for installing is c:\program files. Choose the default install location unless you are out of disk space.
4. 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
5. 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
6. 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
(It’s important to note that Bacula now installs everything into the c:\program files directory.)
6. After the install you will need to navigate to the c:\programs files directory then right click on the bacula folder and make sure the account you plan to use has full control permissions under the security tab in properties. This will give you a pop-up to add permissions for access if you don’t all ready.
7. Next you will need to edit the bacula-fd file. There is a section at the end that defines the monitor setup and needs to be commented out. This section has not been fully ported to 64-bit and will keep the fd service from running. The bacula-fd file can be found in c:\program files\bacula\bacula-fd.conf
# Restricted Director, used by tray-monitor to get the
# status of the file daemon
# Name = @monitor_name@
# Password = “@monitor_password@”
# Monitor = yes
# Send all messages except skipped files back to Director
8. Now you should be able to manually start the Bacula-fd service by navigating to the windows task manger (ctrl-alt-delete)
Next click on the services button.
From here you can right click on the bacula-fd service and set the run level. For most setups the Automatic run level will work. You should only change this to manual if you have a specific reason to do so.
9. Before you can launch bconsole you need to make sure that c:\ProgramData\Bacula\bconsole.conf exists. If it doesn’t you can create it by copying the bconsole.conf file out of c:\program files\bacula into c:\ProgramData\Bacula.
Assuming the service is properly running, it’s time to actually launch the bconsole program in c:\Program Files=>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 email@example.com