fatal errors in non-batch mode.
\usepackage{setspace}
\usepackage{hyperref}
+\makeindex
+\newindex{general}{bix}{bid}{General Index}
+
\sloppy
\begin{document}
\parskip 10pt
\parindent 0pt
+
\title{\includegraphics{./bacula-logo.eps} \\ \bigskip
\begin{center}
\large{It comes in the night and sucks
\author{Kern Sibbald}
\date{\vspace{1.0in}\today \\
This manual documents Bacula version \input{version} \\
- \vspace{0.2in}\\
+ ~\vspace{0.2in}\\
Copyright \copyright 1999-2006, Kern Sibbald \\
- \vspace{0.2in}\\
+ ~\vspace{0.2in}\\
Permission is granted to copy, distribute and/or modify this document under the terms of the \\
GNU Free Documentation License, Version 1.2 published by the Free Software Foundation; \\
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. \\
own bootstrap files, or so that you can edit a bootstrap file produced by {\bf
Bacula}. However, normally the bootstrap file will be automatically created
for you during the
-\ilink{restore_command}{_ConsoleChapter} command in the Console program, or
+\ilink{restore\_command}{_ConsoleChapter} command in the Console program, or
by using a
\ilink{ Write Bootstrap}{writebootstrap} record in your Backup
Jobs, and thus you will never need to know the details of this file.
in the time to insert or search for records.
For each of the databases, you may get significant improvements by adding
-additional indexes. The comments in the Bacula make_xxx_tables give some
+additional indexes. The comments in the Bacula make\_xxx\_tables give some
indications as to what indexes may be appropriate. Please see below
for specific instructions on checking indexes.
answer some of your questions about how to improve performance
of the PostgreSQL engine:
\elink{
-http://www.postgresql.org/docs/faqs.FAQ.html#3.3}
-{http://www.postgresql.org/docs/faqs.FAQ.html#3.3}.
+http://www.postgresql.org/docs/faqs.FAQ.html\#3.3}
+{http://www.postgresql.org/docs/faqs.FAQ.html\#3.3}.
\subsection*{Performance Issues Indexes}
\index[general]{Including other Configuration Files }
\index[general]{Files!Including other Configuration }
\index[general]{Using @ to include other files}
-\index[general{@{\bf filename}}
+\index[general]{@{\bf filename}}
\addcontentsline{toc}{subsubsection}{Including other Configuration Files}
If you wish to break your configuration file into smaller pieces, you can do
\item [Enabled = \lt{}yes|no\gt{}]
\index[dir]{Enable}
- \index[dir]Directive!Enable}
+ \index[dir]{Directive!Enable}
This directive allows you to enable or disable automatic execution
via the scheduler of a Job.
%---------The file header---------------------------------------------
-\usepackage[english]{babel} %language selection
-\usepackage[T1]{fontenc}
+%\usepackage[english]{babel} %language selection
+%\usepackage[T1]{fontenc}
\pagenumbering{arabic}
-\usepackage{hyperref}
+%\usepackage{hyperref}
\hypersetup{colorlinks,
citecolor=black,
filecolor=black,
explicitly name each filesystem you want backed up. Explicitly naming the
filesystems you want backed up avoids the possibility of getting into a
infinite loop recursing filesystems. Another possibility is to
- use {\bf onefs=no} and to set {\bs fstype=ext2, ...}.
+ use {\bf onefs=no} and to set {\bf fstype=ext2, ...}.
See the example below for more details.
If you think that Bacula should be backing up a particular directory
On SuSE, the libwrappers libraries needed to link Bacula are
contained in the tcpd-devel package. On RedHat the package is named
- tcp_wrappers.
+ tcp\_wrappers.
\item [ {-}{-}with-working-dir=\lt{}working-directory-path\gt{} ]
\index[general]{{-}{-}with-working-dir }
\begin{enumerate}
\item You must have an installed copy of {\bf gdb} (the GNU debugger), and it
must be on {\bf Bacula's} path. On some systems such as Solaris, {\bf
- gdb} may be replaced by {\dbx}.
+ gdb} may be replaced by {\bf dbx}.
\item The Bacula installed script file {\bf btraceback} must be in the same
directory as the daemon which dies, and it must be marked as executable.
\item The script file {\bf btraceback.gdb} must have the correct path to it
\index[fd]{syslog}
Send the message to the system log (syslog) using the facility specified in
the {\bf address} field. Note, for the moment, the {\bf address} field is
- ignored and the message is always sent to the LOG_DAEMON facility with
- level LOG_ERR. See {\bf man 3 syslog} for more details. Example:
+ ignored and the message is always sent to the LOG\_DAEMON facility with
+ level LOG\_ERR. See {\bf man 3 syslog} for more details. Example:
\begin{verbatim}
syslog = all, !skipped, !saved
\end{verbatim}
If you are getting incorrect dates (e.g. 1970) and you are
running with a non-English language setting, you might try adding
-a LANG="en_US" immediately before the bsmtp call.
+a LANG=''en\_US'' immediately before the bsmtp call.
\subsection*{dbcheck}
\label{dbcheck}
It is because the DirStartUp script is calling a dynamically loaded
module (timemodule.so in the above case) that then tries to use
Python functions exported from the Python interpreter (in this case
-PyInt_FromLong). The way Bacula is currently linked with Python does
+PyInt\_FromLong). The way Bacula is currently linked with Python does
not permit this. The solution to the problem is to put such functions
(in this case the import of time into a separate Python script, which
will do your calculations and return the values you want. Then call
Can I get my packages released to sourceforge for other people to use?} Yes,
contributions from users are accepted and appreciated. Please examine the
directory platforms/contrib-rpm in the source code for further information.
-\end{enumerate}
-\item {\bf Support for RHEL3/4, CentOS 3/4 and x86_64}
+\item {\bf Support for RHEL3/4, CentOS 3/4 and x86\_64}
The examples below show
explicit build support for RHEL4 and CentOS 4. Build support
- for x86_64 has also been added. Test builds have been done on CentOS but
+ for x86\_64 has also been added. Test builds have been done on CentOS but
not RHEL4.
+\end{enumerate}
\footnotesize
\begin{verbatim}
depends on the system. For example,
on SuSE, the TCP wrappers libraries needed to link Bacula are
contained in the tcpd-devel package. On RedHat the package is named
-tcp_wrappers.
+tcp\_wrappers.
Dan Langille has provided the following information on configuring and
testing TCP wrappers with Bacula.
or whatever is appropriate on your system. Note, if you are running a Linux
system, and the above command does not work, it is most likely because you
have not loaded the appropriate {\bf mt} package, which is often called
-{\bf mt_st}, but may differ according to your distribution.
+{\bf mt\_st}, but may differ according to your distribution.
\item The second possibility, especially, if Bacula wrote while the drive was
in fixed block mode, is to turn off block positioning in Bacula. This is done
If you are running a Linux
system, and the above command does not work, it is most likely because you
have not loaded the appropriate {\bf mt} package, which is often called
-{\bf mt_st}, but may differ according to your distribution.
+{\bf mt\_st}, but may differ according to your distribution.
If you would like to know what options you have set before making any of the
changes noted above, you can now view them on Linux systems, thanks to a tip
skipped. File number is always tracked for MTEOM.
Linux does support both SCSI SPACE Filemarks and End-of-data: When MTEOM
- is called in MT_ST_FAST_MTEOM mode, SCSI SPACE End-of-data is used.
+ is called in MT\_ST\_FAST\_MTEOM mode, SCSI SPACE End-of-data is used.
In the other case, SCSI SPACE Filemarks with count =
8388607 is used.
There is no real slow mode like in Solaris - I just expect, that for
older tape drives Filemarks may be slower than End-of-data, but not so
much as in Solaris slow mode. File number is tracked for MTEOM just
- without MT_ST_FAST_MTEOM - when MT_ST_FAST_MTEOM is used, it is not.
+ without MT\_ST\_FAST\_MTEOM - when MT\_ST\_FAST\_MTEOM is used, it is not.
FreeBSD does support both SCSI SPACE Filemarks and End-of-data, but when
MTEOD (MTEOM) is called, SCSI SPACE End-of-data is always used. FreeBSD
overwrite them providing that you do not do a {\bf make uninstall}.
If the new version of Bacula requires an upgrade to the database,
-you can upgrade it with the script {\bf update_bacula_tables}, which
+you can upgrade it with the script {\bf update\_bacula\_tables}, which
will be installed in your scripts directory (default {\bf /etc/bacula}),
or alternatively, you can find it in the
{\bf \lt{}bacula-source\gt{}/src/cats} directory.
\normalsize
In the above Job Report listing, you see that the VSS snapshot was generated for drive C (if
other drives are backed up, they will be listed on the {\bf Drive(s)="C"} You also see the
-reports from each of the writer program. Here they all report VSS_WS_STABLE, which means
+reports from each of the writer program. Here they all report VSS\_WS\_STABLE, which means
that you will get a consistent snapshot of the data handled by that writer.
\subsection*{VSS Problems}
projects / bacula / docs / commitdiff