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 {\bf SQLite}, {\bf MySQL}
+Bacula needs certain third party packages (such as {\bf SQLite}, {\bf MySQL}, or
+{\bf PostgreSQL}
to build properly depending on the options you specify. To simplify your task,
we have combined a number of these packages into two {\bf 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.
-\label{upgrading1}
+\subsection*{Source Release Files}
+\index[general]{Source Files}
+\index[general]{Release Files}
+\addcontentsline{toc}{subsection}{Source Release File}
+Beginning with Bacula 1.38.0, the source code has been broken into
+four separate tar files each corresponding to a different module in
+the Bacula CVS. The released files are:
+
+\begin{description}
+\item [bacula-1.38.0.tar.gz]
+ This is the primary source code release for Bacula. On each
+ release the version number (1.38.0) will be updated.
+
+\item [bacula-docs-1.38.0.tar.gz]
+ This file contains a copy of the docs directory with the
+ documents prebuild. English html directory, single html
+ file, and pdf file. The French and German translations
+ are in progress, but are not built.
+
+\item [bacula-gui-1.38.0.tar.gz]
+ This file contains the non-core GUI programs. Currently,
+ it contains bacula-web, a PHP program for producing management
+ viewing of your Bacula job status in a browser; and bimagemgr
+ a browser program for burning CDROM images with Bacula Volumes.
+
+\item [bacula-rescue-1.8.1.tar.gz]
+ This is the Bacula Rescue CDROM code. Note, the version number
+ of this package is not tied to the Bacula release version, so
+ it will be different. Using this code, you can burn a CDROM
+ 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.
+
+\end{description}
+
+\label{upgrading1}
\subsection*{Upgrading Bacula}
\index[general]{Bacula!Upgrading }
\index[general]{Upgrading Bacula }
and the version to which you are upgrading. If the Bacula catalog database has
been upgraded, you will either need to reinitialize your database starting
from scratch, or save an ASCII copy of your database, then proceed to upgrade
-it. If there are several database upgrades between your version and the
+it. This is normally done after Bacula is build and installed by:
+
+\begin{verbatim}
+cd <installed-scripts-dir> (default /etc/bacula)
+./update_bacula_tables
+\end{verbatim}
+
+This update script can also be find in the Bacula source src/cats
+directory.
+
+If there are several database upgrades between your version and the
version to which you are upgrading, you will need to apply each database
upgrade script. For your convenience, you can find all the old upgrade scripts
in the {\bf upgradedb} directory of the source code. You will need to edit the
scripts to correspond to your system configuration. The final upgrade script,
-if any, will be in the {\bf src/cats} directory as described in the
-ReleaseNotes.
+if any, can be applied as noted above.
If you are upgrading from one major version to another, you will need to
replace all your components at the same time as generally the inter-daemon
Finally, please note that in general it is not necessary to do a
{\bf make uninstall} before doing an upgrade. In fact, if you do so, you will
most likely delete all your conf files, which could be disastrous.
+The normal procedure during an upgrade is simply {\bf make install}.
+In general none of your existing .conf or .sql files will be overwritten.
+
For additional information on upgrading, please see the \ilink{Upgrading Bacula
Versions}{upgrading} in the Tips chapter of this manual.
\item Detar the {\bf depkg} into the {\bf bacula} directory.
\item cd bacula/depkgs
\item make
- \end{enumerate}
+\end{enumerate}
Although the exact composition of the dependency packages may change from time
to time, the current makeup is the following:
-\addcontentsline{lot}{table}{Depedency Packages}
+\addcontentsline{lot}{table}{Dependency Packages}
\begin{longtable}{|l|l|l|l|}
\hline
\multicolumn{1}{|c| }{\bf 3rd Party Package } & \multicolumn{1}{c| }{\bf
\multicolumn{1}{c| }{X } \\
\hline {zlib } & \multicolumn{1}{c| }{- } & \multicolumn{1}{c| }{- } &
\multicolumn{1}{c| }{X } \\
- \hline {wxWidgits } & \multicolumn{1}{c| }{- } & \multicolumn{1}{c| }{- } &
+ \hline {wxWidgets } & \multicolumn{1}{c| }{- } & \multicolumn{1}{c| }{- } &
\multicolumn{1}{c| }{X }
\\ \hline
with valuable information about your SCSI tape drive (e.g. compression,
min/max block sizes, ...).
-The {\bf depkgs-win32} package contains the source code for the pthreads and
-zlib libraries used by the native Win32 client program. It will only be needed
-if you intend to build the Win32 client from source.
+The {\bf depkgs-win32} package contains the source code for the pthreads,
+zlib, and wxWidgets libraries used by the native Win32 client program. It
+will only be needed if you intend to build the Win32 client from source.
\subsection*{Supported Operating Systems}
\label{Systems}
in the {\bf libz-devel} package. On Debian systems, you will need to load the
{\bf 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.
+
\item As an alternative to MySQL and PostgreSQL, configure and install SQLite,
which is part of the {\bf depkgs}.
\ilink{Installing and Configuring SQLite}{_ChapterStart33}.
- \item Detar the Bacula source code preferably into the {\bf bacula} directory
+
+\item Detar the Bacula source code preferably into the {\bf bacula} directory
discussed above.
+
\item {\bf cd} to the directory containing the source code.
+
\item ./configure (with appropriate options as described below)
+
\item Check the output of ./configure very carefully, especially the Install
binaries and Install config directories. If they are not correct,
please rerun ./configure until they are. The output from ./configure is
stored in {\bf config.out} and can be re-displayed at any time without
rerunning the ./configure by doing {\bf cat config.out}.
+
\item If after running ./configure once, you decide to change options and
re-run it, that is perfectly fine, but before re-running it, you should run:
\footnotesize
\begin{verbatim}
make distclean
-
\end{verbatim}
\normalsize
so that you are sure to start from scratch and not have a mixture of the two
options. This is because ./configure caches much of the information. The {\bf
-make distclean} is also critical if you move the source dirctory from one
+make distclean} is also critical if you move the source directory from one
machine to another. If the {\bf make distclean} fails, just ignore it and
continue on.
+
\item make
+ If you get errors while linking in the Storage daemon directory
+ (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 {\bf
+ {-}{-}enable-static-tools} to the {\bf ./configure} command.
- If you get errors while linking in the Storage daemon directory (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 {\bf \verb{--{enable-static-tools} to the {\bf ./configure}
-command.
\item make install
-\item If you are new to Bacula, we {\bf 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 If you are new to Bacula, we {\bf 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
-\ilink{Setting Up Bacula Configuration Files}{_ChapterStart16} in
-the Configuration chapter of this manual. 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 {\bf Name}s as the passwords and names must agree
-between the configuration files for security reasons.
-\item Create the Bacula MySQL database and tables (if using MySQL)
- \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or
- create the Bacula PostgreSQL database and tables
-\ilink{Installing and Configuring PostgreSQL Phase
-II}{PostgreSQL_phase2} or alternatively if you are using
-SQLite
-\ilink{Installing and Configuring SQLite Phase II}{phase2}.
+ (Directory, File, Storage) and for the Console program. For the details
+ of how to do this, please see \ilink{Setting Up Bacula Configuration
+ Files}{_ChapterStart16} in the Configuration chapter of this manual. 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 {\bf Name}s
+ as the passwords and names must agree between the configuration files
+ for security reasons. \item Create the Bacula MySQL database and tables
+ (if using MySQL)
+ \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or
+ create the Bacula PostgreSQL database and tables
+ \ilink{Installing and Configuring PostgreSQL Phase
+ II}{PostgreSQL_phase2} or alternatively if you are using
+ SQLite
+ \ilink{Installing and Configuring SQLite Phase II}{phase2}.
+
\item Start Bacula ({\bf ./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
\ilink{Running Bacula}{_ChapterStart1} 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
+ 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:
\footnotesize
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 ``make
-install''. However, if there are differences in the libraries or OS versions,
+simply transfer the source tree to that other system and do a "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 ./configure command, you MUST do:
prior to doing your new ./configure. This is because the GNU 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 ``make distclean''.
+mentioned above, either start from the tar file, or do a "make distclean".
In general, you will probably want to supply a more complicated {\bf
configure} statement to ensure that the modules you want are built and that
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 {\bf \verb{--{enable-conio} or {\bf \verb{--{enable-readline} options are useful because
+The {\bf \verb:--:enable-conio} or {\bf \verb:--:enable-readline} options are useful because
they provide a command line history and editing capability for the Console
program. If you have included either option in the build, either the {\bf
termcap} or the {\bf ncurses} package will be needed to link. On some systems,
On some systems such as Mandriva, 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 {\bf
-\verb{--{enable-conio} to use a built-in readline replacement. You will still need
+\verb:--:enable-conio} to use a built-in readline replacement. You will still need
either the termcap or the ncurses library, but it is unlikely that the {\bf conio}
package will gobble up prompts.
continuing with the configuration of Bacula. PostgreSQL is very similar to
MySQL, though it tends to be slightly more SQL92 compliant and has many more
advanced features such as transactions, stored procedures, and the such. It
-requires a certain knowledge to install and maintain. There are some important
-performance problems with PostgreSQL in Bacula versions prior to 1.35.5.
+requires a certain knowledge to install and maintain.
If you wish to use SQLite as the Bacula catalog, please see
\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
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 ./configure process is unable to find specific libraries (e.g.
+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 "./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. {-}{-}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
customize your installation.
\begin{description}
-
-\item [ \verb?--?sysbindir=\lt{}binary-path\gt{}]
- \index[dir]{\verb{--{sysbindir }
+\item [ {-}{-}sysbindir=\lt{}binary-path\gt{}]
+ \index[general]{{-}{-}sysbindir }
Defines where the Bacula binary (executable) files will be placed during a
{\bf make install} command.
-\item [ \verb?--?sysconfdir=\lt{}config-path\gt{}]
- \index[dir]{\verb{--{sysconfdir }
- Defines where the Bacula configuration files should be placed during a {\bf
- make install} command.
-
-\item [ \verb?--?enable-smartalloc ]
- \index[dir]{\verb{--{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 [ \verb?--?enable-gnome ]
- \index[dir]{\verb{--{enable-gnome }
- If you have GNOME installed on your computer and you want to use the GNOME
- GUI Console interface to Bacula, you must specify this option. Doing so will
- build everything in the {\bf src/gnome-console} directory.
-
-\item [ \verb?--?enable-wx-console ]
- \index[console]{\verb{--{enable-wx-console }
- If you have wxWidgets installed on your computer and you want to use the
- wxWidgets GUI Console interface to Bacula, you must specify this option.
- Doing so will build everything in the {\bf src/wx-console} directory. This
- could also be useful to users who want a GUI Console and don't want to
- install Gnome, as wxWidgets can work with GTK+, Motif or even X11 libraries.
-
-
-\item [ \verb?--?enable-tray-monitor ]
- \index[dir]{\verb{--{enable-tray-monitor }
- If you have 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 GUI to monitor Bacula daemons, you
- must specify this option. Doing so will build everything in the {\bf
- src/tray-monitor} directory.
-
-\item [ \verb?--?enable-static-tools]
- \index[dir]{\verb{--{enable-static-tools }
- This option causes the linker to link the Storage daemon utility tools ({\bf
- bls}, {\bf bextract}, and {\bf bscan}) statically. This permits using them
- without having the shared libraries loaded. If you have problems linking in
- the {\bf src/stored} directory, make sure you have not enabled this option,
- or explicitly disable static linking by adding {\bf \verb{--{disable-static-tools}.
-
-
-\item [ \verb?--?enable-static-fd]
- \index[fd]{\verb{--{enable-static-fd }
- This option causes the make process to build a {\bf 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 {\bf make static-bacula-fd} from with
- in the {\bf src/filed} directory. Also, the {\bf \verb{--{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.
-
-\item [ \verb?--?enable-static-sd]
- \index[sd]{\verb{--{enable-static-sd }
- This option causes the make process to build a {\bf 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.
+\item [ {-}{-}sysconfdir=\lt{}config-path\gt{}]
+ \index[general]{{-}{-}sysconfdir }
+ Defines where the Bacula configuration files should be placed during a
+ {\bf make install} command.
+
+\item [ {-}{-}mandir=\lt{}path\gt{}]
+ \index[general]{{-}{-}mandir}
+ By default, Bacula will install a simple Unix man page in
+ /usr/share/man. 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=\lt{}path\gt{}]
+ \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 {\bf
+ {-}{-}datadir} option. You must manually install any po files as
+ Bacula does not (yet) automatically do so.
+
+
+\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-gnome ]
+ \index[general]{{-}{-}enable-gnome }
+ If you have GNOME installed on your computer and you want to use the
+ GNOME GUI Console interface to Bacula, you must specify this option.
+ Doing so will build everything in the {\bf src/gnome-console} directory.
+
+\item [ {-}{-}enable-wx-console ]
+ \index[general]{{-}{-}enable-wx-console }
+ If you have wxWidgets installed on your computer and you want to use the
+ wxWidgets GUI Console interface to Bacula, you must specify this option.
+ Doing so will build everything in the {\bf src/wx-console} directory.
+ This could also be useful to users who want a GUI Console and don't want
+ to install Gnome, as wxWidgets can work with GTK+, Motif or even X11
+ libraries.
+
+
+\item [ {-}{-}enable-tray-monitor ]
+ \index[general]{{-}{-}enable-tray-monitor }
+ If you have 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 GUI to monitor
+ Bacula daemons, you must specify this option. Doing so will build
+ everything in the {\bf src/tray-monitor} directory.
+
+\item [ {-}{-}enable-static-tools]
+ \index[general]{{-}{-}enable-static-tools }
+ This option causes the linker to link the Storage daemon utility tools
+ ({\bf bls}, {\bf bextract}, and {\bf bscan}) statically. This permits
+ using them without having the shared libraries loaded. If you have
+ problems linking in the {\bf src/stored} directory, make sure you have
+ not enabled this option, or explicitly disable static linking by adding
+ {\bf \verb:--:disable-static-tools}.
+
+
+\item [ {-}{-}enable-static-fd]
+ \index[general]{{-}{-}enable-static-fd }
+ This option causes the make process to build a {\bf 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 {\bf make static-bacula-fd}
+ from with in the {\bf src/filed} directory. Also, the {\bf
+ \verb:--: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 {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./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 {\bf 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 {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./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 [ \verb?--?enable-static-dir]
- \index[dir]{\verb{--{enable-static-dir }
- This option causes the make process to build a {\bf 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.
-
-
-\item [ \verb?--?enable-static-cons]
- \index[dir]{\verb{--{enable-static-cons }
- This option causes the make process to build a {\bf static-console} and a
- {\bf static-gnome-console} in addition to the standard console. This static
- version will include statically linked libraries and could be useful during a
- Bare Metal recovery.
-
-\item [ \verb?--?enable-client-only]
- \index[console]{\verb{--{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 {\bf 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.
-
-\item [ \verb?--?enable-largefile]
- \index[console]{\verb{--{enable-largefile }
+\item [ {-}{-}enable-static-dir]
+ \index[general]{{-}{-}enable-static-dir }
+ This option causes the make process to build a {\bf 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 {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./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 {\bf static-console} and
+ a {\bf static-gnome-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 {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./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 {\bf 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 {\bf {-}{-}openssl} or {\bf {-}{-}with-python}
+ on your ./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-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 {\bf \verb{--{disable-largefile}.
-
-\item [ \verb?--?with-sqlite=\lt{}sqlite-path\gt{}]
- \index[fd]{\verb{--{with-sqlite }
- This enables use of the SQLite database. The {\bf sqlite-path} is not
+ revert to 32 bit file addresses by using {\bf \verb:--:disable-largefile}.
+
+\item [ {-}{-}disable-nls]
+ \index[general]{{-}{-}disable-nls}
+ By default, Bacula uses the GNU Native Language Support (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 {\bf {-}{-}disable-nls} to disable use of those libraries.
+ In such a case, Bacula will revert to using English.
+
+\item [ {-}{-}with-sqlite=\lt{}sqlite-path\gt{}]
+ \index[general]{{-}{-}with-sqlite }
+ This enables use of the SQLite version 2.8.x database. The {\bf sqlite-path} is not
normally specified as Bacula looks for the necessary components in a
standard location ({\bf depkgs/sqlite}). See
\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
this manual for more details.
-\item [ \verb?--?with-mysql=\lt{}mysql-path\gt{}]
- \index[fd]{\verb{--{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 {\bf
- mysql-path} that you specify. If this option is not present, the build will
- automatically include the internal Bacula database code. We recommend that
- you use this option if possible. If you do use this option, please proceed to
- installing MySQL in the
- \ilink{Installing and Configuring MySQL}{_ChapterStart} chapter
- before proceeding with the configuration.
-
-\item [ \verb?--?with-postgresql=\lt{}path\gt{}]
- \index[fd]{\verb{--{with-postgresql }
- This provides an explicit path to the PostgreSQL libraries if Bacula cannot
- find it by default.
-
-\item [ \verb?--?with-python=\lt{}path\gt{}]
- \index[fd]{\verb{--{with-python }
+ See the note below under the {-}{-}with-postgresql item.
+
+\item [ {-}{-}with-sqlite3=\lt{}sqlite3-path\gt{}]
+ \index[general]{{-}{-}with-sqlite3 }
+ This enables use of the SQLite version 3.x database. The {\bf
+ sqlite3-path} is not normally specified as Bacula looks for the
+ necessary components in a standard location ({\bf depkgs/sqlite3}). See
+ \ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
+ this manual for more details.
+
+\item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}]
+ \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 {\bf mysql-path} that you specify. Normally, if MySQL is installed
+ in a standard system location, you can simply use {\bf {-}{-}with-mysql}
+ with no path specification. If you do use this option, please proceed
+ to installing MySQL in the \ilink{Installing and Configuring
+ MySQL}{_ChapterStart} chapter before proceeding with the configuration.
+
+ See the note below under the {-}{-}with-postgresql item.
+
+\item [ {-}{-}with-postgresql=\lt{}path\gt{}]
+ \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 {\bf {-}{-}with-postgresql}.
+
+ Note, for Bacula to be configured properly, you must specify one
+ of the four database options supported. That is:
+ {-}{-}with-sqlite, {-}{-}with-sqlite3, {-}{-}with-mysql, or
+ {-}{-}with-postgresql, otherwise the ./configure will fail.
+
+\item [ {-}{-}with-openssl=\lt{}path\gt{}]
+ This configuration option is necessary if you want to enable TLS (ssl)
+ in Bacula. Normally, the {\bf path} specification is not necessary since
+ the configuration searches for the OpenSSL libraries in standard system
+ locations. Enabling OpenSSL in Bacula permits secure communications
+ between the daemons. For more information on using TLS, please see the
+ \ilink{Bacula TLS}{_ChapterStart61} chapter of this manual.
+
+
+\item [ {-}{-}with-python=\lt{}path\gt{}]
+ \index[general]{{-}{-}with-python }
This option enables Bacula support for Python. If no path is
supplied, configure will search the
standard library locations for Python 2.2, 2.3, or 2.4. If it cannot
\ilink{Python chapter}{_ChapterStart60} for the details of using
Python scripting.
-\item [ \verb?--?enable-conio]
- \index[fd]{\verb{--{enable-conio }
- Tells Bacula to enable building the small, light weight readline replacement
- routine. It is generally much easier to configure than readline, although,
- like readline, it needs either the termcap or ncurses library.
-
-\item [ \verb?--?with-readline=\lt{}readline-path\gt{}]
- \index[fd]{\verb{--{with-readline }
- Tells Bacula where {\bf readline} is installed. Normally, Bacula will find
- readline if it is in a standard library. If it is not found and no
- \verb{--{with-readline is specified, readline will be disabled. This option affects
- the Bacula build. 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 [ \verb?--?enable-readline]
- \index[fd]{\verb{--{enable-readline }
+\item [ {-}{-}with-libintl-prefix=\lt{}DIR\gt{}]
+ \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 Native
+ Language Support (NLS).
+
+\item [ {-}{-}enable-conio]
+ \index[general]{{-}{-}enable-conio }
+ Tells Bacula to enable building the small, light weight readline
+ replacement routine. It is generally much easier to configure than
+ readline, although, like readline, it needs either the termcap or
+ ncurses library.
+
+\item [ {-}{-}with-readline=\lt{}readline-path\gt{}]
+ \index[general]{{-}{-}with-readline }
+ Tells Bacula where {\bf readline} is installed. Normally, Bacula will
+ find readline if it is in a standard library. If it is not found and no
+ {-}{-}with-readline is specified, readline will be disabled. This
+ option affects the Bacula build. 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-readline]
+ \index[general]{{-}{-}enable-readline }
Tells Bacula to enable 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 [ \verb?--?with-tcp-wrappers=\lt{}path\gt{}]
- \index[fd]{\verb{--{with-tcp-wrappers }
+\item [ {-}{-}with-tcp-wrappers=\lt{}path\gt{}]
+ \index[general]{{-}{-}with-tcp-wrappers }
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
\ilink{Configuring and Testing TCP Wrappers}{wrappers} section
in the Security Chapter.
-\item [ \verb?--?with-working-dir=\lt{}working-directory-path\gt{} ]
- \index[dir]{\verb{--{with-working-dir }
+\item [ {-}{-}with-working-dir=\lt{}working-directory-path\gt{} ]
+ \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
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 [ \verb?--?with-base-port=\lt{}port=number\gt{}]
- \index[dir]{\verb{--{with-base-port }
+\item [ {-}{-}with-base-port=\lt{}port=number\gt{}]
+ \index[general]{{-}{-}with-base-port }
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 {\bf
- \verb{--{with-baseport} option will automatically assign three ports beginning at
+ \verb:--: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
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 [ \verb?--?with-dump-email=\lt{}email-address\gt{}]
- \index[dir]{\verb{--{with-dump-email }
+\item [ {-}{-}with-dump-email=\lt{}email-address\gt{}]
+ \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 [ \verb?--?with-pid-dir=\lt{}PATH\gt{} ]
- \index[dir]{\verb{--{with-pid-dir }
+\item [ {-}{-}with-pid-dir=\lt{}PATH\gt{} ]
+ \index[general]{{-}{-}with-pid-dir }
This specifies where Bacula should place the process id file during
execution. The default is: {\bf /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 [ \verb?--?with-subsys-dir=\lt{}PATH\gt{}]
- \index[dir]{\verb{--{with-subsys-dir }
+\item [ {-}{-}with-subsys-dir=\lt{}PATH\gt{}]
+ \index[general]{{-}{-}with-subsys-dir }
This specifies where Bacula should place the subsystem lock file during
execution. The default is {\bf /var/run/subsys}. Please make sure that you do
not specify the same directory for this directory and for the {\bf sbindir}
subsys directory is not created by the Bacula install, so you must be sure to
create it before using Bacula.
-\item [ \verb?--?with-dir-password=\lt{}Password\gt{}]
- \index[dir]{\verb{--{with-dir-password }
+\item [ {-}{-}with-dir-password=\lt{}Password\gt{}]
+ \index[general]{{-}{-}with-dir-password }
This option allows you to specify the password used to access the Directory
(normally from the Console program). If it is not specified, configure will
automatically create a random password.
-\item [ \verb?--?with-fd-password=\lt{}Password\gt{} ]
- \index[fd]{\verb{--{with-fd-password }
+\item [ {-}{-}with-fd-password=\lt{}Password\gt{} ]
+ \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 [ \verb?--?with-sd-password=\lt{}Password\gt{} ]
- \index[sd]{\verb{--{with-sd-password }
+\item [ {-}{-}with-sd-password=\lt{}Password\gt{} ]
+ \index[general]{{-}{-}with-sd-password }
This option allows you to specify the password used to access the Directory
(normally called from the Director). If it is not specified, configure will
automatically create a random password.
-\item [ \verb?--?with-dir-user=\lt{}User\gt{} ]
- \index[dir]{\verb{--{with-dir-user }
+\item [ {-}{-}with-dir-user=\lt{}User\gt{} ]
+ \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
+ doing preliminary initializations, it can "drop" to the UserId specified on
this option.
-\item [ \verb?--?with-dir-group=\lt{}Group\gt{} ]
- \index[dir]{\verb{--{with-dir-group }
+\item [ {-}{-}with-dir-group=\lt{}Group\gt{} ]
+ \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
+ doing preliminary initializations, it can "drop" to the GroupId specified
on this option.
-\item [ \verb?--?with-sd-user=\lt{}User\gt{} ]
- \index[sd]{\verb{--{with-sd-user }
+\item [ {-}{-}with-sd-user=\lt{}User\gt{} ]
+ \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
+ 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 [ \verb?--?with-sd-group=\lt{}Group\gt{} ]
- \index[sd]{\verb{--{with-sd-group }
+\item [ {-}{-}with-sd-group=\lt{}Group\gt{} ]
+ \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
+ and after doing preliminary initializations, it can "drop" to the GroupId
specified on this option.
-\item [ \verb?--?with-fd-user=\lt{}User\gt{} ]
- \index[fd]{\verb{--{with-fd-user }
+\item [ {-}{-}with-fd-user=\lt{}User\gt{} ]
+ \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
+ preliminary initializations, it can "drop" to the UserId specified on this
option.
-\item [ \verb?--?with-fd-group=\lt{}Group\gt{} ]
- \index[fd]{\verb{--{with-fd-group }
+\item [ {-}{-}with-fd-group=\lt{}Group\gt{} ]
+ \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
+ root, however, after doing preliminary initializations, it can "drop" to
the GroupId specified on this option.
\end{description}
-Note, many other options are presented when you do a {\bf ./configure \verb{--{help},
-but they are not implemented.
+Note, many other options are presented when you do a {\bf ./configure
+\verb:--:help}, but they are not implemented.
\subsection*{Recommended Options for most Systems}
\index[general]{Systems!Recommended Options for most }
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 \verb{--{sbindir and \verb{--{sysconfdir options with appropriate
-paths. Neither are necessary if you do not use ``make install'' as is the case
+should also include the \verb:--:sbindir and \verb:--: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
Note, Bacula assumes that /var/bacula, /var/run, and /var/loc/subsys exist so
it will not automatically create them during the install process.
+Note, with gcc (GCC) 4.0.1 20050727 (Red Hat 4.0.1-5) on
+an AMD64 CPU running 64 bit CentOS4, there is a compiler bug that generates
+bad code that causes Bacula to segment fault. Typically you will see this
+in the Storage daemon first. The solution is to compile Bacula ensuring
+that no optimization is turned on (normally it is -O2).
+
\subsection*{Solaris}
\index[general]{Solaris }
\addcontentsline{toc}{subsection}{Solaris}
subsys-dir, or working-dir, so you must ensure that they exist before running
Bacula for the first time.
+Note, you may need to install the following packages to build Bacula
+from source:
+\footnotesize
+\begin{verbatim}
+SUNWbinutils,
+SUNWarc,
+SUNWhea,
+SUNWGcc,
+SUNWGnutls
+SUNWGnutls-devel
+SUNWGmake
+SUNWgccruntime
+SUNWlibgcrypt
+SUNWzlib
+SUNWzlibs
+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{verbatim}
+\normalsize
+
\subsection*{FreeBSD}
\index[general]{FreeBSD }
\addcontentsline{toc}{subsection}{FreeBSD}
\addcontentsline{toc}{subsection}{Windows Systems with CYGWIN Installed}
As of version 1.34, Bacula no longer uses CYGWIN for the Win32 File daemon.
-However, it is still built under a CYGWIN build environment -- though you can
-probably do it with VC Studio only. If you wish to build the Win32 File daemon
-from the source, you will need Microsoft C++ version 6.0 or greater. In Bacula
-prior to version 1.33, CYGWIN was used. Details for building it are in the
-README.win32 file of the src/win32 directory.
+However, it is still built under a CYGWIN build environment -- though you
+can probably do it with VC Studio only. If you wish to build the Win32
+File daemon from the source, you will need Microsoft C++ version 7.1.
+Details for building the Win32 FD are in the README.win32 file of the
+src/win32 directory.
Note, although most parts of Bacula build on Windows systems, the only part
that we have tested and used is the File daemon.
\index[general]{Kern's Configure Script }
\addcontentsline{toc}{subsection}{Kern's Configure Script}
-The script that I use for building on my ``production'' Linux machines is:
+The script that I use for building on my "production" Linux machines is:
\footnotesize
\begin{verbatim}
because they have been officially assigned to Bacula by IANA (Internet
Assigned Numbers Authority). We strongly recommend that you use only these
ports to prevent any conflicts with other programs. This is in fact the
-default if you do not specify a {\bf \verb{--{with-baseport} option.
+default if you do not specify a {\bf \verb:--:with-baseport} option.
You may also want to put the following entries in your {\bf /etc/services}
file as it will make viewing the connections made by Bacula easier to
\normalsize
If you have previously installed Bacula, the old binaries will be overwritten,
-but the old configuration files will remain unchanged, and the ``new''
+but the old configuration files will remain unchanged, and the "new"
configuration files will be appended with a {\bf .new}. Generally if you have
previously installed and run Bacula you will want to discard or ignore the
configuration files with the appended {\bf .new}.
fresh copy of the source tree, or using {\bf make\ distclean} before the {\bf
./configure}.
-Since the File daemon does not access the Catalog database, you can remove the
-{\bf \verb{--{with-mysql} or {\bf \verb{--{with-sqlite} options, then add {\bf
-\verb{--{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 {\bf make} and just the client will be built.
-\label{autostart}
+Since the File daemon does not access the Catalog database, you can remove
+the {\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then
+add {\bf \verb:--: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 {\bf make} and just the
+client will be built.
+\label{autostart}
\subsection*{Auto Starting the Daemons}
\index[general]{Daemons!Auto Starting the }
\index[general]{Auto Starting the Daemons }
\end{verbatim}
\normalsize
-Please note, that the auto-start feature is implemented only on systems that
-we officially support (currently, FreeBSD, RedHat Linux, and Solaris), and has
-only been fully tested on RedHat Linux.
+Please note, that the auto-start feature is implemented only on systems
+that we officially support (currently, FreeBSD, RedHat/Fedora Linux, and
+Solaris), and has only been fully tested on Fedora Linux.
-The {\bf make install-autostart} will cause the appropriate startup scripts to
-be installed with the necessary symbolic links. On RedHat Linux systems, these
-scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
-/etc/rc.d/init.d/bacula-fd}, and {\bf /etc/rc.d/init.d/bacula-sd}. However the
-exact location depends on what operating system you are using.
+The {\bf make install-autostart} will cause the appropriate startup scripts
+to be installed with the necessary symbolic links. On RedHat/Fedora Linux
+systems, these scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
+/etc/rc.d/init.d/bacula-fd}, and {\bf /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:
\addcontentsline{toc}{subsection}{Installing Tray Monitor}
The Tray Monitor is already installed if you used the {\bf
-\verb{--{enable-tray-monitor} configure option and ran {\bf make install}.
+\verb:--:enable-tray-monitor} configure option and ran {\bf make install}.
As you don't run your graphical environment as root (if you do, you should
change that bad habit), don't forget to allow your user to read {\bf
projects / bacula / docs / blobdiff