Networking, Programming and Graphics - Tutorials
ONLINEHOWTO.net Tutorials Category

Using Bacula with HP autoloaders | Installation

Type: Code Networking, Programming and Graphics - Tutorials
Networking, Programming and Graphics - Tutorials
Level: Beginner Networking, Programming and Graphics - Tutorials 
Networking, Programming and Graphics - Tutorials
Date: 2009-Jun-30
Networking, Programming and Graphics - Tutorials
Visited: 902 times
Networking, Programming and Graphics - Tutorials
Rating: Networking, Programming and Graphics - Tutorials
Networking, Programming and Graphics - Tutorials
Published: Stephen Think

We continue the manual for Using Bacula with HP autoloaders. In case you have missed the first part I recommend that you read it here Using Bacula with HP autoloaders | Basics

Bacula uses 3 types of database servers, PostgreSQL, SQLite, Mysql to store it's catalog tables. For this manual we've chosen MySQL since it's widely available on all installations. The latter are used to store information about the running jobs, backups available, etc., etc. - i.e. all the system information needed for the proper functioning of the software. Prior to compiling and installing Bacula, you'll need to set up a mysql server.

1. Install MySQL

On the machine on which you are building the Director, Storage Daemon and the Client, you should at least have the header files from the dev package.

2. Compiling Bacula.

Current version of Bacula, as of this writing is 3.0.1. You can download it from: here

3. Once you have it, untar and use the following options to build it.

a) cd to where you extracted

CFLAGS="-g -Wall" 
 ./configure --prefix=/usr/local/bacula --disable-ipv6 --enable-smartalloc --enable-batch-insert --enable-largefile --with-mysql --with-openssl
 --enable-conio --enable-static --enable-includes  --enable-static-tools --enable-statis-fd --enable-static-sd --enable-static-dir 
 --enable-build-dird --enable-build-stored

The above command will configure the Director, Storage Daemon and the Client Daemon as static binaries.
You can then copy them to the appropriate machines provided that they are the same OS version as the one you used for building.


b) make and watch the output for errors, eventually you can redirect it to a file. There should be NO error in the output. For all of the build targets the output should look like:
 ==== Make of lib is good ====
 ==== Make of findlib is good ====
 ==== Make of filed is good ====
 ==== Make of console is good ====
 ==== Make of sqllib is good ====
 ==== Make of dird is good ====
 ===== Make of stored is good ====
 ==== Make of tools is good ====

c) Now run make install | awk '/====/ {print}'. Output of the command should look like this:

 ==== Make of lib is good ====
 ==== Make of findlib is good ====
 ==== Make of filed is good ====
 ==== Make of console is good ====
 ==== Make of sqllib is good ====
 ==== Make of dird is good ====
 ===== Make of stored is good ====

d) make install-autostart - this will create the symlinks in the init.d directory.

e) Your installation is now complete.
Rate this tutorial:                    
Post Comment

Need a specific tutorial? Do not hesitate and submit a request!
Your e-mail: