the Bacula SVN. The released files are:
\begin{description}
-\item [bacula-3.0.3.tar.gz]
+\item [bacula-5.0.0.tar.gz]
This is the primary source code release for Bacula. On each
- release the version number (3.0.3) will be updated.
+ release the version number (5.0.0) will be updated.
-\item [bacula-docs-3.0.3.tar.gz]
+\item [bacula-docs-5.0.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 and German translations
+ file, and pdf file. The French, German, Spanish translations
are in progress, but are not built.
-\item [bacula-gui-3.0.3.tar.gz]
+\item [bacula-gui-5.0.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-3.0.3.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
+\item [bacula-rescue-5.0.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.
- Unfortunately this rescue disk does not properly boot for
- all Linux distributions. The problem is that the boot procedure
- can vary significantly between distributions, and even within
- a distribution, they are a moving target.
-
- This package evolves slower than the Bacula source code,
- so there may not always be a new release of the rescue package when
- making minor updates to the Bacula code. For example, when releasing
- Bacula version 3.0.3, the rescue package may still be at a prior
- version if there were no updates.
-
-\item [winbacula-3.0.3.exe]
+
+\item [win32bacula-5.0.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.
- Beginning with Bacula version 1.39.20, this executable will
- also optionally load the Win32 Director and the Win32
- Storage daemon.
+ This client will also run on 64 bit Windows machines, but
+ 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 [win64bacula-3.0.3.exe]
+\item [win64bacula-5.0.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.
\end{description}
-\label{upgrading1}
-\section{Upgrading Bacula}
+
+\section{Upgrading Bacula}\label{upgrading1}
\index[general]{Bacula!Upgrading}
\index[general]{Upgrading Bacula}
\index[general]{Upgrading}
With version 3.0.0 and later, you {\bf must} ensure that on any one
machine that all components of Bacula are running on exactly the
-same version. Prior to version 3.0.0, it was possible to run a
+same version. Prior to version 3.0.0, it was possible to run a
lower level FD with a newer Director and SD. This is no longer the
-case.
+case.
As always, we attempt to support older File daemons. This avoids the
need to do a simultaneous upgrade of many machines. For exactly what
-older versions of the FD are supported, please see the ReleaseNotes
+older versions of the FD are supported, please see the ReleaseNotes
for the new version. In any case, you must always upgrade both the
Director and the Storage daemon at the same time, and you must also
upgrade any File daemon that is running on the same machine as a Director
Upgrading the catalog is normally done after Bacula is build and installed
by:
-\begin{verbatim}
+\begin{lstlisting}
cd <installed-scripts-dir> (default /etc/bacula)
./update_bacula_tables
-\end{verbatim}
+\end{lstlisting}
This update script can also be find in the Bacula source src/cats
directory.
protocol will change. However, within any particular release (e.g. version
1.32.x) unless there is an oversight or bug, the daemon protocol will not
change. If this is confusing, simply read the ReleaseNotes very carefully as
-they will note if all daemons must be upgraded at the same time.
+they will note if all daemons must be upgraded at the same time.
Finally, please note that in general it is not necessary or desirable
to do a {\bf make uninstall} before doing an upgrade providing you are careful
-not to change the installation directories. In fact, if you do so, you will
+not to change the installation directories. 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:
-\begin{verbatim}
+\begin{lstlisting}
./configure (your options)
make
make install
-\end{verbatim}
+\end{lstlisting}
In general none of your existing .conf or .sql files will be overwritten,
and you must do both the {\bf make} and {\bf make install} commands, a
{\bf make install} without the preceding {\bf make} will not work.
-
-For additional information on upgrading, please see the \ilink{Upgrading Bacula
-Versions}{upgrading} in the Tips chapter of this manual.
+
+For additional information on upgrading, please see the \bsysxrlink{Upgrading Bacula Versions}{upgrading}{problems}{section} of the \problemsman{}.
\section{Releases Numbering}
\index[general]{Release Numbering}
\index[general]{Version Numbering}
-Every Bacula release whether beta or production has a different number
+Every Bacula release whether beta or production has a different number
as well as the date of the release build. The numbering system follows
traditional Open Source conventions in that it is of the form.
-\begin{verbatim}
+\begin{lstlisting}
major.minor.release
-\end{verbatim}
+\end{lstlisting}
For example:
-\begin{verbatim}
+\begin{lstlisting}
1.38.11
-\end{verbatim}
+\end{lstlisting}
where each component (major, minor, patch) is a number.
The major number is currently 1 and normally does not change
the current Bacula version is 1.38.11, versions 1.38.0, 1.38.1, ... 1.38.10
have all been previously released.
-When the minor number is odd, it indicates that the package is under
-development and thus may not be stable. For example, while the current
+When the minor number is odd, it indicates that the package is under
+development and thus may not be stable. For example, while the current
production release of Bacula is currently 1.38.11, the current development
-version is 1.39.22. All patch versions of the development code are
+version is 1.39.22. All patch versions of the development code are
available in the SVN (source repository). However, not all patch versions
of the development code (odd minor version) are officially released. When
they are released, they are released as beta versions (see below for a
-definition of what beta means for Bacula releases).
+definition of what beta means for Bacula releases).
In general when the minor number increases from one production release
to the next (i.e. 1.38.x to 1.40.0), the catalog database must be upgraded,
\index[general]{Beta Releases}
Towards the end of the development cycle, which typically runs
one year from a major release to another, there will be several beta
-releases of the development code prior to a production release.
+releases of the development code prior to a production release.
As noted above, beta versions always have odd minor version numbers
-(e.g 1.37.x or 1.39.x).
+(e.g 1.37.x or 1.39.x).
The purpose of the beta releases is to allow early adopter users to test
the new code. Beta releases are made with the following considerations:
-\begin{itemize}
+\begin{bsysitemize}
\item The code passes the regression testing on FreeBSD, Linux, and Solaris
machines.
-\item There are no known major bugs, or on the rare occasion that
+\item There are no known major bugs, or on the rare occasion that
there are, they will be documented or already in the bugs database.
\item Some of the new code/features may not yet be tested.
\item Beta code is not generally recommended for everyone, but
rather for early adopters.
-\end{itemize}
+\end{bsysitemize}
\label{Dependency}
As discussed above, we have combined a number of third party packages that
Bacula might need into the {\bf depkgs} release. You can,
-of course, get the latest packages from the original authors or
+of course, get the latest packages from the original authors or
from your operating system supplier. The locations of
where we obtained the packages are in the README file in each package.
However, be aware that the packages in the depkgs files have been tested by us
-for compatibility with Bacula.
+for compatibility with Bacula.
Typically, a dependency package will be named {\bf depkgs-ddMMMyy.tar.gz}
where {\bf dd} is the day we release it, {\bf MMM}
is the abbreviated month (e.g. Jan), and {\bf yy} is the year. An actual
-example is: {\bf depkgs-24Jul09.tar.gz}. To install and build this package (if
-needed), you do the following:
+example is: {\bf depkgs-18Dec.tar.gz}. To install and build this package (if
+needed), you do the following:
\begin{enumerate}
\item Create a {\bf bacula} directory, into which you will place both the
- Bacula source as well as the dependency package.
-\item Detar the {\bf depkgs} into the {\bf bacula} directory.
-\item cd bacula/depkgs
-\item make
+ Bacula source as well as the dependency package.
+\item Detar the {\bf depkgs} into the {\bf bacula} directory.
+\item cd bacula/depkgs
+\item make
\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}{Dependency Packages}
-\begin{longtable}{|l|l|l|}
- \hline
-\multicolumn{1}{|c| }{\bf 3rd Party Package} & \multicolumn{1}{c| }{\bf depkgs}
- & \multicolumn{1}{c| }{\bf depkgs-qt} \\
- \hline {SQLite3 } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ }\\
- \hline {mtx } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ } \\
- \hline {qt4 } & \multicolumn{1}{c| }{ } & \multicolumn{1}{c| }{X } \\
- \hline
-\end{longtable}
+to time, the current makeup is the following:
+%\addcontentsline{lot}{table}{Dependency Packages}
+\LTXtable{0.95\linewidth}{table_dependencies}
Note, some of these packages are quite large, so that building them can be a
bit time consuming. The above instructions will build all the packages
contained in the directory. However, when building Bacula, it will take only
-those pieces that it actually needs.
+those pieces that it actually needs.
-Alternatively, you can make just the packages that are needed. For example,
+Alternatively, you can make just the packages that are needed. For example,
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
cd bacula/depkgs
make sqlite
-\end{verbatim}
+\end{lstlisting}
\normalsize
-will configure and build only the SQLite package.
+will configure and build only the SQLite package.
-You should build the packages that you will require in {\bf depkgs} a
+You should build the packages that you will require in {\bf depkgs} a
prior to configuring and building Bacula, since Bacula will need
-them during the build process.
+them during the build process.
+
+Note, the {\bf depkgs-qt} package is required for building bat, because
+bat is currently built with Qt version 4.3.4. It can be built with other
+Qt versions, but that almost always creates problems or introduces
+instabilities.
+
+You can build the depkgs-qt with the following:
+
+\footnotesize
+\begin{lstlisting}
+cd bacula
+tar xfvz depkgs-qt-28Jul09.tar.gz
+cd depkgs-qt
+make qt4
+source qt4-path
+\end{lstlisting}
+\normalsize
+
+Doing the {\bf source qt4-path} defines the following environment
+variables:
+
+\footnotesize
+\begin{lstlisting}
+QTDIR
+QTLIB
+QTINC
+\end{lstlisting}
+\normalsize
+
+Each one should point to a specific location in the depkgs-qt package
+that you loaded. It also puts the depkgs-qt/qt4/bin directory
+on your path before all other directories. This ensures that
+the bat build will use your Qt 4.3.4 library rather than any that
+might be on your system.
+
+Before running your Bacula build, please make sure that
+{\bf qmake-qt4} is not on your path. If it is please rename it. If
+you don't do this, Bacula will attempt to build with any Qt4 package
+installed on your system rather than the one you just built.
+If you logoff and log back in, you must re-source the depkgs-qt/qt4-patch
+file before attempting to rebuild the bat part of Bacula.
For more information on the {\bf depkgs-qt} package, please read the
-INSTALL file in the main directory of that package. If you are going to
+INSTALL file in the main directory of that package. If you are going to
build Qt4 using {\bf depkgs-qt}, you must source the {\bf qt4-paths} file
included in the package prior to building Bacula. Please read the INSTALL
file for more details.
Even if you do not use SQLite, you might find it worthwhile to build {\bf mtx}
because the {\bf tapeinfo} program that comes with it can often provide you
with valuable information about your SCSI tape drive (e.g. compression,
-min/max block sizes, ...). Note, most distros provide {\bf mtx} as part of
+min/max block sizes, ...). Note, most distros provide {\bf mtx} as part of
their release.
The {\bf depkgs1} package is depreciated and previously contained
readline, which should be available on all operating systems.
-The {\bf depkgs-win32} package is deprecated and no longer used in
+The {\bf depkgs-win32} package is deprecated and no longer used in
Bacula version 1.39.x and later. It was previously used to build
the native Win32 client program, but this program is now built on Linux
systems using cross-compiling. All the tools and third party libraries
\index[general]{Systems!Supported Operating}
\index[general]{Supported Operating Systems}
-Please see the
+Please see the
\ilink{ Supported Operating Systems}{SupportedOSes} section
-of the QuickStart chapter of this manual.
+of the QuickStart chapter of this manual.
\section{Building Bacula from Source}
\label{Building}
\index[general]{Source!Building Bacula from}
\index[general]{Building Bacula from Source}
-The basic installation is rather simple.
+The basic installation is rather simple.
\begin{enumerate}
\item Install and build any {\bf depkgs} as noted above. This
should be unnecessary on most modern Operating Systems.
-\item Configure and install MySQL or PostgreSQL (if desired).
- \ilink{Installing and Configuring MySQL Phase I}{MySqlChapter} or
+\item Configure and install MySQL or PostgreSQL (if desired).
+ \ilink{Installing and Configuring MySQL Phase I}{MySqlChapter} or
\ilink{Installing and Configuring PostgreSQL Phase
I}{PostgreSqlChapter}. If you are installing from rpms, and are
using MySQL, please be sure to install {\bf mysql-devel}, so that the MySQL
libz.a} or {\bf libz.so}. If you are using rpm packages, these libraries are
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.
+ find the appropriate package for your system.
- Note, if you already have a running MySQL or PostgreSQL on your system, you
+ 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.
+ 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 SQLite3 may work.
\item Detar the Bacula source code preferably into the {\bf bacula} directory
- discussed above.
+ discussed above.
-\item {\bf cd} to the directory containing the source code.
+\item {\bf cd} to the directory containing the source code.
\item ./configure (with appropriate options as described below). Any
path names you specify as options on the ./configure command line
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}.
+ 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:
+ re-run it, that is perfectly fine, but before re-running it, you should run:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make distclean
-\end{verbatim}
+\end{lstlisting}
\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 directory 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.
+continue on.
-\item make
+\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.
fail because Bacula requires a {\bf make} before a {\bf make install}.
2. you are depriving yourself of the chance to make sure there are no
errors before beginning to write files to your system directories.
-
-\item make install
+
+\item make install
Please be sure you have done a {\bf make} before entering this command,
and that everything has properly compiled and linked without errors.
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
+\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}{ConfigureChapter} in the Configuration chapter of this manual. We
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.
+ for security reasons.
\label{CreateDatabase}
\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 MySQL Phase II}{mysql_phase2} or
+ create the Bacula PostgreSQL database and tables
\ilink{Configuring PostgreSQL
II}{PostgreSQL_configure} or alternatively if you are using
- SQLite \ilink{Installing and Configuring SQLite Phase II}{phase2}.
+ 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.
+ how to do this in detail.
-\item Interface with Bacula using the Console program
+\item Interface with Bacula using the Console program
-\item For the previous two items, please follow the instructions in the
+\item For the previous two items, please follow the instructions in the
\ilink{Running Bacula}{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.
+ 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:
+ install it in a different set of directories, proceed as follows:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make uninstall
make distclean
./configure (your-new-options)
make
make install
-
-\end{verbatim}
+
+\end{lstlisting}
\normalsize
\end{enumerate}
If all goes well, the {\bf ./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 not enabled (default) when building the client.
+client (File daemon) is reported to work with MacOS X 10.3 is if
+readline support is 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 "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:
+done a ./configure command, you MUST do:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make distclean
-\end{verbatim}
+\end{lstlisting}
\normalsize
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
-everything is placed into the correct directories.
+everything is placed into the correct directories.
-For example, on Fedora, Red Hat, or SuSE one could use the following:
+For example, on Fedora, Red Hat, or SuSE one could use the following:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
CFLAGS="-g -Wall" \
./configure \
--sbindir=$HOME/bacula/bin \
--with-mysql \
--with-working-dir=$HOME/bacula/bin/working \
--with-dump-email=$USER
-\end{verbatim}
+\end{lstlisting}
\normalsize
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.
+works. In addition, the above can be installed and run as non-root.
For the developer's convenience, I have added a {\bf defaultconfig} script to
the {\bf 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 {\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 most
-systems, including Red Hat and SuSE, you should include the ncurses package.
-If Bacula's configure process finds the ncurses libraries, it will use
-those rather than the termcap library.
-On some systems, such as SuSE, the 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:
+You should find additional useful examples in this directory as well.
+
+The {\bf \lstinline:--:enable-conio} or {\bf \lstinline:--: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 {\bf termcap} or the {\bf ncurses}
+package will be needed to link. On most systems, including Red Hat and SuSE,
+you should include the ncurses package. If Bacula's configure process finds
+the ncurses libraries, it will use those rather than the termcap library. On
+some systems, such as SuSE, the 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:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
/usr/lib/gcc-lib/i586-suse-linux/3.3.1/.../ld:
cannot find -ltermcap
collect2: ld returned 1 exit status
-\end{verbatim}
+\end{lstlisting}
\normalsize
while building the Bacula Console. In that case, you will need to set the {\bf
-LDFLAGS} environment variable prior to building.
+LDFLAGS} environment variable prior to building.
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
export LDFLAGS="-L/usr/lib/termcap"
-\end{verbatim}
+\end{lstlisting}
\normalsize
-The same library requirements apply if you wish to use the readline
-subroutines for command line editing and history 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 ./configure line
-as in:
+The same library requirements apply if you wish to use the 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 ./configure line as in:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
LDFLAGS="-lssl -lcyrpto" \
./configure <your-options>
-\end{verbatim}
+\end{lstlisting}
\normalsize
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
+\lstinline:--: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.
+package will gobble up prompts.
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
performs well and is suitable for small to medium sized installations (maximum
10-20 machines). However, we should note that a number of users have
had unexplained database corruption with SQLite. For that reason, we
-recommend that you install either MySQL or PostgreSQL for production
+recommend that you install either PostgreSQL or MySQL for production
work.
-If you wish to use MySQL as the Bacula catalog, please see the
-\ilink{Installing and Configuring MySQL}{MySqlChapter} chapter of
-this manual. You will need to install MySQL prior to continuing with the
+If you wish to use MySQL as the Bacula catalog, please see the
+\ilink{Installing and Configuring MySQL}{MySqlChapter} chapter of this
+manual. You will need to install MySQL prior to continuing with the
configuration of Bacula. MySQL is a high quality database that is very
-efficient and is suitable for any sized installation. It is slightly more
-complicated than SQLite to setup and administer because it has a number of
-sophisticated features such as userids and passwords. It runs as a separate
-process, is truly professional and can manage a database of any size.
-
-If you wish to use PostgreSQL as the Bacula catalog, please see the
-\ilink{Installing and Configuring PostgreSQL}{PostgreSqlChapter}
-chapter of this manual. You will need to install PostgreSQL prior to
-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.
-
-If you wish to use SQLite as the Bacula catalog, please see
+efficient and is suitable for small and medium sized installation (up to
+2,000,000 files per job). It is slightly more complicated than SQLite to setup
+and administer because it has a number of sophisticated features such as
+userids and passwords. It runs as a separate process, is truly professional and
+can manage a database of any size.
+
+If you wish to use PostgreSQL as the Bacula catalog, please see the
+\ilink{Installing and Configuring PostgreSQL}{PostgreSqlChapter} chapter of
+this manual. You will need to install PostgreSQL prior to 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. PostgreSQL is suitable for any sized installation
+(some sites have much more than 1 billion objects in the Catalog). Bacula uses
+many optimized PostgreSQL functions, and can run more than 10 time faster on
+jobs having millions of files than MySQL (Specially in during restore, accurate
+mode, bvfs queries and when the database server is not on the same host than
+the Director). It's possible to switch from MySQL/SQLite to PostgreSQL, but it
+requires some DBA knowledge.
+
+If you wish to use SQLite as the Bacula catalog, please see
\ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of
this manual. SQLite is not supported on Solaris.
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.
+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
+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
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.
+come back to this chapter and read the details presented below.
\section{Configure Options}
\label{Options}
\index[general]{Configure Options}
The following command line options are available for {\bf configure} to
-customize your installation.
+customize your installation.
\begin{description}
\item [ \--prefix=\lt{}patch\gt{}]
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
- what ./configure does by default. As a consequence, we suggest that
+ 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 ./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=\lt{}binary-path\gt{}]
\index[general]{{-}{\-}sbindir}
Defines where the Bacula binary (executable) files will be placed during a
- {\bf make install} command.
+ {\bf make install} command.
\item [ {-}{\-}sysconfdir=\lt{}config-path\gt{}]
\index[general]{{-}{\-}sysconfdir}
For the install to succeed you must have {\bf gzip} installed
on your system.
- By default, Bacula will install the Unix man pages in
- /usr/share/man/man1 and /usr/share/man/man8.
+ By default, Bacula will install the Unix man pages in
+ /usr/share/man/man1 and /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
Bacula, you must specify this option. Doing so will build everything in
the {\bf 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).
+ 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 {\bf depkgs-qt}
(change the path to point to your particular installed libpq.a;
these commands were issued on FreeBSD 6.2):
-\begin{verbatim}
+\begin{lstlisting}
$ nm /usr/local/lib/libpq.a | grep PQputCopyData
00001b08 T PQputCopyData
$ nm /usr/local/lib/libpq.a | grep mutex
U pthread_mutex_init
U pthread_mutex_lock
U pthread_mutex_unlock
-\end{verbatim}
+\end{lstlisting}
The above example shows a libpq that contains the required function
PQputCopyData and is thread enabled (i.e. the pthread\_mutex* entries).
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
+ significantly improve attribute insertion times. However, it does
put a significantly larger part of the work on your SQL engine, so
- you may need to pay more attention to tuning it. In particular,
+ 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 /tmp) may run out of space causing errors.
For MySQL, the location is set in my.conf with "tmpdir". You may also
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. Note, due to
+ everything in the {\bf src/tray-monitor} directory. Note, due to
restrictions on what can be linked with GPLed 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
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}.
+ {\bf \lstinline:--:disable-static-tools}.
\item [ {-}{\-}enable-static-fd]
\index[general]{{-}{\-}enable-static-fd}
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
+ \lstinline:--: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.
-
+ 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
+ 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
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
+ 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
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
+ 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
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
+ 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
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
+ 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
\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
+ 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}.
+ revert to 32 bit file addresses by using {\bf \lstinline:--: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
+ 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-openssl=\lt{}path\gt{}]
This configuration option is necessary if you want to enable TLS (ssl),
- which encrypts the communications within
+ which encrypts the communications within
Bacula or if you want to use File Daemon PKI data encryption.
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
+ locations. However, you must ensure that all the libraries are
+ loaded including {\bf 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 TLS, please see the
\ilink{Bacula TLS -- Communications Encryption}{CommEncryption} chapter
\ilink{Bacula PKI -- Data Encryption}{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-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, 2.4, or 2.5. If it cannot find the library, you will need to
supply a path to your Python library directory. Please see the
- \ilink{Python chapter}{PythonChapter} for the details of using Python
+ \bsysxrlink{Python Scripting}
+ {PythonChapter}{misc}{chapter} of the \miscman{} for the details of using Python
scripting.
\item [ {-}{\-}with-libintl-prefix=\lt{}DIR\gt{}]
\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.
+ change in incompatible ways from version to version.
\item [ {-}{\-}with-tcp-wrappers=\lt{}path\gt{}]
\index[general]{{-}{\-}with-tcp-wrappers}
or {\bf /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
+
+ For more information on configuring and testing TCP wrappers, please see the
\ilink{Configuring and Testing TCP Wrappers}{wrappers} section
- in the Security Chapter.
+ 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
\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,
+ 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.
+ you must ensure that it exists before using Bacula for the first time.
-\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
+\item [ {-}{\-}with-baseport=\lt{}port=number\gt{}]
+ \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 {\bf
- \verb:--:with-baseport} option will automatically assign three ports beginning at
+ \lstinline:--: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
+ 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.
+ may also accomplish the same thing by directly editing them later.
\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.
+ This option is normally only used by developers.
\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.
+ the first time.
\item [ {-}{\-}with-subsys-dir=\lt{}PATH\gt{}]
\index[general]{{-}{\-}with-subsys-dir}
not specify the same directory for this directory and for the {\bf 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.
+ create it before using Bacula.
\item [ {-}{\-}with-dir-password=\lt{}Password\gt{}]
\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.
+ automatically create a random 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.
+ automatically create a random 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 Storage daemon
(normally called from the Director). If it is not specified, configure will
- automatically create a random password.
+ automatically create a random password.
\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 this option.
+ specified on this option.
If you specify this option, you must
create the User prior to running {\bf make install}, because the
working directory owner will be set to {\bf User}.
-
+
\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
- on this option.
+ on this option.
If you specify this option, you must
create the Group prior to running {\bf make install}, because the
working directory group will be set to {\bf Group}.
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.
+ it needs.
\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
- specified on this option.
+ specified on this option.
\item [ {-}{\-}with-fd-user=\lt{}User\gt{} ]
\index[general]{{-}{\-}with-fd-user}
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.
+ option.
\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
- the GroupId specified on this option.
+ the GroupId specified on this option.
\item [ {-}{\-}with-mon-dir-password=\lt{}Password\gt{}]
\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.
+ automatically create a random password.
\item [ {-}{\-}with-mon-fd-password=\lt{}Password\gt{} ]
\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.
+ automatically create a random password.
\item [ {-}{\-}with-mon-sd-password=\lt{}Password\gt{} ]
\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.
+ automatically create a random password.
\item [ {-}{\-}with-db-name=\lt{}database-name\gt{} ]
\index[general]{{-}{\-}with-db-name}
\end{description}
Note, many other options are presented when you do a {\bf ./configure
-\verb:--:help}, but they are not implemented.
+\lstinline:--: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:
+For most systems, we recommend starting with the following options:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
./configure \
--enable-smartalloc \
--sbindir=$HOME/bacula/bin \
--with-subsys-dir=$HOME/bacula/bin/working \
--with-mysql=$HOME/mysql \
--with-working-dir=$HOME/bacula/working
-\end{verbatim}
+\end{lstlisting}
\normalsize
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
+should also include the \lstinline:--:sbindir and \lstinline:--: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
\section{Red Hat}
\index[general]{Red Hat}
-Using SQLite:
+Using SQLite:
\footnotesize
-\begin{verbatim}
-
+\begin{lstlisting}
+
CFLAGS="-g -Wall" ./configure \
--sbindir=$HOME/bacula/bin \
--sysconfdir=$HOME/bacula/bin \
--with-subsys-dir=$HOME/bacula/bin/working \
--enable-bat \
--enable-conio
-\end{verbatim}
+\end{lstlisting}
\normalsize
-or
+or
\footnotesize
-\begin{verbatim}
-
+\begin{lstlisting}
+
CFLAGS="-g -Wall" ./configure \
--sbindir=$HOME/bacula/bin \
--sysconfdir=$HOME/bacula/bin \
--with-pid-dir=$HOME/bacula/bin/working \
--with-subsys-dir=$HOME/bacula/bin/working
--enable-conio
-\end{verbatim}
+\end{lstlisting}
\normalsize
-or finally, a completely traditional Red Hat Linux install:
+or finally, a completely traditional Red Hat Linux install:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
CFLAGS="-g -Wall" ./configure \
--sbindir=/usr/sbin \
--sysconfdir=/etc/bacula \
--with-working-dir=/var/bacula \
--with-pid-dir=/var/run \
--enable-conio
-\end{verbatim}
+\end{lstlisting}
\normalsize
Note, Bacula assumes that /var/bacula, /var/run, and /var/lock/subsys exist so
-it will not automatically create them during the install process.
+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.
+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.
+/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.
+we recommend using GNU C++ if possible.
A typical configuration command might look like:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
#!/bin/sh
CFLAGS="-g" ./configure \
--sbindir=$HOME/bacula/bin \
--with-pid-dir=$HOME/bacula/bin/working \
--with-subsys-dir=$HOME/bacula/bin/working \
--with-working-dir=$HOME/bacula/working
-\end{verbatim}
+\end{lstlisting}
\normalsize
As mentioned above, the install process will create the sbindir and sysconfdir
Note, you may need to install the following packages to build Bacula
from source:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
SUNWbinutils,
SUNWarc,
SUNWhea,
SUNWGmakeS
SUNWlibm
-export
+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}
+\end{lstlisting}
\normalsize
If you have installed special software not normally in the Solaris
simplest way to do so is to run:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
setenv LDFLAGS "-L/usr/sfw/lib -R/usr/sfw/lib"
-\end{verbatim}
+\end{lstlisting}
\normalsize
Prior to running the ./configure command.
\section{FreeBSD}
\index[general]{FreeBSD}
-Please see:
+Please see:
\elink{The FreeBSD Diary}{http://www.freebsddiary.org/bacula.php} 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
-\ilink{Tape Testing Chapter}{FreeBSDTapes} of this manual for
+plan to use tape devices, please see the
+\bsysxrlink{Tape Testing}{FreeBSDTapes}{problems}{section} of \problemsman{} for
{\bf important} information on how to configure your tape drive for
-compatibility with Bacula.
+compatibility with \mbacula{}.
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.
+probably not work.
\section{Win32}
\index[general]{Win32}
-To install the binary Win32 version of the File daemon please see the
-\ilink{Win32 Installation Chapter}{Win32Chapter} in this document.
+To install the binary Win32 version of the File daemon please see the
+\ilink{Win32 Installation Chapter}{Win32Chapter} in this document.
\section{One File Configure Script}
\index[general]{Script!One File Configure}
in a single file:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
#!/bin/sh
CFLAGS="-g -Wall" \
./configure \
--with-job-email=$USER@your-site.com \
--with-smtp-host=mail.your-site.com
exit 0
-\end{verbatim}
+\end{lstlisting}
\normalsize
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
-recognize (i.e. netstat -a):
+recognize (i.e. netstat -a):
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
bacula-dir 9101/tcp
bacula-fd 9102/tcp
bacula-sd 9103/tcp
-\end{verbatim}
+\end{lstlisting}
\normalsize
\section{Installing Bacula}
\index[general]{Installing Bacula}
Before setting up your configuration files, you will want to install Bacula in
-its final location. Simply enter:
+its final location. Simply enter:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make install
-\end{verbatim}
+\end{lstlisting}
\normalsize
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 {\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}.
+configuration files with the appended {\bf .new}.
\section{Building a File Daemon or Client}
\index[general]{Client!Building a File Daemon or}
copy the Bacula File daemon binary file {\bf bacula-fd} as well as its
configuration file {\bf 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 ({\bf bacula-dir.conf}).
+Director's configuration file ({\bf 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 {\bf
./configure} command as you did for your main program, starting either from a
fresh copy of the source tree, or using {\bf make\ distclean} before the {\bf
-./configure}.
+./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
+the {\bf \lstinline:--:with-mysql} or {\bf \lstinline:--:with-sqlite} options, then
+add {\bf \lstinline:--: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
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 {\bf unknown}, then you must install the platform
-dependent files by doing:
+dependent files by doing:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
(become root)
make install-autostart
-\end{verbatim}
+\end{lstlisting}
\normalsize
Please note, that the auto-start feature is implemented only on systems
/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:
+If you only wish to install the File daemon, you may do so with:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make install-autostart-fd
-\end{verbatim}
+\end{lstlisting}
\normalsize
\section{Other Make Notes}
\index[general]{Notes!Other Make}
\index[general]{Other Make Notes}
-To simply build a new executable in any directory, enter:
+To simply build a new executable in any directory, enter:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make
-\end{verbatim}
+\end{lstlisting}
\normalsize
To clean out all the objects and binaries (including the files named 1, 2, or
-3, which are development temporary files), enter:
+3, which are development temporary files), enter:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make clean
-\end{verbatim}
+\end{lstlisting}
\normalsize
-To really clean out everything for distribution, enter:
+To really clean out everything for distribution, enter:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make distclean
-\end{verbatim}
+\end{lstlisting}
\normalsize
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 {\bf ./configure} in the top level directory, since
-all the Makefiles will be deleted.
+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 {\bf make}. In most cases, the make will rebuild the Makefile
from the new Makefile.in. In some case, you may need to issue the {\bf make} a
second time. In extreme cases, cd to the top level directory and enter: {\bf
-make Makefiles}.
+make Makefiles}.
-To add dependencies:
+To add dependencies:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make depend
-\end{verbatim}
+\end{lstlisting}
\normalsize
The {\bf make depend} appends the header file dependencies for each of the
object files to Makefile and 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. {\bf make depend} is normally
-automatically invoked during the configuration process.
+automatically invoked during the configuration process.
-To install:
+To install:
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
make install
-\end{verbatim}
+\end{lstlisting}
\normalsize
This not normally done if you are developing Bacula, but is used if you are
-going to run it to backup your system.
+going to run it to backup your system.
After doing a {\bf make install} the following files will be installed on your
system (more or less). The exact files and location (directory) for each file
starting point.
\footnotesize
-\begin{verbatim}
+\begin{lstlisting}
bacula
bacula-dir
bacula-dir.conf
bwx-console
bwx-console.conf
9 man pages
-\end{verbatim}
+\end{lstlisting}
\normalsize
\label{monitor}
\index[general]{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}.
+\lstinline:--: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
{\bf 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.
+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 {\bf Add to this Panel}, then {\bf Utility} and
-finally click on {\bf Notification Area}.
+finally click on {\bf 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 {\bf Add}, then {\bf Applet}
-and finally click on {\bf System Tray}.
+and finally click on {\bf 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.
+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
+See the chapter
\ilink{Configuring Bacula}{ConfigureChapter} in this manual for
-instructions on how to set Bacula configuration files.
+instructions on how to set Bacula configuration files.
projects / bacula / docs / blobdiff