\chapter{Manually Installing \bacula{}} \label{blb:InstallChapter} \index[general]{\bacula{}!Installing Manually} \index[general]{Manually Installing \bacula{}} In general, you will need the \bacula{} source release, and if you want to run a Windows client, you will need the \bacula{} Windows binary release. However, \bacula{} needs certain third party packages (such as \textbf{\mysql{}}, \textbf{\postgresql{}}, or \textbf{\sqlite{}} to build and run properly depending on the options you specify. Normally, \textbf{\mysql{}} and \textbf{\postgresql{}} are packages that can be installed on your distribution. However, if you do not have them, to simplify your task, we have combined a number of these packages into three \textbf{depkgs} releases (Dependency Packages). This can vastly simplify your life by providing you with all the necessary packages rather than requiring you to find them on the Web, load them, and install them. \section{Source Release Files} \index[general]{Source Files} \index[general]{Release Files} The \bacula{} source code has been broken into four separate tar files each corresponding to a different module in the \bacula{} \acs{SVN}. The released files are: \begin{bdescription} \item [\bfilename{bacula-5.2.0.tar.gz}] This is the primary source code release for \bacula{}. On each release the version number (5.2.0) will be updated. \item [\bfilename{bacula-docs-5.2.0.tar.bz2}] This file contains a copy of the docs directory with the documents prebuild. English HTML directory, single HTML file, and PDF file. The French, German, Spanish translations are in progress, but are not built. \item [\bfilename{bacula-gui-5.2.0.tar.gz}] This file contains the non-core \acs{GUI} programs. Currently, it contains bacula-web, a \acs{PHP} program for producing management viewing of your \bacula{} job status in a browser; and \btool{bimagemgr} a browser program for burning CDROM images with \bacula{} Volumes. \item [\bfilename{bacula-rescue-5.2.0.tar.gz}] This is the \bacula{} Rescue USB key code. Note, the version number of this package is not always tied to the \bacula{} release version, so it may be different. Using this code, you can create a USB key with your system configuration and containing a statically linked version of the File daemon. This can permit you to easily repartition and reformat your hard disks and reload your system with \bacula{} in the case of a hard disk failure. \item [\bfilename{win32bacula-5.2.0.exe}] This file is the 32 bit Windows installer for installing the Windows client (File daemon) on a Windows machine. This client will also run on 64 bit Windows machines, but \acs{VSS} support is not available if you are running a 64 bit version of Windows. This installer installs only the FD, the Director and Storage daemon are not included. \item [\bfilename{win64bacula-5.2.0.exe}] This file is the 64 bit Windows installer for installing the Windows client (File daemon) on a Windows machine. This client will only run on 64 bit Windows OS machines. It will not run on 32 bit machines or 32 bit Windows OSes. The win64bacula release is necessary for Volume Shadow Copy (\acs{VSS}) to work on Win64 OSes. This installer installs only the FD, the Director and Storage daemon are not included. \end{bdescription} \section{Building \bacula{} from Source} \label{blb:Building} \index[general]{Source!Building \bacula{} from} \index[general]{Building \bacula{} from Source} The basic installation is rather simple. \begin{benumerate} \item Install and build any \textbf{depkgs} as noted above. This should be unnecessary on most modern Operating Systems. \item Configure and install \mysql{} or \postgresql{} (if desired). \bxlink{Installing and Configuring \mysql{} Phase I}{blb:MySqlChapter}{main}{chapter} or \bxlink{Installing and Configuring \postgresql{} Phase I}{blb:PostgreSqlChapter}{main}{chapter} of the \bmainman{}. If you are installing from rpms, and are using \mysql{}, please be sure to install \textbf{mysql-devel}, so that the \mysql{} header files are available while compiling \bacula{}. In addition, the \mysql{} client library \textbf{mysqlclient} requires the gzip compression library \textbf{libz.a} or \textbf{libz.so}. If you are using rpm packages, these libraries are in the \textbf{libz-devel} package. On Debian systems, you will need to load the \textbf{zlib1g-dev} package. If you are not using rpms or debs, you will need to find the appropriate package for your system. Note, if you already have a running \mysql{} or \postgresql{} on your system, you can skip this phase provided that you have built the thread safe libraries. And you have already installed the additional rpms noted above. \sqlite{} is not supported on Solaris. This is because it frequently fails with bus errors. However \sqlite{}3 may work. \item Detar the \bacula{} source code preferably into the \textbf{bacula} directory discussed above. \item \btool{cd} to the directory containing the source code. \item \btool{./configure} (with appropriate options as described below). Any path names you specify as options on the \btool{./configure} command line must be absolute paths and not relative. \item Check the output of \btool{./configure} very carefully, especially the Install binaries and Install config directories. If they are not correct, please rerun \btool{./configure} until they are. The output from \btool{./configure} is stored in \bfilename{config.out} and can be re-displayed at any time without rerunning the \btool{./configure} by doing \btool{cat config.out}. \item If after running \btool{./configure} once, you decide to change options and re-run it, that is perfectly fine, but before re-running it, you should run: \begin{bVerbatim} make distclean \end{bVerbatim} so that you are sure to start from scratch and not have a mixture of the two options. This is because \btool{./configure} caches much of the information. The \btool{make distclean} is also critical if you move the source directory from one machine to another. If the \btool{make distclean} fails, just ignore it and continue on. \item make If you get errors while linking in the Storage daemon directory (\bdirectoryname{src/stored}), it is probably because you have not loaded the static libraries on your system. I noticed this problem on a Solaris system. To correct it, make sure that you have not added \textbf{\texttt{{-}{-}enable-static-tools}} to the \btool{./configure} command. If you skip this step (\btool{make}) and proceed immediately to the \btool{make install} you are making two serious errors: \begin{benumerate} \item your install will fail because \bacula{} requires a \btool{make} before a \btool{make install}. \item you are depriving yourself of the chance to make sure there are no errors before beginning to write files to your system directories. \end{benumerate} \item \btool{make install} Please be sure you have done a \btool{make} before entering this command, and that everything has properly compiled and linked without errors. \item If you are new to \bacula{}, we \textbf{strongly} recommend that you skip the next step and use the default configuration files, then run the example program in the next chapter, then come back and modify your configuration files to suit your particular needs. \item Customize the configuration files for each of the three daemons (Directory, File, Storage) and for the Console program. For the details of how to do this, please see \bxlink{Setting Up \bacula{} Configuration Files}{blb:ConfigureChapter}{main}{chapter} of the \bmainman{}. We recommend that you start by modifying the default configuration files supplied, making the minimum changes necessary. Complete customization can be done after you have \bacula{} up and running. Please take care when modifying passwords, which were randomly generated, and the \textbf{Name}s as the passwords and names must agree between the configuration files for security reasons. \label{blb:CreateDatabase} \item Create the \bacula{} \mysql{} database and tables (if using \mysql{}) \bxlink{Installing and Configuring \mysql{} Phase II}{blb:mysql_phase2}{main}{chapter} or create the \bacula{} \postgresql{} database and tables \bxlink{Configuring \postgresql{} II}{blb:PostgreSQL_configure}{main}{chapter} or alternatively if you are using \sqlite{} \bilink{Installing and Configuring \sqlite{} Phase II}{blb:sqlite_phase2}. \item Start \bacula{} (\btool{./bacula start}) Note. the next chapter shows you how to do this in detail. \item Interface with \bacula{} using the Console program \item For the previous two items, please follow the instructions in the \bilink{Running \bacula{}}{blb:TutorialChapter} chapter of this manual, where you will run a simple backup and do a restore. Do this before you make heavy modifications to the configuration files so that you are sure that \bacula{} works and are familiar with it. After that changing the conf files will be easier. \item If after installing \bacula{}, you decide to ``move it'', that is to install it in a different set of directories, proceed as follows: \begin{bVerbatim} make uninstall make distclean ./configure make make install \end{bVerbatim} \end{benumerate} If all goes well, the \btool{./configure} will correctly determine which operating system you are running and configure the source code appropriately. Currently, FreeBSD, Linux (Red Hat), and Solaris are supported. The \bacula{} client (File daemon) is reported to work with MacOS X 10.3 is if readline support is \bdefaultvalue{not enabled} (default) when building the client. If you install \bacula{} on more than one system, and they are identical, you can simply transfer the source tree to that other system and do a \btool{make install}. However, if there are differences in the libraries or OS versions, or you wish to install on a different OS, you should start from the original compress tar file. If you do transfer the source tree, and you have previously done a \btool{./configure} command, you \textbf{must} do: \begin{bVerbatim} make distclean \end{bVerbatim} prior to doing your new \btool{./configure}. This is because the \acs{GNU} \texttt{autoconf} tools cache the configuration, and if you re-use a configuration for a Linux machine on a Solaris, you can be sure your build will fail. To avoid this, as mentioned above, either start from the tar file, or do a \btool{make distclean}. In general, you will probably want to supply a more complicated \btool{configure} statement to ensure that the modules you want are built and that everything is placed into the correct directories. For example, on Fedora, Red Hat, or SuSE one could use the following: \begin{bVerbatim} CFLAGS="-g -Wall" \ ./configure \ --sbindir=/opt/bacula/bin \ --sysconfdir=/opt/bacula/etc \ --with-pid-dir=/var/run \ --with-subsys-dir=/var/run \ --with-mysql \ --with-working-dir=/opt/bacula/working \ --with-dump-email=$USER \end{bVerbatim} The advantage of using the above configuration to start is that everything will be put into a single directory, which you can later delete once you have run the examples in the next chapter and learned how \bacula{} works. In addition, the above can be installed and run as non-root. For the developer's convenience, I have added a \btool{defaultconfig} script to the \bdirectoryname{examples} directory. This script contains the statements that you would normally use, and each developer/user may modify them to suit his needs. You should find additional useful examples in this directory as well. The \textbf{\texttt{{-}{-}enable-conio}} or \textbf{\texttt{{-}{-}enable-readline}} options are useful because they provide a command line history, editing capability for the Console program and tab completion on various option. If you have included either option in the build, either the \textbf{\texttt{termcap}} or the \textbf{\texttt{ncurses}} package will be needed to link. On most systems, including Red Hat and SuSE, you should include the \texttt{ncurses} package. If \bacula{}'s configure process finds the \texttt{ncurses} libraries, it will use those rather than the \texttt{termcap} library. On some systems, such as SuSE, the \texttt{termcap} library is not in the standard library directory. As a consequence, the option may be disabled or you may get an error message such as: \begin{bVerbatim} /usr/lib/gcc-lib/i586-suse-linux/3.3.1/.../ld: cannot find -ltermcap collect2: ld returned 1 exit status \end{bVerbatim} while building the \bacula{} Console. In that case, you will need to set the \textbf{\texttt{LDFLAGS}} environment variable prior to building. \begin{bVerbatim} export LDFLAGS="-L/usr/lib/termcap" \end{bVerbatim} The same library requirements apply if you wish to use the \texttt{readline} subroutines for command line editing, history and tab completion or if you are using a \mysql{} library that requires encryption. If you need encryption, you can either export the appropriate additional library options as shown above or, alternatively, you can include them directly on the \btool{./configure} line as in: \begin{bVerbatim} LDFLAGS="-lssl -lcyrpto" \ ./configure \end{bVerbatim} On some systems such as Mandriva, \texttt{readline} tends to gobble up prompts, which makes it totally useless. If this happens to you, use the disable option, or if you are using version 1.33 and above try using \textbf{\texttt{{-}{-}enable-conio}} to use a built-in \texttt{readline} replacement. You will still need either the \texttt{termcap} or the \texttt{ncurses} library, but it is unlikely that the \textbf{\texttt{conio}} package will gobble up prompts. \texttt{readline} is no longer supported after version 1.34. The code within \bacula{} remains, so it should be usable, and if users submit patches for it, we will be happy to apply them. However, due to the fact that each version of \texttt{readline} seems to be incompatible with previous versions, and that there are significant differences between systems, we can no longer afford to support it. \section{Quick Start} \index[general]{Quick Start} \index[general]{Start!Quick} There are a number of options and important considerations given below that you can skip for the moment if you have not had any problems building \bacula{} with a simplified configuration as shown above. If the \btool{./configure} process is unable to find specific libraries (e.g. \texttt{libintl}, you should ensure that the appropriate package is installed on your system. Alternatively, if the package is installed in a non-standard location (as far as \bacula{} is concerned), then there is generally an option listed below (or listed with \btool{./configure {-}{-}help} that will permit you to specify the directory that should be searched. In other cases, there are options that will permit you to disable to feature (e.g. \texttt{{-}{-}disable-nls}). If you want to dive right into it, we recommend you skip to the next chapter, and run the example program. It will teach you a lot about \bacula{} and as an example can be installed into a single directory (for easy removal) and run as non-root. If you have any problems or when you want to do a real installation, come back to this chapter and read the details presented below. \section{Configure Options} \label{blb:Options} \index[general]{Options!Configure} \index[general]{Configure Options} The following command line options are available for \btool{configure} to customize your installation. \begin{bdescription} \item [ {-}{-}prefix=\bbracket{patch}] \index[general]{{-}{-}prefix} This option is meant to allow you to direct where the architecture independent files should be placed. However, we find this a somewhat vague concept, and so we have not implemented this option other than to use any explicit prefix that you may define. If you do not explicitly specify a prefix, \bacula{}'s configure routine will not use the default value that \btool{./configure {-}{-}help} prints. As a consequence, we suggest that you avoid it. We have provided options that allow you to explicitly specify the directories for each of the major categories of installation files. \item [ {-}{-}sbindir=\bbracket{binary-path}] \index[general]{{-}{-}sbindir} Defines where the \bacula{} binary (executable) files will be placed during a \btool{make install} command. \item [ {-}{-}sysconfdir=\bbracket{config-path}] \index[general]{{-}{-}sysconfdir} Defines where the \bacula{} configuration files should be placed during a \btool{make install} command. Note, for security reasons, this directory should be unique to \bacula{} and not read/writable by any other user/group than \texttt{bacula} is running under. \item [ {-}{-}mandir=\bbracket{path}] \index[general]{{-}{-}mandir} Note, as of \bacula{} version 1.39.14, the meaning of any path specified on this option is change from prior versions. It now specifies the top level man directory. Previously the mandir specified the full path to where you wanted the man files installed. The man files will be installed in gzip'ed format under \bdirectoryname{mandir/man1} and \bdirectoryname{mandir/man8} as appropriate. For the install to succeed you must have \btool{gzip} installed on your system. By default, \bacula{} will install the Unix man pages in \bdirectoryname{/usr/share/man/man1} and \bdirectoryname{/usr/share/man/man8}. If you wish the man page to be installed in a different location, use this option to specify the path. Note, the main HTML and PDF \bacula{} documents are in a separate tar file that is not part of the source distribution. \item [ {-}{-}datadir=\bbracket{path} ] \index[general]{{-}{-}datadir} If you translate \bacula{} or parts of \bacula{} into a different language you may specify the location of the po files using the \textbf{\texttt{{-}{-}datadir}} option. You must manually install any po files as \bacula{} does not (yet) automatically do so. \item [ {-}{-}disable-ipv6 ] \index[general]{{-}{-}disable-ipv6} \item [ {-}{-}enable-smartalloc ] \index[general]{{-}{-}enable-smartalloc} This enables the inclusion of the Smartalloc orphaned buffer detection code. This option is highly recommended. Because we never build without this option, you may experience problems if it is not enabled. In this case, simply re-enable the option. We strongly recommend keeping this option enabled as it helps detect memory leaks. This configuration parameter is used while building \bacula{} \item [ {-}{-}enable-bat ] \label{blb:enablebat} \index[general]{{-}{-}enable-bat} If you have Qt4 >= 4.3.4 installed on your computer including the \btool{libqt4} and \btool{libqt4-devel} (\btool{libqt4-dev} on Debian) libraries, and you want to use the \bat{} (\acl{BAT}) \acs{GUI} Console interface to \bacula{}, you must specify this option. Doing so will build everything in the \bdirectoryname{src/qt-console} directory. The build with enable-bat will work only with a full \bacula{} build (i.e. it will not work with a client-only build). Qt4 is available on OpenSUSE 10.2, CentOS 5, Fedora, and Debian. If it is not available on your system, you can download the \btool{depkgs-qt} package from the \bacula{} Source Forge download area and build it. See the \bfilename{INSTALL} file in that package for more details. In particular to use the Qt4 built by \textbf{depkgs-qt} you \textbf{must} source the file \bfilename{qt4-paths}. \item [ {-}{-}enable-batch-insert ] \index[general]{{-}{-}enable-batch-insert} This option enables batch inserts of the attribute records (default) in the catalog database, which is much faster (10 times or more) than without this option for large numbers of files. However, this option will automatically be disabled if your \acs{SQL} libraries are not thread safe. If you find that batch mode is not enabled on your \bacula{} installation, then your database most likely does not support threads. \sqlite{}2 is not thread safe. Batch insert cannot be enabled when using \sqlite{}2 On most systems, \mysql{}, \postgresql{} and \sqlite{}3 are thread safe. To verify that your \postgresql{} is thread safe, you can try this (change the path to point to your particular installed \bfilename{libpq.a}; these commands were issued on FreeBSD 6.2): \begin{bVerbatim} $ nm /usr/local/lib/libpq.a | grep PQputCopyData 00001b08 T PQputCopyData $ nm /usr/local/lib/libpq.a | grep mutex U pthread_mutex_lock U pthread_mutex_unlock U pthread_mutex_init U pthread_mutex_lock U pthread_mutex_unlock \end{bVerbatim} The above example shows a \btool{libpq} that contains the required function \texttt{PQputCopyData} and is thread enabled (i.e. the \texttt{pthread\_mutex}* entries). If you do not see \texttt{PQputCopyData}, your version of \postgresql{} is too old to allow batch insert. If you do not see the mutex entries, then thread support has not been enabled. Our tests indicate you usually need to change the configuration options and recompile/reinstall the \postgresql{} client software to get thread support. \bacula{} always links to the thread safe \mysql{} libraries. Running with Batch Insert turned on is recommended because it can significantly improve attribute insertion times. However, it does put a significantly larger part of the work on your \acs{SQL} engine, so you may need to pay more attention to tuning it. In particular, Batch Insert can require large temporary table space, and consequently, the default location (often \bdirectoryname{/tmp}) may run out of space causing errors. For \mysql{}, the location is set in \bfilename{my.conf} with ``tmpdir''. You may also want to increase the memory available to your \acs{SQL} engine to further improve performance during Batch Inserts. \item [ {-}{-}enable-bwx-console ] \index[general]{{-}{-}enable-bwx-console} If you have wxWidgets installed on your computer and you want to use the wxWidgets \acs{GUI} Console interface to \bacula{}, you must specify this option. Doing so will build everything in the \bdirectoryname{src/wx-console} directory. This could also be useful to users who want a \acs{GUI} Console and don't want to install QT, as wxWidgets can work with GTK+, Motif or even X11 libraries. \item [ {-}{-}enable-tray-monitor ] \index[general]{{-}{-}enable-tray-monitor} If you have \acs{GTK} installed on your computer, you run a graphical environment or a window manager compatible with the FreeDesktop system tray standard (like KDE and GNOME) and you want to use a \acs{GUI} to monitor \bacula{} daemons, you must specify this option. Doing so will build everything in the \bdirectoryname{src/tray-monitor} directory. Note, due to restrictions on what can be linked with \acs{GPL}ed code, we were forced to remove the egg code that dealt with the tray icons and replace it by calls to the GTK+ API, and unfortunately, the tray icon API necessary was not implemented until GTK version 2.10 or later. \item [ {-}{-}enable-static-tools] \index[general]{{-}{-}enable-static-tools} This option causes the linker to link the Storage daemon utility tools (\btool{bls}, \btool{bextract}, and \btool{bscan}) statically. This permits using them without having the shared libraries loaded. If you have problems linking in the \textbf{src/stored} directory, make sure you have not enabled this option, or explicitly disable static linking by adding \textbf{\texttt{{-}{-}disable-static-tools}}. \item [ {-}{-}enable-static-fd] \index[general]{{-}{-}enable-static-fd} This option causes the make process to build a \textbf{static-bacula-fd} in addition to the standard File daemon. This static version will include statically linked libraries and is required for the Bare Metal recovery. This option is largely superseded by using \btool{make static-bacula-fd} from with in the \bdirectoryname{src/filed} directory. Also, the \textbf{\texttt{{-}{-}enable-client-only}} option described below is useful for just building a client so that all the other parts of the program are not compiled. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure you do not specify \textbf{\texttt{{-}{-}openssl}} or other options on your \btool{./configure} statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. \item [ {-}{-}enable-static-sd] \index[general]{{-}{-}enable-static-sd} This option causes the make process to build a \textbf{static-bacula-sd} in addition to the standard Storage daemon. This static version will include statically linked libraries and could be useful during a Bare Metal recovery. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure you do not specify \textbf{\texttt{{-}{-}openssl}} or other options on your \btool{./configure} statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. \item [ {-}{-}enable-static-dir] \index[general]{{-}{-}enable-static-dir} This option causes the make process to build a \textbf{static-bacula-dir} in addition to the standard Director. This static version will include statically linked libraries and could be useful during a Bare Metal recovery. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure you do not specify \textbf{\texttt{{-}{-}openssl}} or other options on your \btool{./configure} statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. \item [ {-}{-}enable-static-cons] \index[general]{{-}{-}enable-static-cons} This option causes the make process to build a \textbf{static-console} in addition to the standard console. This static version will include statically linked libraries and could be useful during a Bare Metal recovery. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure you do not specify \textbf{\texttt{{-}{-}openssl}} or other options on your \btool{./configure} statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. \item [ {-}{-}enable-client-only] \index[general]{{-}{-}enable-client-only} This option causes the make process to build only the File daemon and the libraries that it needs. None of the other daemons, storage tools, nor the console will be built. Likewise a \btool{make install} will then only install the File daemon. To cause all daemons to be built, you will need to do a configuration without this option. This option greatly facilitates building a Client on a client only machine. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used. The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure you do not specify \textbf{\texttt{{-}{-}openssl}} or other options on your \btool{./configure} statement as these options require additional libraries. You may be able to enable those options, but you will need to load additional static libraries. \item [ {-}{-}enable-build-dird] \index[general]{{-}{-}enable-build-dird} This option causes the make process to build the Director and the Director's tools. By default, this option is on, but you may turn it off by using \textbf{\texttt{{-}{-}disable-build-dird}} to prevent the Director from being built. \item [ {-}{-}enable-build-stored] \index[general]{{-}{-}enable-build-stored} This option causes the make process to build the Storage daemon. By default, this option is on, but you may turn it off by using \textbf{\texttt{{-}{-}disable-build-stored}} to prevent the Storage daemon from being built. \item [ {-}{-}enable-largefile] \index[general]{{-}{-}enable-largefile} This option (default) causes \bacula{} to be built with 64 bit file address support if it is available on your system. This permits \bacula{} to read and write files greater than 2 GBytes in size. You may disable this feature and revert to 32 bit file addresses by using \textbf{\texttt{{-}{-}disable-largefile}}. \item [ {-}{-}disable-nls] \index[general]{{-}{-}disable-nls} By default, \bacula{} uses the \acs{GNU} \ac{NLS} libraries. On some machines, these libraries may not be present or may not function correctly (especially on non-Linux implementations). In such cases, you may specify \textbf{\texttt{{-}{-}disable-nls}} to disable use of those libraries. In such a case, \bacula{} will revert to using English. \item [ {-}{-}disable-ipv6 ] \index[general]{{-}{-}disable-ipv6} By default, \bacula{} enables IPv6 protocol. On some systems, the files for IPv6 may exist, but the functionality could be turned off in the kernel. In that case, in order to correctly build \bacula{}, you will explicitly need to use this option so that \bacula{} does not attempt to reference OS function calls that do not exist. \item [ {-}{-}with-sqlite3=\bbracket{sqlite3-path}] \index[general]{{-}{-}with-sqlite3} This enables use of the \sqlite{} version 3.x database. The \textbf{sqlite3-path} is not normally specified as \bacula{} looks for the necessary components in a standard location (\textbf{depkgs/sqlite3}). See \bilink{Installing and Configuring \sqlite{}}{blb:SqlLiteChapter} chapter of this manual for more details. \sqlite{}3 is not supported on Solaris. \item [ {-}{-}with-mysql=\bbracket{mysql-path}] \index[general]{{-}{-}with-mysql} This enables building of the Catalog services for \bacula{}. It assumes that \mysql{} is running on your system, and expects it to be installed in the \textbf{mysql-path} that you specify. Normally, if \mysql{} is installed in a standard system location, you can simply use \textbf{\texttt{{-}{-}with-mysql}} with no path specification. If you do use this option, please proceed to installing \mysql{} in the \bxlink{Installing and Configuring \mysql{}}{blb:MySqlChapter}{main}{chapter} before proceeding with the configuration. See the note below under the \texttt{{-}{-}with-postgresql} item. \item [ {-}{-}with-postgresql=\bbracket{path}] \index[general]{{-}{-}with-postgresql} This provides an explicit path to the \postgresql{} libraries if \bacula{} cannot find it by default. Normally to build with \postgresql{}, you would simply use \textbf{\texttt{{-}{-}with-postgresql}}. Note, for \bacula{} to be configured properly, you must specify one of the four database options supported. That is: \texttt{{-}{-}with-sqlite}, \texttt{{-}{-}with-sqlite3}, \texttt{{-}{-}with-mysql}, or \texttt{{-}{-}with-postgresql}, otherwise the \btool{./configure} will fail. \item [ {-}{-}with-openssl=\bbracket{path}] This configuration option is necessary if you want to enable \acs{TLS} (ssl), which encrypts the communications within \bacula{} or if you want to use File Daemon \acs{PKI} data encryption. Normally, the \textbf{path} specification is not necessary since the configuration searches for the OpenSSL libraries in standard system locations. However, you must ensure that all the libraries are loaded including \btool{libssl-dev} or the equivalent on your system. Enabling OpenSSL in \bacula{} permits secure communications between the daemons and/or data encryption in the File daemon. For more information on using \acs{TLS}, please see the \bilink{\bacula{} \acs{TLS} -- Communications Encryption}{blb:CommEncryption} chapter of this manual. For more information on using \acs{PKI} data encryption, please see the \bilink{\bacula{} \acs{PKI} -- Data Encryption}{blb:DataEncryption} chapter of this manual. If you get errors linking, you need to load the development libraries, or you need to disable SSL by setting without-openssl. \item [ {-}{-}with-libintl-prefix=\bbracket{DIR}] \index[general]{{-}{-}with-libintl-prefix} This option may be used to tell \bacula{} to search DIR/include and DIR/lib for the libintl headers and libraries needed for \ac{NLS}. \item [ {-}{-}enable-conio] \index[general]{{-}{-}enable-conio} Tells \bacula{} to enable building the small, light weight \texttt{readline} replacement routine. It is generally much easier to configure than \texttt{readline}, although, like \texttt{readline}, it needs either the \texttt{termcap} or \texttt{ncurses} library. \item [ {-}{-}with-\texttt{readline}=\bbracket{\texttt{readline}-path}] \index[general]{{-}{-}with-\texttt{readline}} Tells \bacula{} where \textbf{\texttt{readline}} is installed. Normally, \bacula{} will find \texttt{readline} if it is in a standard library. If it is not found and no {-}{-}with-\texttt{readline} is specified, \texttt{readline} will be disabled. This option affects the \bacula{} build. \texttt{readline} provides the Console program with a command line history and editing capability and is no longer supported, so you are on your own if you have problems. \item [ {-}{-}enable-\texttt{readline}] \index[general]{{-}{-}enable-\texttt{readline}} Tells \bacula{} to enable \texttt{readline} support. It is normally disabled due to the large number of configuration problems and the fact that the package seems to change in incompatible ways from version to version. \item [ {-}{-}with-tcp-wrappers=\bbracket{path}] \index[general]{{-}{-}with-tcp-wrappers} \index[general]{TCP Wrappers} \index[general]{Wrappers!TCP} \index[general]{libwrappers} This specifies that you want TCP wrappers (man hosts\_access(5)) compiled in. The path is optional since \bacula{} will normally find the libraries in the standard locations. This option affects the \bacula{} build. In specifying your restrictions in the \bfilename{/etc/hosts.allow} or \bfilename{/etc/hosts.deny} files, do not use the \textbf{twist} option (hosts\_options(5)) or the \bacula{} process will be terminated. Note, when setting up your \bfilename{/etc/hosts.allow} or \bfilename{/etc/hosts.deny}, you must identify the \bacula{} daemon in question with the name you give it in your conf file rather than the name of the executable. For more information on configuring and testing TCP wrappers, please see the \bilink{Configuring and Testing TCP Wrappers}{blb:wrappers} section in the Security Chapter. On SuSE, the libwrappers libraries needed to link \bacula{} are contained in the tcpd-devel package. On Red Hat, the package is named tcp\_wrappers. \item [ {-}{-}with-archivedir=\bbracket{path} ] \index[general]{{-}{-}with-archivedir} The directory used for disk-based backups. Default value is /tmp. This parameter sets the default values in the bacula-dir.conf and bacula-sd.conf configuration files. For example, it sets the Where directive for the default restore job and the Archive Device directive for the FileStorage device. This option is designed primarily for use in regression testing. Most users can safely ignore this option. \item [ {-}{-}with-working-dir=\bbracket{working-directory-path} ] \index[general]{{-}{-}with-working-dir} This option is mandatory and specifies a directory into which \bacula{} may safely place files that will remain between \bacula{} executions. For example, if the internal database is used, \bacula{} will keep those files in this directory. This option is only used to modify the daemon configuration files. You may also accomplish the same thing by directly editing them later. The working directory is not automatically created by the install process, so you must ensure that it exists before using \bacula{} for the first time. \item [ {-}{-}with-baseport=\bbracket{port=number}] \index[general]{{-}{-}with-baseport} In order to run, \bacula{} needs three TCP/IP ports (one for the \bacula{} Console, one for the Storage daemon, and one for the File daemon). The \textbf{\texttt{{-}{-}with-baseport}} option will automatically assign three ports beginning at the base port address specified. You may also change the port number in the resulting configuration files. However, you need to take care that the numbers correspond correctly in each of the three daemon configuration files. The default base port is 9101, which assigns ports 9101 through 9103. These ports (9101, 9102, and 9103) have been officially assigned to \bacula{} by IANA. This option is only used to modify the daemon configuration files. You may also accomplish the same thing by directly editing them later. \item [ {-}{-}with-dump-email=\bbracket{email-address}] \index[general]{{-}{-}with-dump-email} This option specifies the email address where any core dumps should be set. This option is normally only used by developers. \item [ {-}{-}with-pid-dir=\bbracket{PATH} ] \index[general]{{-}{-}with-pid-dir} This specifies where \bacula{} should place the process id file during execution. The default is: \bdirectoryname{/var/run}. This directory is not created by the install process, so you must ensure that it exists before using \bacula{} the first time. \item [ {-}{-}with-subsys-dir=\bbracket{PATH}] \index[general]{{-}{-}with-subsys-dir} This specifies where \bacula{} should place the subsystem lock file during execution. The default is \bdirectoryname{/var/run/subsys}. Please make sure that you do not specify the same directory for this directory and for the \bdirectoryname{sbindir} directory. This directory is used only within the autostart scripts. The subsys directory is not created by the \bacula{} install, so you must be sure to create it before using \bacula{}. \item [ {-}{-}with-dir-password=\bbracket{Password}] \index[general]{{-}{-}with-dir-password} This option allows you to specify the password used to access the Director (normally from the Console program). If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-fd-password=\bbracket{Password} ] \index[general]{{-}{-}with-fd-password} This option allows you to specify the password used to access the File daemon (normally called from the Director). If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-sd-password=\bbracket{Password} ] \index[general]{{-}{-}with-sd-password} This option allows you to specify the password used to access the Storage daemon (normally called from the Director). If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-dir-user=\bbracket{User} ] \index[general]{{-}{-}with-dir-user} This option allows you to specify the Userid used to run the Director. The Director must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the UserId specified on this option. If you specify this option, you must create the User prior to running \btool{make install}, because the working directory owner will be set to \textbf{User}. \item [ {-}{-}with-dir-group=\bbracket{Group} ] \index[general]{{-}{-}with-dir-group} This option allows you to specify the GroupId used to run the Director. The Director must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the GroupId specified on this option. If you specify this option, you must create the Group prior to running \btool{make install}, because the working directory group will be set to \textbf{Group}. \item [ {-}{-}with-sd-user=\bbracket{User} ] \index[general]{{-}{-}with-sd-user} This option allows you to specify the Userid used to run the Storage daemon. The Storage daemon must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the UserId specified on this option. If you use this option, you will need to take care that the Storage daemon has access to all the devices (tape drives, ...) that it needs. \item [ {-}{-}with-sd-group=\bbracket{Group} ] \index[general]{{-}{-}with-sd-group} This option allows you to specify the GroupId used to run the Storage daemon. The Storage daemon must be started as root, but doesn't need to run as root, and after doing preliminary initializations, it can "drop" to the GroupId specified on this option. \item [ {-}{-}with-fd-user=\bbracket{User} ] \index[general]{{-}{-}with-fd-user} This option allows you to specify the Userid used to run the File daemon. The File daemon must be started as root, and in most cases, it needs to run as root, so this option is used only in very special cases, after doing preliminary initializations, it can "drop" to the UserId specified on this option. \item [ {-}{-}with-fd-group=\bbracket{Group} ] \index[general]{{-}{-}with-fd-group} This option allows you to specify the GroupId used to run the File daemon. The File daemon must be started as root, and in most cases, it must be run as root, however, after doing preliminary initializations, it can "drop" to the GroupId specified on this option. \item [ {-}{-}with-mon-dir-password=\bbracket{Password}] \index[general]{{-}{-}with-mon-dir-password} This option allows you to specify the password used to access the Directory from the monitor. If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-mon-fd-password=\bbracket{Password} ] \index[general]{{-}{-}with-mon-fd-password} This option allows you to specify the password used to access the File daemon from the Monitor. If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-mon-sd-password=\bbracket{Password} ] \index[general]{{-}{-}with-mon-sd-password} This option allows you to specify the password used to access the Storage daemon from the Monitor. If it is not specified, configure will automatically create a random password. \item [ {-}{-}with-db-name=\bbracket{database-name} ] \index[general]{{-}{-}with-db-name} This option allows you to specify the database name to be used in the conf files. The default is bacula. \item [ {-}{-}with-db-user=\bbracket{database-user} ] \index[general]{{-}{-}with-db-user} This option allows you to specify the database user name to be used in the conf files. The default is bacula. \end{bdescription} Note, many other options are presented when you do a \btool{./configure {-}{-}help}, but they are not implemented. \section{Recommended Options for Most Systems} \index[general]{Systems!Recommended Options for Most} \index[general]{Recommended Options for Most Systems} For most systems, we recommend starting with the following options: \begin{bVerbatim} ./configure \ --enable-smartalloc \ --sbindir=/opt/bacula/bin \ --sysconfdir=/opt/bacula/etc \ --with-pid-dir=/opt/bacula/working \ --with-subsys-dir=/opt/bacula/working \ --with-working-dir=/opt/bacula/working \end{bVerbatim} If you want to install \bacula{} in an installation directory rather than run it out of the build directory (as developers will do most of the time), you should also include the \texttt{{-}{-}sbindir} and \texttt{{-}{-}sysconfdir} options with appropriate paths. Neither are necessary if you do not use "make install" as is the case for most development work. The install process will create the sbindir and sysconfdir if they do not exist, but it will not automatically create the pid-dir, subsys-dir, or working-dir, so you must ensure that they exist before running \bacula{} for the first time. \section{Red Hat} \index[general]{Red Hat} Using \sqlite{}: \begin{bVerbatim} CFLAGS="-g -Wall" \btool{./configure} \ --sbindir=/opt/bacula/bin \ --sysconfdir=/opt/bacula/etc \ --enable-smartalloc \ --with-sqlite=$HOME/bacula/depkgs/sqlite \ --with-working-dir=/opt/bacula/working \ --with-pid-dir=/opt/bacula/working \ --with-subsys-dir=/opt/bacula/working \ --enable-bat \ --enable-\texttt{readline} \end{bVerbatim} or \begin{bVerbatim} CFLAGS="-g -Wall" \btool{./configure} \ --sbindir=/opt/bacula/bin \ --sysconfdir=/opt/bacula/etc \ --enable-smartalloc \ --with-mysql \ --with-working-dir=/opt/bacula/working --with-pid-dir=/opt/bacula/working \ --with-subsys-dir=/opt/bacula/working --enable-\texttt{readline} \end{bVerbatim} or finally, a completely traditional Red Hat Linux install, which we do not recommend, because it make it harder to backup \bacula{} for disaster recovery purposes: \begin{bVerbatim} CFLAGS="-g -Wall" \btool{./configure} \ --sbindir=/usr/sbin \ --sysconfdir=/etc/bacula \ --with-scriptdir=/etc/bacula \ --enable-smartalloc \ --enable-bat \ --with-mysql \ --with-working-dir=/var/bacula \ --with-pid-dir=/var/run \ --enable-\texttt{readline} \end{bVerbatim} Note, \bacula{} assumes that /var/bacula, /var/run, and /var/lock/subsys exist so it will not automatically create them during the install process. \section{Solaris} \index[general]{Solaris} To build \bacula{} from source, you will need the following installed on your system (they are not by default): libiconv, gcc 3.3.2, stdc++, libgcc (for stdc++ and gcc\_s libraries), make 3.8 or later. You will probably also need to: Add /usr/local/bin to PATH and Add /usr/ccs/bin to PATH for ar. It is possible to build \bacula{} on Solaris with the Solaris compiler, but we recommend using GNU C++ if possible. A typical configuration command might look like: \begin{bVerbatim} #!/bin/sh CFLAGS="-g" \btool{./configure} \ --sbindir=/opt/bacula/bin \ --sysconfdir=/opt/bacula/etc \ --with-mysql \ --enable-smartalloc \ --with-pid-dir=/opt/bacula/working \ --with-subsys-dir=/opt/bacula/working \ --with-working-dir=/opt/bacula/working \end{bVerbatim} Note, you may need to install the following packages to build \bacula{} from source: \begin{bVerbatim} SUNWbinutils, SUNWarc, SUNWhea, SUNWGcc, SUNWGnutls SUNWGnutls-devel SUNWGmake SUNWgccruntime SUNWlibgcrypt SUNWzlib SUNWzlibs SUNW\texttt{readline} SUNWbinutilsS SUNWGmakeS SUNWlibm export PATH=/usr/bin::/usr/ccs/bin:/etc:/usr/openwin/bin:/usr/local/bin:/usr/sfw/bin:/opt/sfw/bin:/usr/ucb:/usr/sbin \end{bVerbatim} If you have installed special software not normally in the Solaris libraries, such as OpenSSL, or the packages shown above, then you may need to add \bdirectoryname{/usr/sfw/lib} to the library search path. Probably the simplest way to do so is to run: \begin{bVerbatim} setenv LDFLAGS "-L/usr/sfw/lib -R/usr/sfw/lib" \end{bVerbatim} Prior to running the \btool{./configure} command. Alternatively, you can set the LD\_LIBARY\_PATH and/or the LD\_RUN\_PATH environment variables appropriately. It is also possible to use the \btool{crle} program to set the library search path. However, this should be used with caution. \section{FreeBSD} \index[general]{FreeBSD} Please see: \bref{http://www.freebsddiary.org/bacula.php}{The FreeBSD Diary} for a detailed description on how to make \bacula{} work on your system. In addition, users of FreeBSD prior to 4.9-STABLE dated Mon Dec 29 15:18:01 2003 UTC who plan to use tape devices, please see the \bxlink{Tape Testing}{blb:FreeBSDTapes}{problems}{section} of \bproblemman{} for \textbf{important} information on how to configure your tape drive for compatibility with \bacula{}. If you are using \bacula{} with \mysql{}, you should take care to compile \mysql{} with FreeBSD native threads rather than LinuxThreads, since \bacula{} is normally built with FreeBSD native threads rather than LinuxTreads. Mixing the two will probably not work. \section{Win32} \index[general]{Win32} To install the binary Win32 version of the File daemon please see the \bilink{Win32 Installation Chapter}{blb:Win32Chapter} in this document. \section{One File Configure Script} \index[general]{Script!One File Configure} \index[general]{One Files Configure Script} The following script could be used if you want to put everything in a single directory (except for the working directory): \begin{bVerbatim} #!/bin/sh CFLAGS="-g -Wall" \ \btool{./configure} \ --sbindir=$HOME/bacula/bin \ --sysconfdir=$HOME/bacula/bin \ --mandir=$HOME/bacula/bin \ --enable-smartalloc \ --enable-bat \ --with-pid-dir=$HOME/bacula/bin/working \ --with-subsys-dir=$HOME/bacula/bin/working \ --with-mysql \ --with-working-dir=$HOME/bacula/bin/working \ --with-dump-email=$USER@your-site.com \ --with-job-email=$USER@your-site.com \ --with-smtp-host=mail.your-site.com exit 0 \end{bVerbatim} You may also want to put the following entries in your \bfilename{/etc/services} file as it will make viewing the connections made by \bacula{} easier to recognize (i.e. netstat -a): \begin{bVerbatim} bacula-dir 9101/tcp bacula-fd 9102/tcp bacula-sd 9103/tcp \end{bVerbatim} \section{Installing \bacula{}} \index[general]{\bacula{}!Installing} \index[general]{Installing \bacula{}} Before setting up your configuration files, you will want to install \bacula{} in its final location. Simply enter: \begin{bVerbatim} make install \end{bVerbatim} If you have previously installed \bacula{}, the old binaries will be overwritten, but the old configuration files will remain unchanged, and the "new" configuration files will be appended with a \textbf{.new}. Generally if you have previously installed and run \bacula{} you will want to discard or ignore the configuration files with the appended \textbf{.new}. \section{Building a File Daemon or Client} \index[general]{Client!Building a File Daemon or} \index[general]{Building a File Daemon or Client} If you run the Director and the Storage daemon on one machine and you wish to back up another machine, you must have a copy of the File daemon for that machine. If the machine and the Operating System are identical, you can simply copy the \bacula{} File daemon binary file \bfilename{bacula-fd} as well as its configuration file \bfilename{bacula-fd.conf} then modify the name and password in the conf file to be unique. Be sure to make corresponding additions to the Director's configuration file (\bfilename{bacula-dir.conf}). If the architecture or the OS level are different, you will need to build a File daemon on the Client machine. To do so, you can use the same \btool{./configure} command as you did for your main program, starting either from a fresh copy of the source tree, or using \btool{make\ distclean} before the \btool{./configure}. Since the File daemon does not access the Catalog database, you can remove the \textbf{\texttt{{-}{-}with-mysql}} or \textbf{\texttt{{-}{-}with-sqlite}} options, then add \textbf{\texttt{{-}{-}enable-client-only}}. This will compile only the necessary libraries and the client programs and thus avoids the necessity of installing one or another of those database programs to build the File daemon. With the above option, you simply enter \btool{make} and just the client will be built. \label{blb:autostart} \section{Auto Starting the Daemons} \index[general]{Daemons!Auto Starting the} \index[general]{Auto Starting the Daemons} If you wish the daemons to be automatically started and stopped when your system is booted (a good idea), one more step is necessary. First, the ./configure process must recognize your system -- that is it must be a supported platform and not \textbf{unknown}, then you must install the platform dependent files by doing: \begin{bVerbatim} (become root) make install-autostart \end{bVerbatim} Please note, that the auto-start feature is implemented only on systems that we officially support (currently, FreeBSD, Red Hat/Fedora Linux, and Solaris), and has only been fully tested on Fedora Linux. The \btool{make install-autostart} will cause the appropriate startup scripts to be installed with the necessary symbolic links. On Red Hat/Fedora Linux systems, these scripts reside in \btool{/etc/rc.d/init.d/bacula-dir}, \btool{/etc/rc.d/init.d/bacula-fd}, and \btool{/etc/rc.d/init.d/bacula-sd}. However the exact location depends on what operating system you are using. If you only wish to install the File daemon, you may do so with: \begin{bVerbatim} make install-autostart-fd \end{bVerbatim} \section{Other Make Notes} \index[general]{Notes!Other Make} \index[general]{Other Make Notes} To simply build a new executable in any directory, enter: \begin{bVerbatim} make \end{bVerbatim} To clean out all the objects and binaries (including the files named 1, 2, or 3, which are development temporary files), enter: \begin{bVerbatim} make clean \end{bVerbatim} To really clean out everything for distribution, enter: \begin{bVerbatim} make distclean \end{bVerbatim} note, this cleans out the Makefiles and is normally done from the top level directory to prepare for distribution of the source. To recover from this state, you must redo the \btool{./configure} in the top level directory, since all the Makefiles will be deleted. To add a new file in a subdirectory, edit the Makefile.in in that directory, then simply do a \btool{make}. In most cases, the make will rebuild the Makefile from the new Makefile.in. In some case, you may need to issue the \btool{make} a second time. In extreme cases, cd to the top level directory and enter: \btool{make Makefiles}. To add dependencies: \begin{bVerbatim} make depend \end{bVerbatim} The \btool{make depend} appends the header file dependencies for each of the object files to \bfilename{Makefile} and \bfilename{Makefile.in}. This command should be done in each directory where you change the dependencies. Normally, it only needs to be run when you add or delete source or header files. \btool{make depend} is normally automatically invoked during the configuration process. To install: \begin{bVerbatim} make install \end{bVerbatim} This not normally done if you are developing \bacula{}, but is used if you are going to run it to back up your system. After doing a \btool{make install} the following files will be installed on your system (more or less). The exact files and location (directory) for each file depends on your \btool{./configure} command (e.g. if you are using \sqlite{} instead of \mysql{}, some of the files will be different). NOTE: it is quite probable that this list is out of date. But it is a starting point. \begin{bVerbatim} bacula bacula-dir bacula-dir.conf bacula-fd bacula-fd.conf bacula-sd bacula-sd.conf bacula-tray-monitor tray-monitor.conf bextract bls bscan btape btraceback btraceback.gdb bconsole bconsole.conf create_mysql_database dbcheck delete_catalog_backup drop_bacula_tables drop_mysql_tables make_bacula_tables make_catalog_backup make_mysql_tables mtx-changer query.sql bsmtp startmysql stopmysql bwx-console bwx-console.conf 9 man pages \end{bVerbatim} \label{blb:monitor} \section{Installing Tray Monitor} \index[general]{Monitor!Installing Tray} \index[general]{Installing Tray Monitor} The Tray Monitor is already installed if you used the \textbf{\texttt{{-}{-}enable-tray-monitor}} configure option and ran \btool{make install}. As you don't run your graphical environment as \texttt{root} (if you do, you should change that bad habit), don't forget to allow your user to read \bfilename{tray-monitor.conf}, and to execute \btool{bacula-tray-monitor} (this is not a security issue). Then log into your graphical environment (KDE, GNOME or something else), run \btool{bacula-tray-monitor} as your user, and see if a cassette icon appears somewhere on the screen, usually on the task bar. If it doesn't, follow the instructions below related to your environment or window manager. \subsection{GNOME} \index[general]{GNOME} System tray, or notification area if you use the GNOME terminology, has been supported in GNOME since version 2.2. To activate it, right-click on one of your panels, open the menu \textbf{Add to this Panel}, then \textbf{Utility} and finally click on \textbf{Notification Area}. \subsection{KDE} \index[general]{KDE} System tray has been supported in KDE since version 3.1. To activate it, right-click on one of your panels, open the menu \textbf{Add}, then \textbf{Applet} and finally click on \textbf{System Tray}. \subsection{Other Window Managers} \index[general]{Managers!Other window} \index[general]{Other window managers} Read the documentation to know if the Freedesktop system tray standard is supported by your window manager, and if applicable, how to activate it. \section{Modifying the \bacula{} Configuration Files} \index[general]{Modifying the \bacula{} Configuration Files} \index[general]{Files!Modifying the \bacula{} Configuration} See the chapter \bilink{Configuring \bacula{}}{blb:ConfigureChapter} in this manual for instructions on how to set \bacula{} configuration files.