In the previous articles we've coved the installation of Bacula. In this one we will cover basic configuration, based on the installation locations we used before. If you have not read them I recommend that you pay a visit
Using Bacula with HP autoloaders | Basics
Using Bacula with HP autoloaders | Installation
Using Bacula with HP autoloaders | System Configs
Bacula consists of 3 parts - Director, Storage Daemon and File Daemon + additional 4th part GUI tools. Before we can use any of those we need to create the Catalog - MySQL db in our case. To do so we need to follow next 4 steps.
1. cd /usr/local/bacula/etc
2. ./create_bacula_database
3. ./make_bacula_tables
4. ./grant_mysql_privileges
To verify that all was completed successfully login in mysql server with administrative user and execute the following command :
mysql> show grants for bacula@localhost;
Output should look like this:
Using Bacula with HP autoloaders | Configuration
|
+------------------------------------------------------------+
| Grants for bacula@localhost |
+------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'bacula'@'localhost' |
| GRANT ALL PRIVILEGES ON `bacula`.* TO 'bacula'@'localhost' |
+------------------------------------------------------------+
Preliminary notes
We have several configuration files which we should be aware of. Each configuration files defines Resources (by Bacula terminology) which are used to connect to the other components. A Resource is a part of a configuration file that defines a specific unit of information that is available to Bacula. It consists of several directives (individual configuration statements).
For the following files we MUST have the resources as listed below:
bacula-dir.conf
We have several configuration files which we should be aware of. Each configuration files defines Resources (by Bacula terminology) which are used to connect to the other components. A Resource is a part of a configuration file that defines a specific unit of information that is available to Bacula. It consists of several directives (individual configuration statements).
For the following files we MUST have the resources as listed below:
bacula-dir.conf
-Director{} - defines the configuration for the Director
-JobDefs{} - defines Job options common for all jobs
-Job {} - defines individual jobs
-FileSet{} - defines files/dirs to backup and options for them
-Schedule{} - defines schedules when/how to backup
-Client{} - defines which individual clients to backup
-Storage{} - defines storage daemons
-Catalog{} - defines configuration of Catalog and file with SQL commands
-Messages{} - defines how to handle messages from the Bacula installation
-Pool{} - defines in which Pools to backup, i.e. on tape/disk/etc.
Next file on the configuration is bacula-sd.conf . Here is a description of its contents and a short description of the information the file contains.
-Storage{} - defines the configuration for the Storage Daemon (SD)
-Director{} - defines the Director which will connect to this SD as well as ACL for it
-Autochanger{} - defines parameters for our autochanger device
-Device{} - defines the actual device on which the autochanger will write,(the device in the tape)
We move to the configuration file for the File Daemon bacula-fd.conf
-Director{} - defines the director to which this FileDaemon (FD) is allowd to connect
-FileDaemon{} - defines the FD itself, with additional config params
-Messages{} - defines where this FD will send its messages
The last file we would look into is bconsole.conf
-Director{} - defines the director to which this console will connect
Next Tutorials
Post Comment
Need a specific tutorial? Do not hesitate and submit a request!
