4 \chapter{Installing Bacula}
6 \index[general]{Bacula!Installing}
7 \index[general]{Installing Bacula}
9 In general, you will need the Bacula source release, and if you want to run
10 a Windows client, you will need the Bacula Windows binary release.
11 However, Bacula needs certain third party packages (such as {\bf MySQL},
12 {\bf PostgreSQL}, or {\bf SQLite} to build and run
13 properly depending on the
14 options you specify. Normally, {\bf MySQL} and {\bf PostgreSQL} are
15 packages that can be installed on your distribution. However, if you do
16 not have them, to simplify your task, we have combined a number of these
17 packages into three {\bf depkgs} releases (Dependency Packages). This can
18 vastly simplify your life by providing you with all the necessary packages
19 rather than requiring you to find them on the Web, load them, and install
22 \section{Source Release Files}
23 \index[general]{Source Files}
24 \index[general]{Release Files}
25 Beginning with Bacula 1.38.0, the source code has been broken into
26 four separate tar files each corresponding to a different module in
27 the Bacula SVN. The released files are:
30 \item [bacula-5.0.0.tar.gz]
31 This is the primary source code release for Bacula. On each
32 release the version number (5.0.0) will be updated.
34 \item [bacula-docs-5.0.0.tar.bz2]
35 This file contains a copy of the docs directory with the
36 documents prebuild. English HTML directory, single HTML
37 file, and pdf file. The French, German, Spanish translations
38 are in progress, but are not built.
40 \item [bacula-gui-5.0.0.tar.gz]
41 This file contains the non-core GUI programs. Currently,
42 it contains bacula-web, a PHP program for producing management
43 viewing of your Bacula job status in a browser; and bimagemgr
44 a browser program for burning CDROM images with Bacula Volumes.
46 \item [bacula-rescue-5.0.0.tar.gz]
47 This is the Bacula Rescue USB key code. Note, the version number
48 of this package is not always tied to the Bacula release version, so
49 it may be different. Using this code, you can create a USB key
50 with your system configuration and containing a statically
51 linked version of the File daemon. This can permit you to easily
52 repartition and reformat your hard disks and reload your
53 system with Bacula in the case of a hard disk failure.
55 \item [win32bacula-5.0.0.exe]
56 This file is the 32 bit Windows installer for installing
57 the Windows client (File daemon) on a Windows machine.
58 This client will also run on 64 bit Windows machines, but
59 VSS support is not available if you are running a 64 bit
60 version of Windows. This installer installs only the FD,
61 the Director and Storage daemon are not included.
64 \item [win64bacula-5.0.0.exe]
65 This file is the 64 bit Windows installer for installing
66 the Windows client (File daemon) on a Windows machine.
67 This client will only run on 64 bit Windows OS machines.
68 It will not run on 32 bit machines or 32 bit Windows OSes.
69 The win64bacula release is necessary for Volume Shadow
70 Copy (VSS) to work on Win64 OSes. This installer
71 installs only the FD, the Director and Storage daemon
77 \section{Upgrading Bacula}
78 \index[general]{Bacula!Upgrading}
79 \index[general]{Upgrading Bacula}
80 \index[general]{Upgrading}
82 If you are upgrading from one Bacula version to another, you should first
83 carefully read the ReleaseNotes of all major versions between your current
84 version and the version to which you are upgrading. In many upgrades,
85 especially for minor patch upgrades (e.g. between 3.0.0 and 3.0.1) there
86 will be no database upgrade, and hence the process is rather simple.
88 With version 3.0.0 and later, you {\bf must} ensure that on any one
89 machine that all components of Bacula are running on exactly the
90 same version. Prior to version 3.0.0, it was possible to run a
91 lower level FD with a newer Director and SD. This is no longer the
94 As always, we attempt to support older File daemons. This avoids the
95 need to do a simultaneous upgrade of many machines. For exactly what
96 older versions of the FD are supported, please see the ReleaseNotes
97 for the new version. In any case, you must always upgrade both the
98 Director and the Storage daemon at the same time, and you must also
99 upgrade any File daemon that is running on the same machine as a Director
100 or a Storage daemon (see the prior paragraph).
102 If the Bacula catalog
103 database has been upgraded (as it is almost every major release), you will
104 either need to reinitialize your database starting from scratch (not
105 normally a good idea), or save an ASCII copy of your database, then proceed
106 to upgrade it. If you are upgrading two major versions (e.g. 1.36 to 2.0)
107 then life will be more complicated because you must do two database
108 upgrades. See below for more on this.
110 Upgrading the catalog is normally done after Bacula is build and installed
114 cd <installed-scripts-dir> (default /etc/bacula)
115 ./update_bacula_tables
118 This update script can also be find in the Bacula source src/cats
121 If there are several database upgrades between your version and the
122 version to which you are upgrading, you will need to apply each database
123 upgrade script. For your convenience, you can find all the old upgrade scripts
124 in the {\bf upgradedb} directory of the source code. You will need to edit the
125 scripts to correspond to your system configuration. The final upgrade script,
126 if any, can be applied as noted above.
128 If you are upgrading from one major version to another, you will need to
129 replace all your components at the same time as generally the inter-daemon
130 protocol will change. However, within any particular release (e.g. version
131 1.32.x) unless there is an oversight or bug, the daemon protocol will not
132 change. If this is confusing, simply read the ReleaseNotes very carefully as
133 they will note if all daemons must be upgraded at the same time.
135 Finally, please note that in general it is not necessary or desirable
136 to do a {\bf make uninstall} before doing an upgrade providing you are careful
137 not to change the installation directories. In fact, if you do so, you will
138 most likely delete all your conf files, which could be disastrous.
139 The normal procedure during an upgrade is simply:
142 ./configure (your options)
147 In general none of your existing .conf or .sql files will be overwritten,
148 and you must do both the {\bf make} and {\bf make install} commands, a
149 {\bf make install} without the preceding {\bf make} will not work.
151 For additional information on upgrading, please see the \ilink{Upgrading Bacula
152 Versions}{upgrading} in the Tips chapter of this manual.
154 \section{Releases Numbering}
155 \index[general]{Release Numbering}
156 \index[general]{Version Numbering}
157 Every Bacula release whether beta or production has a different number
158 as well as the date of the release build. The numbering system follows
159 traditional Open Source conventions in that it is of the form.
170 where each component (major, minor, patch) is a number.
171 The major number is currently 1 and normally does not change
172 very frequently. The minor number starts at 0 and increases
173 each for each production release by 2 (i.e. it is always an
174 even number for a production release), and the patch number is
175 starts at zero each time the minor number changes. The patch
176 number is increased each time a bug fix (or fixes) is released
179 So, as of this date (10 September 2006), the current production Bacula
180 release is version 1.38.11. If there are bug fixes, the next release
181 will be 1.38.12 (i.e. the patch number has increased by one).
183 For all patch releases where the minor version number does not change,
184 the database and all the daemons will be compatible. That means that
185 you can safely run a 1.38.0 Director with a 1.38.11 Client. Of course,
186 in this case, the Director may have bugs that are not fixed. Generally,
187 within a minor release (some minor releases are not so minor), all
188 patch numbers are officially released to production. This means that while
189 the current Bacula version is 1.38.11, versions 1.38.0, 1.38.1, ... 1.38.10
190 have all been previously released.
192 When the minor number is odd, it indicates that the package is under
193 development and thus may not be stable. For example, while the current
194 production release of Bacula is currently 1.38.11, the current development
195 version is 1.39.22. All patch versions of the development code are
196 available in the SVN (source repository). However, not all patch versions
197 of the development code (odd minor version) are officially released. When
198 they are released, they are released as beta versions (see below for a
199 definition of what beta means for Bacula releases).
201 In general when the minor number increases from one production release
202 to the next (i.e. 1.38.x to 1.40.0), the catalog database must be upgraded,
203 the Director and Storage daemon must always be on the same minor release
204 number, and often (not always), the Clients must also be on the same minor
205 release. As often as possible, we attempt to make new releases that are
206 downwards compatible with prior clients, but this is not always possible.
207 You must check the release notes. In general, you will have fewer problems
208 if you always run all the components on the same minor version number (i.e.
209 all either 1.38.x or 1.40.x but not mixed).
213 \section*{Beta Releases}
214 \index[general]{Beta Releases}
215 Towards the end of the development cycle, which typically runs
216 one year from a major release to another, there will be several beta
217 releases of the development code prior to a production release.
218 As noted above, beta versions always have odd minor version numbers
219 (e.g 1.37.x or 1.39.x).
220 The purpose of the beta releases is to allow early adopter users to test
221 the new code. Beta releases are made with the following considerations:
224 \item The code passes the regression testing on FreeBSD, Linux, and Solaris
227 \item There are no known major bugs, or on the rare occasion that
228 there are, they will be documented or already in the bugs database.
230 \item Some of the new code/features may not yet be tested.
232 \item Bugs are expected to be found, especially in the new
233 code before the final production release.
235 \item The code will have been run in production in at least one small
238 \item The Win32 client will have been run in production at least
239 one night at that small site.
241 \item The documentation in the manual is unlikely to be complete especially
242 for the new features, and the Release Notes may not be fully
245 \item Beta code is not generally recommended for everyone, but
246 rather for early adopters.
251 \section{Dependency Packages}
252 \index[general]{Dependency Packages}
253 \index[general]{Packages!Dependency}
255 As discussed above, we have combined a number of third party packages that
256 Bacula might need into the {\bf depkgs} release. You can,
257 of course, get the latest packages from the original authors or
258 from your operating system supplier. The locations of
259 where we obtained the packages are in the README file in each package.
260 However, be aware that the packages in the depkgs files have been tested by us
261 for compatibility with Bacula.
263 Typically, a dependency package will be named {\bf depkgs-ddMMMyy.tar.gz}
264 where {\bf dd} is the day we release it, {\bf MMM}
265 is the abbreviated month (e.g. Jan), and {\bf yy} is the year. An actual
266 example is: {\bf depkgs-18Dec.tar.gz}. To install and build this package (if
267 needed), you do the following:
270 \item Create a {\bf bacula} directory, into which you will place both the
271 Bacula source as well as the dependency package.
272 \item Detar the {\bf depkgs} into the {\bf bacula} directory.
273 \item cd bacula/depkgs
277 Although the exact composition of the dependency packages may change from time
278 to time, the current makeup is the following:
280 \addcontentsline{lot}{table}{Dependency Packages}
281 \begin{longtable}{|l|l|l|}
283 \multicolumn{1}{|c| }{\bf 3rd Party Package} & \multicolumn{1}{c| }{\bf depkgs}
284 & \multicolumn{1}{c| }{\bf depkgs-qt} \\
285 \hline {SQLite3 } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ }\\
286 \hline {mtx } & \multicolumn{1}{c| }{X } & \multicolumn{1}{c| }{ } \\
287 \hline {qt4 } & \multicolumn{1}{c| }{ } & \multicolumn{1}{c| }{X } \\
291 Note, some of these packages are quite large, so that building them can be a
292 bit time consuming. The above instructions will build all the packages
293 contained in the directory. However, when building Bacula, it will take only
294 those pieces that it actually needs.
296 Alternatively, you can make just the packages that are needed. For example,
305 will configure and build only the SQLite package.
307 You should build the packages that you will require in {\bf depkgs} a
308 prior to configuring and building Bacula, since Bacula will need
309 them during the build process.
311 Note, the {\bf depkgs-qt} package is required for building bat, because
312 bat is currently built with Qt version 4.3.4. It can be built with other
313 Qt versions, but that almost always creates problems or introduces
316 You can build the depkgs-qt with the following:
321 tar xfvz depkgs-qt-28Jul09.tar.gz
328 Doing the {\bf source qt4-path} defines the following environment
339 Each one should point to a specific location in the depkgs-qt package
340 that you loaded. It also puts the depkgs-qt/qt4/bin directory
341 on your path before all other directories. This ensures that
342 the bat build will use your Qt 4.3.4 library rather than any that
343 might be on your system.
345 Before running your Bacula build, please make sure that
346 {\bf qmake-qt4} is not on your path. If it is please rename it. If
347 you don't do this, Bacula will attempt to build with any Qt4 package
348 installed on your system rather than the one you just built.
349 If you logoff and log back in, you must re-source the depkgs-qt/qt4-patch
350 file before attempting to rebuild the bat part of Bacula.
352 For more information on the {\bf depkgs-qt} package, please read the
353 INSTALL file in the main directory of that package. If you are going to
354 build Qt4 using {\bf depkgs-qt}, you must source the {\bf qt4-paths} file
355 included in the package prior to building Bacula. Please read the INSTALL
356 file for more details.
358 Even if you do not use SQLite, you might find it worthwhile to build {\bf mtx}
359 because the {\bf tapeinfo} program that comes with it can often provide you
360 with valuable information about your SCSI tape drive (e.g. compression,
361 min/max block sizes, ...). Note, most distros provide {\bf mtx} as part of
364 The {\bf depkgs1} package is depreciated and previously contained
365 readline, which should be available on all operating systems.
367 The {\bf depkgs-win32} package is deprecated and no longer used in
368 Bacula version 1.39.x and later. It was previously used to build
369 the native Win32 client program, but this program is now built on Linux
370 systems using cross-compiling. All the tools and third party libraries
371 are automatically downloaded by executing the appropriate scripts. See
372 src/win32/README.mingw32 for more details.
374 \section{Supported Operating Systems}
376 \index[general]{Systems!Supported Operating}
377 \index[general]{Supported Operating Systems}
380 \ilink{ Supported Operating Systems}{SupportedOSes} section
381 of the QuickStart chapter of this manual.
383 \section{Building Bacula from Source}
385 \index[general]{Source!Building Bacula from}
386 \index[general]{Building Bacula from Source}
388 The basic installation is rather simple.
391 \item Install and build any {\bf depkgs} as noted above. This
392 should be unnecessary on most modern Operating Systems.
394 \item Configure and install MySQL or PostgreSQL (if desired).
395 \ilink{Installing and Configuring MySQL Phase I}{MySqlChapter} or
396 \ilink{Installing and Configuring PostgreSQL Phase
397 I}{PostgreSqlChapter}. If you are installing from rpms, and are
398 using MySQL, please be sure to install {\bf mysql-devel}, so that the MySQL
399 header files are available while compiling Bacula. In addition, the MySQL
400 client library {\bf mysqlclient} requires the gzip compression library {\bf
401 libz.a} or {\bf libz.so}. If you are using rpm packages, these libraries are
402 in the {\bf libz-devel} package. On Debian systems, you will need to load the
403 {\bf zlib1g-dev} package. If you are not using rpms or debs, you will need to
404 find the appropriate package for your system.
406 Note, if you already have a running MySQL or PostgreSQL on your system, you
407 can skip this phase provided that you have built the thread safe libraries.
408 And you have already installed the additional rpms noted above.
410 SQLite is not supported on Solaris. This is because it
411 frequently fails with bus errors. However SQLite3 may work.
413 \item Detar the Bacula source code preferably into the {\bf bacula} directory
416 \item {\bf cd} to the directory containing the source code.
418 \item ./configure (with appropriate options as described below). Any
419 path names you specify as options on the ./configure command line
420 must be absolute paths and not relative.
422 \item Check the output of ./configure very carefully, especially the Install
423 binaries and Install config directories. If they are not correct,
424 please rerun ./configure until they are. The output from ./configure is
425 stored in {\bf config.out} and can be re-displayed at any time without
426 rerunning the ./configure by doing {\bf cat config.out}.
428 \item If after running ./configure once, you decide to change options and
429 re-run it, that is perfectly fine, but before re-running it, you should run:
437 so that you are sure to start from scratch and not have a mixture of the two
438 options. This is because ./configure caches much of the information. The {\bf
439 make distclean} is also critical if you move the source directory from one
440 machine to another. If the {\bf make distclean} fails, just ignore it and
444 If you get errors while linking in the Storage daemon directory
445 (src/stored), it is probably because you have not loaded the static
446 libraries on your system. I noticed this problem on a Solaris system.
447 To correct it, make sure that you have not added {\bf
448 {-} {-}enable-static-tools} to the {\bf ./configure} command.
450 If you skip this step ({\bf make}) and proceed immediately to the {\bf
451 make install} you are making two serious errors: 1. your install will
452 fail because Bacula requires a {\bf make} before a {\bf make install}.
453 2. you are depriving yourself of the chance to make sure there are no
454 errors before beginning to write files to your system directories.
458 Please be sure you have done a {\bf make} before entering this command,
459 and that everything has properly compiled and linked without errors.
462 \item If you are new to Bacula, we {\bf strongly} recommend that you skip
463 the next step and use the default configuration files, then run the
464 example program in the next chapter, then come back and modify your
465 configuration files to suit your particular needs.
467 \item Customize the configuration files for each of the three daemons
468 (Directory, File, Storage) and for the Console program. For the details
469 of how to do this, please see \ilink{Setting Up Bacula Configuration
470 Files}{ConfigureChapter} in the Configuration chapter of this manual. We
471 recommend that you start by modifying the default configuration files
472 supplied, making the minimum changes necessary. Complete customization
473 can be done after you have Bacula up and running. Please take care when
474 modifying passwords, which were randomly generated, and the {\bf Name}s
475 as the passwords and names must agree between the configuration files
476 for security reasons.
478 \label{CreateDatabase}
479 \item Create the Bacula MySQL database and tables
481 \ilink{Installing and Configuring MySQL Phase II}{mysql_phase2} or
482 create the Bacula PostgreSQL database and tables
483 \ilink{Configuring PostgreSQL
484 II}{PostgreSQL_configure} or alternatively if you are using
485 SQLite \ilink{Installing and Configuring SQLite Phase II}{phase2}.
487 \item Start Bacula ({\bf ./bacula start}) Note. the next chapter shows you
488 how to do this in detail.
490 \item Interface with Bacula using the Console program
492 \item For the previous two items, please follow the instructions in the
493 \ilink{Running Bacula}{TutorialChapter} chapter of this manual,
494 where you will run a simple backup and do a restore. Do this before you make
495 heavy modifications to the configuration files so that you are sure that
496 Bacula works and are familiar with it. After that changing the conf files
499 \item If after installing Bacula, you decide to "move it", that is to
500 install it in a different set of directories, proceed as follows:
506 ./configure (your-new-options)
515 If all goes well, the {\bf ./configure} will correctly determine which
516 operating system you are running and configure the source code appropriately.
517 Currently, FreeBSD, Linux (Red Hat), and Solaris are supported. The Bacula
518 client (File daemon) is reported to work with MacOS X 10.3 is if
519 readline support is not enabled (default) when building the client.
521 If you install Bacula on more than one system, and they are identical, you can
522 simply transfer the source tree to that other system and do a "make
523 install". However, if there are differences in the libraries or OS versions,
524 or you wish to install on a different OS, you should start from the original
525 compress tar file. If you do transfer the source tree, and you have previously
526 done a ./configure command, you MUST do:
534 prior to doing your new ./configure. This is because the GNU autoconf tools
535 cache the configuration, and if you re-use a configuration for a Linux machine
536 on a Solaris, you can be sure your build will fail. To avoid this, as
537 mentioned above, either start from the tar file, or do a "make distclean".
539 In general, you will probably want to supply a more complicated {\bf
540 configure} statement to ensure that the modules you want are built and that
541 everything is placed into the correct directories.
543 For example, on Fedora, Red Hat, or SuSE one could use the following:
549 --sbindir=/opt/bacula/bin \
550 --sysconfdir=/opt/bacula/etc \
551 --with-pid-dir=/var/run \
552 --with-subsys-dir=/var/run \
554 --with-working-dir=/opt/bacula/working \
555 --with-dump-email=$USER
559 The advantage of using the above configuration to start is that
560 everything will be put into a single directory, which you can later delete
561 once you have run the examples in the next chapter and learned how Bacula
562 works. In addition, the above can be installed and run as non-root.
564 For the developer's convenience, I have added a {\bf defaultconfig} script to
565 the {\bf examples} directory. This script contains the statements that you
566 would normally use, and each developer/user may modify them to suit his needs.
567 You should find additional useful examples in this directory as well.
569 The {\bf \verb:--:enable-conio} or {\bf \verb:--:enable-readline} options are
570 useful because they provide a command line history, editing capability for the
571 Console program and tab completion on various option. If you have included
572 either option in the build, either the {\bf termcap} or the {\bf ncurses}
573 package will be needed to link. On most systems, including Red Hat and SuSE,
574 you should include the ncurses package. If Bacula's configure process finds
575 the ncurses libraries, it will use those rather than the termcap library. On
576 some systems, such as SuSE, the termcap library is not in the standard library
577 directory. As a consequence, the option may be disabled or you may get an
578 error message such as:
582 /usr/lib/gcc-lib/i586-suse-linux/3.3.1/.../ld:
583 cannot find -ltermcap
584 collect2: ld returned 1 exit status
588 while building the Bacula Console. In that case, you will need to set the {\bf
589 LDFLAGS} environment variable prior to building.
593 export LDFLAGS="-L/usr/lib/termcap"
597 The same library requirements apply if you wish to use the readline subroutines
598 for command line editing, history and tab completion or if you are using a
599 MySQL library that requires encryption. If you need encryption, you can either
600 export the appropriate additional library options as shown above or,
601 alternatively, you can include them directly on the ./configure line as in:
605 LDFLAGS="-lssl -lcyrpto" \
606 ./configure <your-options>
610 On some systems such as Mandriva, readline tends to
611 gobble up prompts, which makes it totally useless. If this happens to you, use
612 the disable option, or if you are using version 1.33 and above try using {\bf
613 \verb:--:enable-conio} to use a built-in readline replacement. You will still need
614 either the termcap or the ncurses library, but it is unlikely that the {\bf conio}
615 package will gobble up prompts.
617 readline is no longer supported after version 1.34. The code within Bacula
618 remains, so it should be usable, and if users submit patches for it, we will
619 be happy to apply them. However, due to the fact that each version of
620 readline seems to be incompatible with previous versions, and that there
621 are significant differences between systems, we can no longer afford to
624 \section{What Database to Use?}
626 \index[general]{What Database to Use?}
627 \index[general]{Use!What Database to}
629 Before building Bacula you need to decide if you want to use SQLite, MySQL, or
630 PostgreSQL. If you are not already running MySQL or PostgreSQL, you might
631 want to start by testing with SQLite (not supported on Solaris).
632 This will greatly simplify the setup for you
633 because SQLite is compiled into Bacula an requires no administration. It
634 performs well and is suitable for small to medium sized installations (maximum
635 10-20 machines). However, we should note that a number of users have
636 had unexplained database corruption with SQLite. For that reason, we
637 recommend that you install either PostgreSQL or MySQL for production
640 If you wish to use MySQL as the Bacula catalog, please see the
641 \ilink{Installing and Configuring MySQL}{MySqlChapter} chapter of this
642 manual. You will need to install MySQL prior to continuing with the
643 configuration of Bacula. MySQL is a high quality database that is very
644 efficient and is suitable for small and medium sized installation (up to
645 2,000,000 files per job). It is slightly more complicated than SQLite to setup
646 and administer because it has a number of sophisticated features such as
647 userids and passwords. It runs as a separate process, is truly professional and
648 can manage a database of any size.
650 If you wish to use PostgreSQL as the Bacula catalog, please see the
651 \ilink{Installing and Configuring PostgreSQL}{PostgreSqlChapter} chapter of
652 this manual. You will need to install PostgreSQL prior to continuing with the
653 configuration of Bacula. PostgreSQL is very similar to MySQL, though it tends
654 to be slightly more SQL92 compliant and has many more advanced features such as
655 transactions, stored procedures, and the such. It requires a certain knowledge
656 to install and maintain. PostgreSQL is suitable for any sized installation
657 (some sites have much more than 1 billion objects in the Catalog). Bacula uses
658 many optimized PostgreSQL functions, and can run more than 10 time faster on
659 jobs having millions of files than MySQL (Specially in during restore, accurate
660 mode, bvfs queries and when the database server is not on the same host than
661 the Director). It's possible to switch from MySQL/SQLite to PostgreSQL, but it
662 requires some DBA knowledge.
664 If you wish to use SQLite as the Bacula catalog, please see
665 \ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of
666 this manual. SQLite is not supported on Solaris.
668 \section{Quick Start}
669 \index[general]{Quick Start}
670 \index[general]{Start!Quick}
672 There are a number of options and important considerations given below
673 that you can skip for the moment if you have not had any problems building
674 Bacula with a simplified configuration as shown above.
676 If the ./configure process is unable to find specific libraries (e.g.
677 libintl, you should ensure that the appropriate package is installed on
678 your system. Alternatively, if the package is installed in a non-standard
679 location (as far as Bacula is concerned), then there is generally an
680 option listed below (or listed with "./configure {-} {-}help" that will
681 permit you to specify the directory that should be searched. In other
682 cases, there are options that will permit you to disable to feature
683 (e.g. {-} {-}disable-nls).
685 If you want to dive right into it, we recommend you skip to the next chapter,
686 and run the example program. It will teach you a lot about Bacula and as an
687 example can be installed into a single directory (for easy removal) and run as
688 non-root. If you have any problems or when you want to do a real installation,
689 come back to this chapter and read the details presented below.
691 \section{Configure Options}
693 \index[general]{Options!Configure}
694 \index[general]{Configure Options}
696 The following command line options are available for {\bf configure} to
697 customize your installation.
700 \item [ \--prefix=\lt{}patch\gt{}]
701 \index[general]{{-}prefix}
702 This option is meant to allow you to direct where the architecture
703 independent files should be placed. However, we find this a somewhat
704 vague concept, and so we have not implemented this option other than
705 to use any explicit prefix that you may define. If you do not
706 explicitly specify a prefix, Bacula's configure routine will not use
707 the default value that ./configure --help prints.
708 As a consequence, we suggest that
709 you avoid it. We have provided options that allow you to explicitly
710 specify the directories for each of the major categories of installation
712 \item [ {-}{\-}sbindir=\lt{}binary-path\gt{}]
713 \index[general]{{-}{\-}sbindir}
714 Defines where the Bacula binary (executable) files will be placed during a
715 {\bf make install} command.
717 \item [ {-}{\-}sysconfdir=\lt{}config-path\gt{}]
718 \index[general]{{-}{\-}sysconfdir}
719 Defines where the Bacula configuration files should be placed during a
720 {\bf make install} command. Note, for security reasons,
721 this directory should be unique to Bacula and not read/writable by
722 any other user/group than Bacula is running under.
724 \item [ {-}{\-}mandir=\lt{}path\gt{}]
725 \index[general]{{-}{\-}mandir}
726 Note, as of Bacula version 1.39.14, the meaning of any path
727 specified on this option is change from prior versions. It
728 now specifies the top level man directory.
729 Previously the mandir specified the full path to where you
730 wanted the man files installed.
731 The man files will be installed in gzip'ed format under
732 mandir/man1 and mandir/man8 as appropriate.
733 For the install to succeed you must have {\bf gzip} installed
736 By default, Bacula will install the Unix man pages in
737 /usr/share/man/man1 and /usr/share/man/man8.
738 If you wish the man page to be installed in
739 a different location, use this option to specify the path.
740 Note, the main HTML and PDF Bacula documents are in a separate
741 tar file that is not part of the source distribution.
743 \item [ {-}{\-}datadir=\lt{}path\gt{} ]
744 \index[general]{{-}{\-}datadir}
745 If you translate Bacula or parts of Bacula into a different language
746 you may specify the location of the po files using the {\bf
747 {-}{\-}datadir} option. You must manually install any po files as
748 Bacula does not (yet) automatically do so.
750 \item [ {-}{\-}disable-ipv6 ]
751 \index[general]{{-}{\-}disable-ipv6}
753 \item [ {-}{\-}enable-smartalloc ]
754 \index[general]{{-}{\-}enable-smartalloc}
755 This enables the inclusion of the Smartalloc orphaned buffer detection
756 code. This option is highly recommended. Because we never build
757 without this option, you may experience problems if it is not enabled.
758 In this case, simply re-enable the option. We strongly recommend
759 keeping this option enabled as it helps detect memory leaks. This
760 configuration parameter is used while building Bacula
762 \item [ {-}{\-}enable-bat ]
764 \index[general]{{-}{\-}enable-bat}
765 If you have Qt4 >= 4.3.4 installed on your computer including the
766 libqt4 and libqt4-devel (libqt4-dev on Debian) libraries, and you want
767 to use the Bacula Administration Tool (bat) GUI Console interface to
768 Bacula, you must specify this option. Doing so will build everything in
769 the {\bf src/qt-console} directory. The build with enable-bat will work
770 only with a full Bacula build (i.e. it will not work with a client-only
773 Qt4 is available on OpenSUSE 10.2, CentOS 5, Fedora, and Debian. If it
774 is not available on your system, you can download the {\bf depkgs-qt}
775 package from the Bacula Source Forge download area and build it.
777 INSTALL file in that package for more details. In particular to use
778 the Qt4 built by {\bf depkgs-qt} you {\bf must} source the file
781 \item [ {-}{\-}enable-batch-insert ]
782 \index[general]{{-}{\-}enable-batch-insert}
783 This option enables batch inserts of the attribute records (default) in
784 the catalog database, which is much faster (10 times or more) than
785 without this option for large numbers of files. However, this option
786 will automatically be disabled if your SQL libraries are not
787 thread safe. If you find that batch mode is not enabled on your Bacula
788 installation, then your database most likely does not support threads.
790 SQLite2 is not thread safe. Batch insert cannot be enabled when using
793 On most systems, MySQL, PostgreSQL and SQLite3 are thread safe.
795 To verify that your PostgreSQL is thread safe, you can try this
796 (change the path to point to your particular installed libpq.a;
797 these commands were issued on FreeBSD 6.2):
800 $ nm /usr/local/lib/libpq.a | grep PQputCopyData
801 00001b08 T PQputCopyData
802 $ nm /usr/local/lib/libpq.a | grep mutex
804 U pthread_mutex_unlock
807 U pthread_mutex_unlock
810 The above example shows a libpq that contains the required function
811 PQputCopyData and is thread enabled (i.e. the pthread\_mutex* entries).
812 If you do not see PQputCopyData, your version of PostgreSQL is too old
813 to allow batch insert. If you do not see the mutex entries, then thread
814 support has not been enabled. Our tests indicate you usually need to
815 change the configuration options and recompile/reinstall the PostgreSQL
816 client software to get thread support.
818 Bacula always links to the thread safe MySQL libraries.
820 Running with Batch Insert turned on is recommended because it can
821 significantly improve attribute insertion times. However, it does
822 put a significantly larger part of the work on your SQL engine, so
823 you may need to pay more attention to tuning it. In particular,
824 Batch Insert can require large temporary table space, and consequently,
825 the default location (often /tmp) may run out of space causing errors.
826 For MySQL, the location is set in my.conf with "tmpdir". You may also
827 want to increase the memory available to your SQL engine to further
828 improve performance during Batch Inserts.
830 \item [ {-}{\-}enable-bwx-console ]
831 \index[general]{{-}{\-}enable-bwx-console}
832 If you have wxWidgets installed on your computer and you want to use the
833 wxWidgets GUI Console interface to Bacula, you must specify this option.
834 Doing so will build everything in the {\bf src/wx-console} directory.
835 This could also be useful to users who want a GUI Console and don't want
836 to install QT, as wxWidgets can work with GTK+, Motif or even X11
839 \item [ {-}{\-}enable-tray-monitor ]
840 \index[general]{{-}{\-}enable-tray-monitor}
841 If you have GTK installed on your computer, you run a graphical
842 environment or a window manager compatible with the FreeDesktop system
843 tray standard (like KDE and GNOME) and you want to use a GUI to monitor
844 Bacula daemons, you must specify this option. Doing so will build
845 everything in the {\bf src/tray-monitor} directory. Note, due to
846 restrictions on what can be linked with GPLed code, we were forced to
847 remove the egg code that dealt with the tray icons and replace it by
848 calls to the GTK+ API, and unfortunately, the tray icon API necessary
849 was not implemented until GTK version 2.10 or later.
851 \item [ {-}{\-}enable-static-tools]
852 \index[general]{{-}{\-}enable-static-tools}
853 This option causes the linker to link the Storage daemon utility tools
854 ({\bf bls}, {\bf bextract}, and {\bf bscan}) statically. This permits
855 using them without having the shared libraries loaded. If you have
856 problems linking in the {\bf src/stored} directory, make sure you have
857 not enabled this option, or explicitly disable static linking by adding
858 {\bf \verb:--:disable-static-tools}.
860 \item [ {-}{\-}enable-static-fd]
861 \index[general]{{-}{\-}enable-static-fd}
862 This option causes the make process to build a {\bf static-bacula-fd} in
863 addition to the standard File daemon. This static version will include
864 statically linked libraries and is required for the Bare Metal recovery.
865 This option is largely superseded by using {\bf make static-bacula-fd}
866 from with in the {\bf src/filed} directory. Also, the {\bf
867 \verb:--:enable-client-only} option described below is useful for just
868 building a client so that all the other parts of the program are not
871 When linking a static binary, the linker needs the static versions
872 of all the libraries that are used, so frequently users will
873 experience linking errors when this option is used. The first
874 thing to do is to make sure you have the static glibc library
875 installed on your system. The second thing to do is the make sure
876 you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python}
877 on your ./configure statement as these options require additional
878 libraries. You may be able to enable those options, but you will
879 need to load additional static libraries.
882 \item [ {-}{\-}enable-static-sd]
883 \index[general]{{-}{\-}enable-static-sd}
884 This option causes the make process to build a {\bf static-bacula-sd} in
885 addition to the standard Storage daemon. This static version will
886 include statically linked libraries and could be useful during a Bare
889 When linking a static binary, the linker needs the static versions
890 of all the libraries that are used, so frequently users will
891 experience linking errors when this option is used. The first
892 thing to do is to make sure you have the static glibc library
893 installed on your system. The second thing to do is the make sure
894 you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python}
895 on your ./configure statement as these options require additional
896 libraries. You may be able to enable those options, but you will
897 need to load additional static libraries.
900 \item [ {-}{\-}enable-static-dir]
901 \index[general]{{-}{\-}enable-static-dir}
902 This option causes the make process to build a {\bf static-bacula-dir}
903 in addition to the standard Director. This static version will include
904 statically linked libraries and could be useful during a Bare Metal
907 When linking a static binary, the linker needs the static versions
908 of all the libraries that are used, so frequently users will
909 experience linking errors when this option is used. The first
910 thing to do is to make sure you have the static glibc library
911 installed on your system. The second thing to do is the make sure
912 you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python}
913 on your ./configure statement as these options require additional
914 libraries. You may be able to enable those options, but you will
915 need to load additional static libraries.
918 \item [ {-}{\-}enable-static-cons]
919 \index[general]{{-}{\-}enable-static-cons}
920 This option causes the make process to build a {\bf static-console} in
921 addition to the standard console. This static version will include
922 statically linked libraries and could be useful during a Bare Metal
925 When linking a static binary, the linker needs the static versions
926 of all the libraries that are used, so frequently users will
927 experience linking errors when this option is used. The first
928 thing to do is to make sure you have the static glibc library
929 installed on your system. The second thing to do is the make sure
930 you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python}
931 on your ./configure statement as these options require additional
932 libraries. You may be able to enable those options, but you will
933 need to load additional static libraries.
936 \item [ {-}{\-}enable-client-only]
937 \index[general]{{-}{\-}enable-client-only}
938 This option causes the make process to build only the File daemon and
939 the libraries that it needs. None of the other daemons, storage tools,
940 nor the console will be built. Likewise a {\bf make install} will then
941 only install the File daemon. To cause all daemons to be built, you
942 will need to do a configuration without this option. This option
943 greatly facilitates building a Client on a client only machine.
945 When linking a static binary, the linker needs the static versions
946 of all the libraries that are used, so frequently users will
947 experience linking errors when this option is used. The first
948 thing to do is to make sure you have the static glibc library
949 installed on your system. The second thing to do is the make sure
950 you do not specify {\bf {-}{\-}openssl} or {\bf {-}{\-}with-python}
951 on your ./configure statement as these options require additional
952 libraries. You may be able to enable those options, but you will
953 need to load additional static libraries.
955 \item [ {-}{\-}enable-build-dird]
956 \index[general]{{-}{\-}enable-build-dird}
957 This option causes the make process to build the Director and the
958 Director's tools. By default, this option is on, but you may turn
959 it off by using {\bf {-}{\-}disable-build-dird} to prevent the
960 Director from being built.
962 \item [ {-}{\-}enable-build-stored]
963 \index[general]{{-}{\-}enable-build-stored}
964 This option causes the make process to build the Storage daemon.
965 By default, this option is on, but you may turn
966 it off by using {\bf {-}{\-}disable-build-stored} to prevent the
967 Storage daemon from being built.
970 \item [ {-}{\-}enable-largefile]
971 \index[general]{{-}{\-}enable-largefile}
972 This option (default) causes Bacula to be built with 64 bit file address
973 support if it is available on your system. This permits Bacula to read and
974 write files greater than 2 GBytes in size. You may disable this feature and
975 revert to 32 bit file addresses by using {\bf \verb:--:disable-largefile}.
977 \item [ {-}{\-}disable-nls]
978 \index[general]{{-}{\-}disable-nls}
979 By default, Bacula uses the GNU Native Language Support (NLS) libraries. On
980 some machines, these libraries may not be present or may not function
981 correctly (especially on non-Linux implementations). In such cases, you
982 may specify {\bf {-}{\-}disable-nls} to disable use of those libraries.
983 In such a case, Bacula will revert to using English.
985 \item [ {-}{\-}disable-ipv6 ]
986 \index[general]{{-}{\-}disable-ipv6}
987 By default, Bacula enables IPv6 protocol. On some systems, the files
988 for IPv6 may exist, but the functionality could be turned off in the
989 kernel. In that case, in order to correctly build Bacula, you will
990 explicitly need to use this option so that Bacula does not attempt
991 to reference OS function calls that do not exist.
993 \item [ {-}{\-}with-sqlite3=\lt{}sqlite3-path\gt{}]
994 \index[general]{{-}{\-}with-sqlite3}
995 This enables use of the SQLite version 3.x database. The {\bf
996 sqlite3-path} is not normally specified as Bacula looks for the
997 necessary components in a standard location ({\bf depkgs/sqlite3}). See
998 \ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of
999 this manual for more details. SQLite3 is not supported on Solaris.
1001 \item [ {-}{\-}with-mysql=\lt{}mysql-path\gt{}]
1002 \index[general]{{-}{\-}with-mysql}
1003 This enables building of the Catalog services for Bacula. It assumes
1004 that MySQL is running on your system, and expects it to be installed in
1005 the {\bf mysql-path} that you specify. Normally, if MySQL is installed
1006 in a standard system location, you can simply use {\bf {-}{\-}with-mysql}
1007 with no path specification. If you do use this option, please proceed
1008 to installing MySQL in the \ilink{Installing and Configuring
1009 MySQL}{MySqlChapter} chapter before proceeding with the configuration.
1011 See the note below under the {-}{\-}with-postgresql item.
1013 \item [ {-}{\-}with-postgresql=\lt{}path\gt{}]
1014 \index[general]{{-}{\-}with-postgresql}
1015 This provides an explicit path to the PostgreSQL libraries if Bacula
1016 cannot find it by default. Normally to build with PostgreSQL, you would
1017 simply use {\bf {-}{\-}with-postgresql}.
1019 Note, for Bacula to be configured properly, you must specify one
1020 of the four database options supported. That is:
1021 {-}{\-}with-sqlite, {-}{\-}with-sqlite3, {-}{\-}with-mysql, or
1022 {-}{\-}with-postgresql, otherwise the ./configure will fail.
1024 \item [ {-}{\-}with-openssl=\lt{}path\gt{}]
1025 This configuration option is necessary if you want to enable TLS (ssl),
1026 which encrypts the communications within
1027 Bacula or if you want to use File Daemon PKI data encryption.
1028 Normally, the {\bf path} specification is not necessary since
1029 the configuration searches for the OpenSSL libraries in standard system
1030 locations. However, you must ensure that all the libraries are
1031 loaded including {\bf libssl-dev} or the equivalent on your
1032 system. Enabling OpenSSL in Bacula permits secure communications
1033 between the daemons and/or data encryption in the File daemon.
1034 For more information on using TLS, please see the
1035 \ilink{Bacula TLS -- Communications Encryption}{CommEncryption} chapter
1037 For more information on using PKI data encryption, please see the
1038 \ilink{Bacula PKI -- Data Encryption}{DataEncryption}
1039 chapter of this manual.
1041 If you get errors linking, you need to load the development libraries,
1042 or you need to disable SSL by setting without-openssl.
1045 \item [ {-}{\-}with-python=\lt{}path\gt{}]
1046 \index[general]{{-}{\-}with-python}
1047 This option enables Bacula support for Python. If no path is supplied,
1048 configure will search the standard library locations for Python 2.2,
1049 2.3, 2.4, or 2.5. If it cannot find the library, you will need to
1050 supply a path to your Python library directory. Please see the
1051 \ilink{Python chapter}{PythonChapter} for the details of using Python
1054 \item [ {-}{\-}with-libintl-prefix=\lt{}DIR\gt{}]
1055 \index[general]{{-}{\-}with-libintl-prefix}
1056 This option may be used to tell Bacula to search DIR/include and
1057 DIR/lib for the libintl headers and libraries needed for Native
1058 Language Support (NLS).
1060 \item [ {-}{\-}enable-conio]
1061 \index[general]{{-}{\-}enable-conio}
1062 Tells Bacula to enable building the small, light weight readline
1063 replacement routine. It is generally much easier to configure than
1064 readline, although, like readline, it needs either the termcap or
1067 \item [ {-}{\-}with-readline=\lt{}readline-path\gt{}]
1068 \index[general]{{-}{\-}with-readline}
1069 Tells Bacula where {\bf readline} is installed. Normally, Bacula will
1070 find readline if it is in a standard library. If it is not found and no
1071 {-}{\-}with-readline is specified, readline will be disabled. This
1072 option affects the Bacula build. Readline provides the Console program
1073 with a command line history and editing capability and is no longer
1074 supported, so you are on your own if you have problems.
1076 \item [ {-}{\-}enable-readline]
1077 \index[general]{{-}{\-}enable-readline}
1078 Tells Bacula to enable readline support. It is normally disabled due to the
1079 large number of configuration problems and the fact that the package seems to
1080 change in incompatible ways from version to version.
1082 \item [ {-}{\-}with-tcp-wrappers=\lt{}path\gt{}]
1083 \index[general]{{-}{\-}with-tcp-wrappers}
1084 \index[general]{TCP Wrappers}
1085 \index[general]{Wrappers!TCP}
1086 \index[general]{libwrappers}
1087 This specifies that you want TCP wrappers (man hosts\_access(5)) compiled in.
1088 The path is optional since Bacula will normally find the libraries in the
1089 standard locations. This option affects the Bacula build. In specifying your
1090 restrictions in the {\bf /etc/hosts.allow} or {\bf /etc/hosts.deny} files, do
1091 not use the {\bf twist} option (hosts\_options(5)) or the Bacula process will
1092 be terminated. Note, when setting up your {\bf /etc/hosts.allow}
1093 or {\bf /etc/hosts.deny}, you must identify the Bacula daemon in
1094 question with the name you give it in your conf file rather than the
1095 name of the executable.
1097 For more information on configuring and testing TCP wrappers, please see the
1098 \ilink{Configuring and Testing TCP Wrappers}{wrappers} section
1099 in the Security Chapter.
1101 On SuSE, the libwrappers libraries needed to link Bacula are
1102 contained in the tcpd-devel package. On Red Hat, the package is named
1105 \item [ {-}{\-}with-archivedir=\lt{}path\gt{} ]
1106 \index[general]{{-}{\-}with-archivedir}
1107 The directory used for disk-based backups. Default value is /tmp.
1108 This parameter sets the default values in the bacula-dir.conf and bacula-sd.conf
1109 configuration files. For example, it sets the Where directive for the
1110 default restore job and the Archive Device directive for the FileStorage
1113 This option is designed primarily for use in regression testing.
1114 Most users can safely ignore this option.
1116 \item [ {-}{\-}with-working-dir=\lt{}working-directory-path\gt{} ]
1117 \index[general]{{-}{\-}with-working-dir}
1118 This option is mandatory and specifies a directory into which Bacula may
1119 safely place files that will remain between Bacula executions. For example,
1120 if the internal database is used, Bacula will keep those files in this
1121 directory. This option is only used to modify the daemon configuration
1122 files. You may also accomplish the same thing by directly editing them later.
1123 The working directory is not automatically created by the install process, so
1124 you must ensure that it exists before using Bacula for the first time.
1126 \item [ {-}{\-}with-baseport=\lt{}port=number\gt{}]
1127 \index[general]{{-}{\-}with-baseport}
1128 In order to run, Bacula needs three TCP/IP ports (one for the Bacula
1129 Console, one for the Storage daemon, and one for the File daemon). The {\bf
1130 \verb:--:with-baseport} option will automatically assign three ports beginning at
1131 the base port address specified. You may also change the port number in the
1132 resulting configuration files. However, you need to take care that the
1133 numbers correspond correctly in each of the three daemon configuration
1134 files. The default base port is 9101, which assigns ports 9101 through 9103.
1135 These ports (9101, 9102, and 9103) have been officially assigned to Bacula by
1136 IANA. This option is only used to modify the daemon configuration files. You
1137 may also accomplish the same thing by directly editing them later.
1139 \item [ {-}{\-}with-dump-email=\lt{}email-address\gt{}]
1140 \index[general]{{-}{\-}with-dump-email}
1141 This option specifies the email address where any core dumps should be set.
1142 This option is normally only used by developers.
1144 \item [ {-}{\-}with-pid-dir=\lt{}PATH\gt{} ]
1145 \index[general]{{-}{\-}with-pid-dir}
1146 This specifies where Bacula should place the process id file during
1147 execution. The default is: {\bf /var/run}. This directory is not created by
1148 the install process, so you must ensure that it exists before using Bacula
1151 \item [ {-}{\-}with-subsys-dir=\lt{}PATH\gt{}]
1152 \index[general]{{-}{\-}with-subsys-dir}
1153 This specifies where Bacula should place the subsystem lock file during
1154 execution. The default is {\bf /var/run/subsys}. Please make sure that you do
1155 not specify the same directory for this directory and for the {\bf sbindir}
1156 directory. This directory is used only within the autostart scripts. The
1157 subsys directory is not created by the Bacula install, so you must be sure to
1158 create it before using Bacula.
1160 \item [ {-}{\-}with-dir-password=\lt{}Password\gt{}]
1161 \index[general]{{-}{\-}with-dir-password}
1162 This option allows you to specify the password used to access the Director
1163 (normally from the Console program). If it is not specified, configure will
1164 automatically create a random password.
1166 \item [ {-}{\-}with-fd-password=\lt{}Password\gt{} ]
1167 \index[general]{{-}{\-}with-fd-password}
1168 This option allows you to specify the password used to access the File daemon
1169 (normally called from the Director). If it is not specified, configure will
1170 automatically create a random password.
1172 \item [ {-}{\-}with-sd-password=\lt{}Password\gt{} ]
1173 \index[general]{{-}{\-}with-sd-password}
1174 This option allows you to specify the password used to access the Storage daemon
1175 (normally called from the Director). If it is not specified, configure will
1176 automatically create a random password.
1178 \item [ {-}{\-}with-dir-user=\lt{}User\gt{} ]
1179 \index[general]{{-}{\-}with-dir-user}
1180 This option allows you to specify the Userid used to run the Director. The
1181 Director must be started as root, but doesn't need to run as root, and
1182 after doing preliminary initializations, it can "drop" to the UserId
1183 specified on this option.
1184 If you specify this option, you must
1185 create the User prior to running {\bf make install}, because the
1186 working directory owner will be set to {\bf User}.
1188 \item [ {-}{\-}with-dir-group=\lt{}Group\gt{} ]
1189 \index[general]{{-}{\-}with-dir-group}
1190 This option allows you to specify the GroupId used to run the Director. The
1191 Director must be started as root, but doesn't need to run as root, and after
1192 doing preliminary initializations, it can "drop" to the GroupId specified
1194 If you specify this option, you must
1195 create the Group prior to running {\bf make install}, because the
1196 working directory group will be set to {\bf Group}.
1198 \item [ {-}{\-}with-sd-user=\lt{}User\gt{} ]
1199 \index[general]{{-}{\-}with-sd-user}
1200 This option allows you to specify the Userid used to run the Storage daemon.
1201 The Storage daemon must be started as root, but doesn't need to run as root,
1202 and after doing preliminary initializations, it can "drop" to the UserId
1203 specified on this option. If you use this option, you will need to take care
1204 that the Storage daemon has access to all the devices (tape drives, ...) that
1207 \item [ {-}{\-}with-sd-group=\lt{}Group\gt{} ]
1208 \index[general]{{-}{\-}with-sd-group}
1209 This option allows you to specify the GroupId used to run the Storage daemon.
1210 The Storage daemon must be started as root, but doesn't need to run as root,
1211 and after doing preliminary initializations, it can "drop" to the GroupId
1212 specified on this option.
1214 \item [ {-}{\-}with-fd-user=\lt{}User\gt{} ]
1215 \index[general]{{-}{\-}with-fd-user}
1216 This option allows you to specify the Userid used to run the File daemon. The
1217 File daemon must be started as root, and in most cases, it needs to run as
1218 root, so this option is used only in very special cases, after doing
1219 preliminary initializations, it can "drop" to the UserId specified on this
1222 \item [ {-}{\-}with-fd-group=\lt{}Group\gt{} ]
1223 \index[general]{{-}{\-}with-fd-group}
1224 This option allows you to specify the GroupId used to run the File daemon.
1225 The File daemon must be started as root, and in most cases, it must be run as
1226 root, however, after doing preliminary initializations, it can "drop" to
1227 the GroupId specified on this option.
1229 \item [ {-}{\-}with-mon-dir-password=\lt{}Password\gt{}]
1230 \index[general]{{-}{\-}with-mon-dir-password}
1231 This option allows you to specify the password used to access the Directory
1232 from the monitor. If it is not specified, configure will
1233 automatically create a random password.
1235 \item [ {-}{\-}with-mon-fd-password=\lt{}Password\gt{} ]
1236 \index[general]{{-}{\-}with-mon-fd-password}
1237 This option allows you to specify the password used to access the File daemon
1238 from the Monitor. If it is not specified, configure will
1239 automatically create a random password.
1241 \item [ {-}{\-}with-mon-sd-password=\lt{}Password\gt{} ]
1242 \index[general]{{-}{\-}with-mon-sd-password}
1243 This option allows you to specify the password used to access the
1244 Storage daemon from the Monitor. If it is not specified, configure will
1245 automatically create a random password.
1247 \item [ {-}{\-}with-db-name=\lt{}database-name\gt{} ]
1248 \index[general]{{-}{\-}with-db-name}
1249 This option allows you to specify the database name to be used in
1250 the conf files. The default is bacula.
1252 \item [ {-}{\-}with-db-user=\lt{}database-user\gt{} ]
1253 \index[general]{{-}{\-}with-db-user}
1254 This option allows you to specify the database user name to be used in
1255 the conf files. The default is bacula.
1259 Note, many other options are presented when you do a {\bf ./configure
1260 \verb:--:help}, but they are not implemented.
1262 \section{Recommended Options for Most Systems}
1263 \index[general]{Systems!Recommended Options for Most}
1264 \index[general]{Recommended Options for Most Systems}
1266 For most systems, we recommend starting with the following options:
1271 --enable-smartalloc \
1272 --sbindir=/opt/bacula/bin \
1273 --sysconfdir=/opt/bacula/etc \
1274 --with-pid-dir=/opt/bacula/working \
1275 --with-subsys-dir=/opt/bacula/working \
1276 --with-working-dir=/opt/bacula/working
1280 If you want to install Bacula in an installation directory rather than run it
1281 out of the build directory (as developers will do most of the time), you
1282 should also include the \verb:--:sbindir and \verb:--:sysconfdir options with appropriate
1283 paths. Neither are necessary if you do not use "make install" as is the case
1284 for most development work. The install process will create the sbindir and
1285 sysconfdir if they do not exist, but it will not automatically create the
1286 pid-dir, subsys-dir, or working-dir, so you must ensure that they exist before
1287 running Bacula for the first time.
1290 \index[general]{Red Hat}
1297 CFLAGS="-g -Wall" ./configure \
1298 --sbindir=/opt/bacula/bin \
1299 --sysconfdir=/opt/bacula/etc \
1300 --enable-smartalloc \
1301 --with-sqlite=$HOME/bacula/depkgs/sqlite \
1302 --with-working-dir=/opt/bacula/working \
1303 --with-pid-dir=/opt/bacula/working \
1304 --with-subsys-dir=/opt/bacula/working \
1315 CFLAGS="-g -Wall" ./configure \
1316 --sbindir=/opt/bacula/bin \
1317 --sysconfdir=/opt/bacula/etc \
1318 --enable-smartalloc \
1320 --with-working-dir=/opt/bacula/working
1321 --with-pid-dir=/opt/bacula/working \
1322 --with-subsys-dir=/opt/bacula/working
1327 or finally, a completely traditional Red Hat Linux install,
1328 which we do not recommend, because it make it harder to
1329 backup Bacula for disaster recovery purposes:
1333 CFLAGS="-g -Wall" ./configure \
1334 --sbindir=/usr/sbin \
1335 --sysconfdir=/etc/bacula \
1336 --with-scriptdir=/etc/bacula \
1337 --enable-smartalloc \
1340 --with-working-dir=/var/bacula \
1341 --with-pid-dir=/var/run \
1346 Note, Bacula assumes that /var/bacula, /var/run, and /var/lock/subsys exist so
1347 it will not automatically create them during the install process.
1350 \index[general]{Solaris}
1352 To build Bacula from source, you will need the following installed on your
1353 system (they are not by default): libiconv, gcc 3.3.2, stdc++, libgcc (for
1354 stdc++ and gcc\_s libraries), make 3.8 or later.
1356 You will probably also need to: Add /usr/local/bin to PATH and Add
1357 /usr/ccs/bin to PATH for ar.
1359 It is possible to build Bacula on Solaris with the Solaris compiler, but
1360 we recommend using GNU C++ if possible.
1362 A typical configuration command might look like:
1367 CFLAGS="-g" ./configure \
1368 --sbindir=/opt/bacula/bin \
1369 --sysconfdir=/opt/bacula/etc \
1371 --enable-smartalloc \
1372 --with-pid-dir=/opt/bacula/working \
1373 --with-subsys-dir=/opt/bacula/working \
1374 --with-working-dir=/opt/bacula/working
1378 Note, you may need to install the following packages to build Bacula
1399 PATH=/usr/bin::/usr/ccs/bin:/etc:/usr/openwin/bin:/usr/local/bin:/usr/sfw/bin:/opt/sfw/bin:/usr/ucb:/usr/sbin
1403 If you have installed special software not normally in the Solaris
1404 libraries, such as OpenSSL, or the packages shown above, then you may need
1405 to add {\bf /usr/sfw/lib} to the library search path. Probably the
1406 simplest way to do so is to run:
1410 setenv LDFLAGS "-L/usr/sfw/lib -R/usr/sfw/lib"
1414 Prior to running the ./configure command.
1416 Alternatively, you can set the LD\_LIBARY\_PATH and/or the LD\_RUN\_PATH
1417 environment variables appropriately.
1419 It is also possible to use the {\bf crle} program to set the library
1420 search path. However, this should be used with caution.
1423 \index[general]{FreeBSD}
1426 \elink{The FreeBSD Diary}{http://www.freebsddiary.org/bacula.php} for a
1427 detailed description on how to make Bacula work on your system. In addition,
1428 users of FreeBSD prior to 4.9-STABLE dated Mon Dec 29 15:18:01 2003 UTC who
1429 plan to use tape devices, please see the
1430 \ilink{Tape Testing Chapter}{FreeBSDTapes} of this manual for
1431 {\bf important} information on how to configure your tape drive for
1432 compatibility with Bacula.
1434 If you are using Bacula with MySQL, you should take care to compile MySQL with
1435 FreeBSD native threads rather than LinuxThreads, since Bacula is normally built
1436 with FreeBSD native threads rather than LinuxTreads. Mixing the two will
1440 \index[general]{Win32}
1442 To install the binary Win32 version of the File daemon please see the
1443 \ilink{Win32 Installation Chapter}{Win32Chapter} in this document.
1445 \section{One File Configure Script}
1446 \index[general]{Script!One File Configure}
1447 \index[general]{One Files Configure Script}
1449 The following script could be used if you want to put everything
1450 in a single directory (except for the working directory):
1457 --sbindir=$HOME/bacula/bin \
1458 --sysconfdir=$HOME/bacula/bin \
1459 --mandir=$HOME/bacula/bin \
1460 --enable-smartalloc \
1462 --with-pid-dir=$HOME/bacula/bin/working \
1463 --with-subsys-dir=$HOME/bacula/bin/working \
1465 --with-working-dir=$HOME/bacula/bin/working \
1466 --with-dump-email=$USER@your-site.com \
1467 --with-job-email=$USER@your-site.com \
1468 --with-smtp-host=mail.your-site.com
1473 You may also want to put the following entries in your {\bf /etc/services}
1474 file as it will make viewing the connections made by Bacula easier to
1475 recognize (i.e. netstat -a):
1485 \section{Installing Bacula}
1486 \index[general]{Bacula!Installing}
1487 \index[general]{Installing Bacula}
1489 Before setting up your configuration files, you will want to install Bacula in
1490 its final location. Simply enter:
1498 If you have previously installed Bacula, the old binaries will be overwritten,
1499 but the old configuration files will remain unchanged, and the "new"
1500 configuration files will be appended with a {\bf .new}. Generally if you have
1501 previously installed and run Bacula you will want to discard or ignore the
1502 configuration files with the appended {\bf .new}.
1504 \section{Building a File Daemon or Client}
1505 \index[general]{Client!Building a File Daemon or}
1506 \index[general]{Building a File Daemon or Client}
1508 If you run the Director and the Storage daemon on one machine and you wish to
1509 back up another machine, you must have a copy of the File daemon for that
1510 machine. If the machine and the Operating System are identical, you can simply
1511 copy the Bacula File daemon binary file {\bf bacula-fd} as well as its
1512 configuration file {\bf bacula-fd.conf} then modify the name and password in
1513 the conf file to be unique. Be sure to make corresponding additions to the
1514 Director's configuration file ({\bf bacula-dir.conf}).
1516 If the architecture or the OS level are different, you will need to build a
1517 File daemon on the Client machine. To do so, you can use the same {\bf
1518 ./configure} command as you did for your main program, starting either from a
1519 fresh copy of the source tree, or using {\bf make\ distclean} before the {\bf
1522 Since the File daemon does not access the Catalog database, you can remove
1523 the {\bf \verb:--:with-mysql} or {\bf \verb:--:with-sqlite} options, then
1524 add {\bf \verb:--:enable-client-only}. This will compile only the
1525 necessary libraries and the client programs and thus avoids the necessity
1526 of installing one or another of those database programs to build the File
1527 daemon. With the above option, you simply enter {\bf make} and just the
1528 client will be built.
1531 \section{Auto Starting the Daemons}
1532 \index[general]{Daemons!Auto Starting the}
1533 \index[general]{Auto Starting the Daemons}
1535 If you wish the daemons to be automatically started and stopped when your
1536 system is booted (a good idea), one more step is necessary. First, the
1537 ./configure process must recognize your system -- that is it must be a
1538 supported platform and not {\bf unknown}, then you must install the platform
1539 dependent files by doing:
1544 make install-autostart
1548 Please note, that the auto-start feature is implemented only on systems
1549 that we officially support (currently, FreeBSD, Red Hat/Fedora Linux, and
1550 Solaris), and has only been fully tested on Fedora Linux.
1552 The {\bf make install-autostart} will cause the appropriate startup scripts
1553 to be installed with the necessary symbolic links. On Red Hat/Fedora Linux
1554 systems, these scripts reside in {\bf /etc/rc.d/init.d/bacula-dir} {\bf
1555 /etc/rc.d/init.d/bacula-fd}, and {\bf /etc/rc.d/init.d/bacula-sd}. However
1556 the exact location depends on what operating system you are using.
1558 If you only wish to install the File daemon, you may do so with:
1562 make install-autostart-fd
1566 \section{Other Make Notes}
1567 \index[general]{Notes!Other Make}
1568 \index[general]{Other Make Notes}
1570 To simply build a new executable in any directory, enter:
1578 To clean out all the objects and binaries (including the files named 1, 2, or
1579 3, which are development temporary files), enter:
1587 To really clean out everything for distribution, enter:
1595 note, this cleans out the Makefiles and is normally done from the top level
1596 directory to prepare for distribution of the source. To recover from this
1597 state, you must redo the {\bf ./configure} in the top level directory, since
1598 all the Makefiles will be deleted.
1600 To add a new file in a subdirectory, edit the Makefile.in in that directory,
1601 then simply do a {\bf make}. In most cases, the make will rebuild the Makefile
1602 from the new Makefile.in. In some case, you may need to issue the {\bf make} a
1603 second time. In extreme cases, cd to the top level directory and enter: {\bf
1606 To add dependencies:
1614 The {\bf make depend} appends the header file dependencies for each of the
1615 object files to Makefile and Makefile.in. This command should be done in each
1616 directory where you change the dependencies. Normally, it only needs to be run
1617 when you add or delete source or header files. {\bf make depend} is normally
1618 automatically invoked during the configuration process.
1628 This not normally done if you are developing Bacula, but is used if you are
1629 going to run it to backup your system.
1631 After doing a {\bf make install} the following files will be installed on your
1632 system (more or less). The exact files and location (directory) for each file
1633 depends on your {\bf ./configure} command (e.g. if you are using SQLite instead
1634 of MySQL, some of the files will be different).
1636 NOTE: it is quite probable that this list is out of date. But it is a
1658 create_mysql_database
1660 delete_catalog_backup
1679 \section{Installing Tray Monitor}
1680 \index[general]{Monitor!Installing Tray}
1681 \index[general]{Installing Tray Monitor}
1683 The Tray Monitor is already installed if you used the {\bf
1684 \verb:--:enable-tray-monitor} configure option and ran {\bf make install}.
1686 As you don't run your graphical environment as root (if you do, you should
1687 change that bad habit), don't forget to allow your user to read {\bf
1688 tray-monitor.conf}, and to execute {\bf bacula-tray-monitor} (this is not a
1691 Then log into your graphical environment (KDE, GNOME or something else), run
1692 {\bf bacula-tray-monitor} as your user, and see if a cassette icon appears
1693 somewhere on the screen, usually on the task bar.
1694 If it doesn't, follow the instructions below related to your environment or
1698 \index[general]{GNOME}
1700 System tray, or notification area if you use the GNOME terminology, has been
1701 supported in GNOME since version 2.2. To activate it, right-click on one of
1702 your panels, open the menu {\bf Add to this Panel}, then {\bf Utility} and
1703 finally click on {\bf Notification Area}.
1706 \index[general]{KDE}
1708 System tray has been supported in KDE since version 3.1. To activate it,
1709 right-click on one of your panels, open the menu {\bf Add}, then {\bf Applet}
1710 and finally click on {\bf System Tray}.
1712 \subsection{Other Window Managers}
1713 \index[general]{Managers!Other window}
1714 \index[general]{Other window managers}
1716 Read the documentation to know if the Freedesktop system tray standard is
1717 supported by your window manager, and if applicable, how to activate it.
1719 \section{Modifying the Bacula Configuration Files}
1720 \index[general]{Modifying the Bacula Configuration Files}
1721 \index[general]{Files!Modifying the Bacula Configuration}
1724 \ilink{Configuring Bacula}{ConfigureChapter} in this manual for
1725 instructions on how to set Bacula configuration files.