Now basically use name of the file as part of the chapter label.
This makes it more clear for following or creating new cross-references.
Note that most of the labels were not even used.
This also fixed two previously broken references in license.tex.
And fixed two chapters that had identical label (oldfileset and mysql).
(No changes to content.)
\chapter{ANSI and IBM Tape Labels}
-\label{_ChapterStart62}
+\label{AnsiLabelsChapter}
\index[general]{ANSI and IBM Tape Labels}
\index[general]{Labels!Tape}
%%
\chapter{Autochanger Support}
-\label{_ChapterStart18}
+\label{AutochangersChapter}
\index[general]{Support!Autochanger }
\index[general]{Autochanger Support }
%%
\chapter{The Bootstrap File}
-\label{_ChapterStart43}
+\label{BootstrapChapter}
\index[general]{File!Bootstrap }
\index[general]{Bootstrap File }
%%
\section{Bacula Bugs}
-\label{_ChapterStart4}
+\label{BugsChapter}
\index[general]{Bacula Bugs }
\index[general]{Bugs!Bacula }
%%
\chapter{Catalog Maintenance}
-\label{_ChapterStart12}
+\label{CatMaintenanceChapter}
\index[general]{Maintenance!Catalog }
\index[general]{Catalog Maintenance }
%%
\chapter{Customizing the Configuration Files}
-\label{_ChapterStart16}
+\label{ConfigureChapter}
\index[general]{Files!Customizing the Configuration }
\index[general]{Customizing the Configuration Files }
\begin{itemize}
\item
- \ilink{Console}{_ChapterStart36} -- to define the resources for
+ \ilink{Console}{ConsoleConfChapter} -- to define the resources for
the Console program (user interface to the Director). It defines which
Directors are available so that you may interact with them.
\item
- \ilink{Director}{_ChapterStart40} -- to define the resources
+ \ilink{Director}{DirectorChapter} -- to define the resources
necessary for the Director. You define all the Clients and Storage daemons
that you use in this configuration file.
\item
- \ilink{Client}{_ChapterStart25} -- to define the resources for
+ \ilink{Client}{FiledConfChapter} -- to define the resources for
each client to be backed up. That is, you will have a separate Client
resource file on each machine that runs a File daemon.
\item
- \ilink{Storage}{_ChapterStart31} -- to define the resources to
+ \ilink{Storage}{StoredConfChapter} -- to define the resources to
be used by each Storage daemon. Normally, you will have a single Storage
daemon that controls your tape drive or tape drives. However, if you have
tape drives on several machines, you will have at least one Storage daemon
the current time, the only Resource Record defined is the Director resource,
which gives the Console the name and address of the Director. For more
information on configuration of the Console program, please see the
-\ilink{Console Configuration File}{_ChapterStart36} Chapter of
+\ilink{Console Configuration File}{ConsoleConfChapter} Chapter of
this document.
\section{Running the Console Program}
Python interpreter is initialized, there is no other way to make it
accept any changes to the startup script {\bf DirStartUp.py}. For more
details on Python scripting, please see the \ilink{Python
- Scripting}{_ChapterStart60} chapter of this manual.
+ Scripting}{PythonChapter} chapter of this manual.
\label{ManualPruning}
\item [prune]
%%
\chapter{Console Configuration}
-\label{_ChapterStart36}
+\label{ConsoleConfChapter}
\index[general]{Configuration!Console}
\index[general]{Console Configuration}
For a general discussion of the syntax of configuration files and their
resources including the data types recognized by {\bf Bacula}, please see
-the \ilink{Configuration}{_ChapterStart16} chapter of this manual.
+the \ilink{Configuration}{ConfigureChapter} chapter of this manual.
The following Console Resource definition must be defined:
likely already be set to the value you specified on the {\bf
\verb:--:with-base-port} option of the {\bf ./configure} command. This port must be
identical to the {\bf DIRport} specified in the {\bf Director} resource of
- the \ilink{Director's configuration}{_ChapterStart40} file. The
+ the \ilink{Director's configuration}{DirectorChapter} file. The
default is 9101 so this directive is not normally specified.
\item [Address = \lt{}address\gt{}]
Where the password is the password needed for the Director to accept the
Console connection. This password must be identical to the {\bf Password}
specified in the {\bf Director} resource of the
- \ilink{Director's configuration}{_ChapterStart40} file. This
+ \ilink{Director's configuration}{DirectorChapter} file. This
directive is required.
\end{description}
%%
\chapter{Critical Items to Implement Before Production}
-\label{_ChapterStart32}
+\label{CriticalChapter}
\index[general]{Production!Critical Items to Implement Before }
\index[general]{Critical Items to Implement Before Production }
\item Test your tape drive for compatibility with Bacula by using the test
command in the \ilink{btape}{btape} program.
\item Better than doing the above is to walk through the nine steps in the
- \ilink{Tape Testing}{_ChapterStart27} chapter of the manual. It
+ \ilink{Tape Testing}{TapeTestingChapter} chapter of the manual. It
may take you a bit of time, but it will eliminate surprises.
\item Test the end of tape handling of your tape drive by using the
fill command in the \ilink{btape}{btape} program.
Write Bootstrap directive is described in the
\ilink{Director Configuration}{writebootstrap} chapter of the
manual, and more details are available in the
- \ilink{Bootstrap File}{_ChapterStart43} chapter. Also, the default
+ \ilink{Bootstrap File}{BootstrapChapter} chapter. Also, the default
bacula-dir.conf comes with a Write Bootstrap directive defined. This allows
you to recover the state of your system as of the last backup.
\item Backup your catalog. An example of this is found in the default
reconstruct if your server dies.
\item Make a Bacula Rescue CDROM! See the
\ilink{Disaster Recovery Using a Bacula Rescue
- CDROM}{_ChapterRescue} chapter. It is trivial to make such a CDROM,
+ CDROM}{RescueChapter} chapter. It is trivial to make such a CDROM,
and it can make system recovery in the event of a lost hard disk infinitely
easier.
\item Bacula assumes all filenames are in UTF-8 format. This is important
you avoid problems.
\begin{itemize}
-\item Read the \ilink{Quick Start Guide to Bacula}{_ChapterStart37}
+\item Read the \ilink{Quick Start Guide to Bacula}{QuickStartChapter}
\item After installing and experimenting with Bacula, read and work carefully
through the examples in the
- \ilink{Tutorial}{_ChapterStart1} chapter of this manual.
+ \ilink{Tutorial}{TutorialChapter} chapter of this manual.
\item Learn what each of the \ilink{Bacula Utility Programs}{_UtilityChapter}
does.
\item Set up reasonable retention periods so that your catalog does not grow
to be too big. See the following three chapters:\\
- \ilink{Recycling your Volumes}{_ChapterStart22},\\
- \ilink{Basic Volume Management}{_ChapterStart39},\\
- \ilink{Using Pools to Manage Volumes}{_ChapterStart11}.
+ \ilink{Recycling your Volumes}{RecyclingChapter},\\
+ \ilink{Basic Volume Management}{DiskChapter},\\
+ \ilink{Using Pools to Manage Volumes}{PoolsChapter}.
\item Perform a bare metal recovery using the Bacula Rescue CDROM. See the
- \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{_ChapterRescue}
+ \ilink{Disaster Recovery Using a Bacula Rescue CDROM}{RescueChapter}
chapter.
\end{itemize}
%%
\chapter{Configuring the Director}
-\label{_ChapterStart40}
+\label{DirectorChapter}
\index[general]{Director!Configuring the}
\index[general]{Configuring the Director}
For a general discussion of configuration files and resources including the
data types recognized by {\bf Bacula}. Please see the
-\ilink{Configuration}{_ChapterStart16} chapter of this manual.
+\ilink{Configuration}{ConfigureChapter} chapter of this manual.
\section{Director Resource Types}
\index[general]{Types!Director Resource}
the files you select to be restored.
For additional details of the {\bf bootstrap} file, please see
- \ilink{Restoring Files with the Bootstrap File}{_ChapterStart43} chapter
+ \ilink{Restoring Files with the Bootstrap File}{BootstrapChapter} chapter
of this manual.
\label{writebootstrap}
\end{verbatim}
For more details on using this file, please see the chapter entitled
- \ilink{The Bootstrap File}{_ChapterStart43} of this manual.
+ \ilink{The Bootstrap File}{BootstrapChapter} of this manual.
\item [Client = \lt{}client-resource-name\gt{}]
\index[dir]{Client}
probably should use two different Media Types for your two disk Devices
(even though you might think of them as both being File types). You can
find more on this subject in the \ilink{Basic Volume
- Management}{_ChapterStart39} chapter of this manual.
+ Management}{DiskChapter} chapter of this manual.
The {\bf MediaType} specified here, {\bf must} correspond to the {\bf
Media Type} specified in the {\bf Device} resource of the {\bf Storage
yes} in the \ilink{Device Resource}{Autochanger} in the Storage daemon's
configuration file as well as other important Storage daemon
configuration information. Please consult the \ilink{Using
- Autochangers}{_ChapterStart18} manual of this chapter for the details of
+ Autochangers}{AutochangersChapter} manual of this chapter for the details of
using autochangers.
\item [Maximum Concurrent Jobs = \lt{}number\gt{}]
Default} Pool. If your backup strategy calls for you to mount a different tape
each day, you will probably want to define a separate Pool for each day. For
more information on this subject, please see the
-\ilink{Backup Strategies}{_ChapterStart3} chapter of this
+\ilink{Backup Strategies}{StrategiesChapter} chapter of this
manual.
specify variable expansion characters, you should always enclose the
format with double quote characters ({\bf "}). For more details on
variable expansion, please see the \ilink{Variable
- Expansion}{_ChapterStart50} Chapter of this manual.
+ Expansion}{VarsChapter} Chapter of this manual.
If no variable expansion characters are found in the string, the Volume
name will be formed from the {\bf format} string appended with the
When this keyword is present, any resource or command name (which ever is
appropriate) will be accepted. For an example configuration file, please see
the
-\ilink{Console Configuration}{_ChapterStart36} chapter of this
+\ilink{Console Configuration}{ConsoleConfChapter} chapter of this
manual.
\section{The Counter Resource}
%%
\chapter{Basic Volume Management}
-\label{_ChapterStart39}
+\label{DiskChapter}
\index[general]{Basic Volume Management}
\index[general]{Management!Basic Volume}
\index[general]{Disk Volumes}
In version 1.37 and later, it is probably much better to use Python scripting
and the NewVolume event since generating Volume labels in a Python script is
much easier than trying to figure out Counter variables. See the
-\ilink{Python Scripting}{_ChapterStart60} chapter of this manual for more
+\ilink{Python Scripting}{PythonChapter} chapter of this manual for more
details.
Please note that automatic Volume labeling can also be used with tapes, but
work with autochangers since Bacula will not access unknown slots. There
are several methods of labeling all volumes in an autochanger magazine.
For more information on this, please see the \ilink{
-Autochanger}{_ChapterStart18} chapter of this manual.
+Autochanger}{AutochangersChapter} chapter of this manual.
Automatic Volume labeling is enabled by making a change to both the Pool
resource (Director) and to the Device resource (Storage daemon) shown above.
Bacula will create Volume names Vol0001, Vol0002, and so on when new Volumes
are needed. Much more complex and elaborate labels can be created using
variable expansion defined in the
-\ilink{Variable Expansion}{_ChapterStart50} chapter of this manual.
+\ilink{Variable Expansion}{VarsChapter} chapter of this manual.
The second change that is necessary to make automatic labeling work is to give
the Storage daemon permission to automatically label Volumes. Do so by adding
The first three records (File Retention, Job Retention, and AutoPrune)
determine the amount of time that Job and File records will remain in your
Catalog, and they are discussed in detail in the
-\ilink{Automatic Volume Recycling}{_ChapterStart22} chapter of
+\ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of
this manual.
Volume Retention, AutoPrune, and Recycle determine how long Bacula will keep
your Volumes before reusing them, and they are also discussed in detail in the
-\ilink{Automatic Volume Recycling}{_ChapterStart22} chapter of
+\ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of
this manual.
The Maximum Volumes record can also be used in conjunction with the Volume
% TODO: and use detailed indexing to help reader
\chapter{Bacula Frequently Asked Questions}
-\label{_ChapterStart48}
+\label{FaqChapter}
\index[general]{Questions!Bacula Frequently Asked }
\index[general]{Bacula Frequently Asked Questions }
\elink{http://paramount.ind.wpi.edu/wiki/doku.php?id=faq}{http://paramount.ind.wpi.edu/wiki/doku.php?id=faq}.
Please also see
-\ilink{the bugs section}{_ChapterStart4} of this document for a list
+\ilink{the bugs section}{BugsChapter} of this document for a list
of known bugs and solutions.
\begin{description}
back to the original conf files generated by the Bacula installation
process. Make only the absolutely necessary modifications to these
files -- e.g. add the correct email address. Then follow the
- instructions in the \ilink{ Running Bacula}{_ChapterStart1} chapter of
+ instructions in the \ilink{ Running Bacula}{TutorialChapter} chapter of
this manual. You will run a backup to disk and a restore. Only when
that works, should you begin customization of the conf files.
For the first problem, see the next FAQ question. For the second
problem, please review the \ilink{ Windows Installation
- instructions}{_ChapterStart7} in this manual.
+ instructions}{Win32Chapter} in this manual.
\label{windowsdie}
\section{My Windows Client Immediately Dies When I Start It}
resource. For an example of how to backup to files, please see the
\ilink{Pruning Example}{PruningExample} in the Recycling chapter of this
manual. Also, there is a whole chapter devoted to \ilink{Basic Volume
- Management}{_ChapterStart39}. This chapter was originally written to
+ Management}{DiskChapter}. This chapter was originally written to
explain how to write to disk, but was expanded to include volume
management. It is, however, still quite a good chapter to read.
\index[general]{Checking Restores}
It is really quite simple, but took me a while to figure
out how to "prove" it. First make a Bacula Rescue disk, see the
- \ilink{Disaster Recovery Using Bacula}{_ChapterRescue} chapter
+ \ilink{Disaster Recovery Using Bacula}{RescueChapter} chapter
of this manual.
Second, you run a full backup of all your files on all partitions.
Third, you run an Verify InitCatalog Job on the same FileSet, which
%%
\chapter{Client/File daemon Configuration}
-\label{_ChapterStart25}
+\label{FiledConfChapter}
\index[general]{Configuration!Client/File daemon }
\index[general]{Client/File daemon Configuration }
For a general discussion of configuration file and resources including the
data types recognized by {\bf Bacula}, please see the
-\ilink{Configuration}{_ChapterStart16} chapter of this manual. The
+\ilink{Configuration}{ConfigureChapter} chapter of this manual. The
following Client Resource definitions must be defined:
\begin{itemize}
Ludovic Strappazon has pointed out that this feature can be used to backup a
full Microsoft Windows disk. Simply boot into the system using a Linux Rescue
disk, then load a statically linked Bacula as described in the
- \ilink{ Disaster Recovery Using Bacula}{_ChapterRescue} chapter of
+ \ilink{ Disaster Recovery Using Bacula}{RescueChapter} chapter of
this manual. Then save the whole disk partition. In the case of a disaster,
you can then restore the desired partition by again booting with the rescue
disk and doing a restore of the partition.
%%
\chapter{Dealing with Firewalls}
-\label{_ChapterStart26}
+\label{FirewallsChapter}
\index[general]{Dealing with Firewalls }
\index[general]{Firewalls!Dealing with }
%%
\chapter{What is Bacula?}
-\label{_ChapterStart41}
+\label{GeneralChapter}
\index[general]{Bacula!What is }
\index[general]{What is Bacula? }
The RPMs for MySQL and PostgreSQL ship as part of Red Hat Linux and
several other releases. Alternatively, building the rpms from the
source is quite easy, see the \ilink{ Installing and Configuring
- MySQL}{_ChapterStart} chapter of this document for the details. For
+ MySQL}{MySqlChapter} chapter of this document for the details. For
more information on MySQL, please see:
\elink{www.mysql.com}{http://www.mysql.com}. Or see the \ilink{
- Installing and Configuring PostgreSQL}{_ChapterStart10} chapter of this
+ Installing and Configuring PostgreSQL}{PostgreSqlChapter} chapter of this
document for the details. For more information on PostgreSQL, please
see: \elink{www.postgresql.org}{http://www.postgresql.org}.
Configuring and building SQLite is even easier. For the details of
configuring SQLite, please see the \ilink{ Installing and Configuring
- SQLite}{_ChapterStart33} chapter of this document.
+ SQLite}{SqlLiteChapter} chapter of this document.
\item
\label{MonDef}
{\bf Bacula Monitor} services is the program that allows the
To get Bacula up and running quickly, we recommend that you first scan the
Terminology section below, then quickly review the next chapter entitled
-\ilink{The Current State of Bacula}{_ChapterStart2}, then the
-\ilink{Getting Started with Bacula}{_ChapterStart37}, which will
+\ilink{The Current State of Bacula}{StateChapter}, then the
+\ilink{Getting Started with Bacula}{QuickStartChapter}, which will
give you a quick overview of getting Bacula running. After which, you should
proceed to the chapter on
-\ilink{Installing Bacula}{_ChapterStart17}, then
-\ilink{How to Configure Bacula}{_ChapterStart16}, and finally the
+\ilink{Installing Bacula}{InstallChapter}, then
+\ilink{How to Configure Bacula}{ConfigureChapter}, and finally the
chapter on
-\ilink{ Running Bacula}{_ChapterStart1}.
+\ilink{ Running Bacula}{TutorialChapter}.
\section{Terminology}
\index[general]{Terminology }
{\bf Bacula} is a backup, restore and verification program and is not a
complete disaster recovery system in itself, but it can be a key part of one
if you plan carefully and follow the instructions included in the
-\ilink{ Disaster Recovery}{_ChapterRescue} Chapter of this manual.
+\ilink{ Disaster Recovery}{RescueChapter} Chapter of this manual.
With proper planning, as mentioned in the Disaster Recovery chapter {\bf
Bacula} can be a central component of your disaster recovery system. For
%%
\section*{GNU General Public License}
-\label{_ChapterStart20}
+\label{GplChapter}
\index[general]{GNU General Public License }
\index[general]{License!GNU General Public }
%%
\chapter{Installing Bacula}
-\label{_ChapterStart17}
+\label{InstallChapter}
\index[general]{Bacula!Installing}
\index[general]{Installing Bacula}
\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}{_ChapterStart} or
+ \ilink{Installing and Configuring MySQL Phase I}{MySqlChapter} or
\ilink{Installing and Configuring PostgreSQL Phase
- I}{_ChapterStart10}. If you are installing from rpms, and are
+ I}{PostgreSqlChapter}. If you are installing from rpms, and are
using MySQL, please be sure to install {\bf mysql-devel}, so that the MySQL
header files are available while compiling Bacula. In addition, the MySQL
client library {\bf mysqlclient} requires the gzip compression library {\bf
\item As an alternative to MySQL and PostgreSQL, configure and install SQLite,
which is part of the {\bf depkgs} and also available with most modern
Operating Systems.
- \ilink{Installing and Configuring SQLite}{_ChapterStart33}. SQLite is
+ \ilink{Installing and Configuring SQLite}{SqlLiteChapter}. SQLite is
probably not suited to a fair size production environment because it
tends to be slow compared to MySQL and it has few or poor tools for
repairing database damage.
\item Customize the configuration files for each of the three daemons
(Directory, File, Storage) and for the Console program. For the details
of how to do this, please see \ilink{Setting Up Bacula Configuration
- Files}{_ChapterStart16} in the Configuration chapter of this manual. We
+ Files}{ConfigureChapter} in the Configuration chapter of this manual. We
recommend that you start by modifying the default configuration files
supplied, making the minimum changes necessary. Complete customization
can be done after you have Bacula up and running. Please take care when
\item Interface with Bacula using the Console program
\item For the previous two items, please follow the instructions in the
- \ilink{Running Bacula}{_ChapterStart1} chapter of this manual,
+ \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
work.
If you wish to use MySQL as the Bacula catalog, please see the
-\ilink{Installing and Configuring MySQL}{_ChapterStart} chapter of
+\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
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}{_ChapterStart10}
+\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
requires a certain knowledge to install and maintain.
If you wish to use SQLite as the Bacula catalog, please see
-\ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
+\ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of
this manual.
\section{Quick Start}
This enables use of the SQLite version 2.8.x database. The {\bf sqlite-path} is not
normally specified as Bacula looks for the necessary components in a
standard location ({\bf depkgs/sqlite}). See
- \ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
+ \ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of
this manual for more details.
See the note below under the {-}{-}with-postgresql item.
This enables use of the SQLite version 3.x database. The {\bf
sqlite3-path} is not normally specified as Bacula looks for the
necessary components in a standard location ({\bf depkgs/sqlite3}). See
- \ilink{Installing and Configuring SQLite}{_ChapterStart33} chapter of
+ \ilink{Installing and Configuring SQLite}{SqlLiteChapter} chapter of
this manual for more details.
\item [ {-}{-}with-mysql=\lt{}mysql-path\gt{}]
in a standard system location, you can simply use {\bf {-}{-}with-mysql}
with no path specification. If you do use this option, please proceed
to installing MySQL in the \ilink{Installing and Configuring
- MySQL}{_ChapterStart} chapter before proceeding with the configuration.
+ MySQL}{MySqlChapter} chapter before proceeding with the configuration.
See the note below under the {-}{-}with-postgresql item.
standard library locations for Python 2.2, 2.3, or 2.4. If it cannot
find the library, you will need to supply a path to your Python
library directory. Please see the
- \ilink{Python chapter}{_ChapterStart60} for the details of using
+ \ilink{Python chapter}{PythonChapter} for the details of using
Python scripting.
\item [ {-}{-}with-libintl-prefix=\lt{}DIR\gt{}]
\index[general]{Win32}
To install the binary Win32 version of the File daemon please see the
-\ilink{Win32 Installation Chapter}{_ChapterStart7} in this document.
+\ilink{Win32 Installation Chapter}{Win32Chapter} in this document.
\section{One File Configure Script}
\index[general]{Script!One File Configure}
\index[general]{Files!Modifying the Bacula Configuration}
See the chapter
-\ilink{Configuring Bacula}{_ChapterStart16} in this manual for
+\ilink{Configuring Bacula}{ConfigureChapter} in this manual for
instructions on how to set Bacula configuration files.
\section*{The internal database is not supported, please do not
use it.}
-\label{_ChapterStart42}
+\label{InternalDbChapter}
\index[general]{Use it!The internal database is not supported please
do not }
\index[general]{The internal database is not supported, please do not
%%
\chapter{What To Do When Bacula Crashes (Kaboom)}
-\label{_ChapterStart47}
+\label{KaboomChapter}
\index[general]{Kaboom!What To Do When Bacula Crashes }
\index[general]{What To Do When Bacula Crashes (Kaboom) }
%%
\section*{GNU Lesser General Public License}
-\label{_ChapterStart49}
+\label{LesserChapter}
\index[general]{GNU Lesser General Public License }
\index[general]{License!GNU Lesser General Public }
%%
\chapter{Bacula Copyright, Trademark, and Licenses}
-\label{_ChapterStart29}
+\label{LicenseChapter}
\index[general]{Licenses!Bacula Copyright Trademark}
\index[general]{Bacula Copyright, Trademark, and Licenses}
\index[general]{GPL }
The vast bulk of the source code is released under a modified version of the
-\ilink{GNU General Public License version 2.}{_ChapterStart20} The
+\ilink{GNU General Public License version 2.}{GplChapter} The
modifications (actually additions) are described in the source file LICENSE,
and their purpose is not to alter the essential qualities of the GPL but to
permit more freedom in linking certain third party software supposedly non-GPL
\index[general]{LGPL }
Some of the Bacula library source code is released under the
-\ilink{GNU Lesser General Public License.}{_ChapterStart49} This
+\ilink{GNU Lesser General Public License.}{LesserChapter} This
permits third parties to use these parts of our code in their proprietary
programs to interface to Bacula.
For a general discussion of configuration file and resources including the
data types recognized by {\bf Bacula}, please see the
-\ilink{Configuration}{_ChapterStart16} chapter of this manual.
+\ilink{Configuration}{ConfigureChapter} chapter of this manual.
The following Monitor Resource definition must be defined:
Where the password is the password needed for Directors to accept the Console
connection. This password must be identical to the {\bf Password} specified
in the {\bf Console} resource of the
-\ilink{Director's configuration}{_ChapterStart40} file. This
+\ilink{Director's configuration}{DirectorChapter} file. This
record is required if you wish to monitor Directors.
\item [Refresh Interval = \lt{}time\gt{}]
As you are not permitted to define a Password in this resource, to avoid
obtaining full Director privileges, you must create a Console resource in the
-\ilink{Director's configuration}{_ChapterStart40} file, using the
+\ilink{Director's configuration}{DirectorChapter} file, using the
Console Name and Password defined in the Monitor resource. To avoid security
problems, you should configure this Console resource to allow access to no
other daemons, and permit the use of only two commands: {\bf status} and {\bf
\verb:--:with-base-port} option of the {\bf ./configure} command. This port must be
identical to the {\bf DIRport} specified in the {\bf Director} resource of
the
-\ilink{Director's configuration}{_ChapterStart40} file. The
+\ilink{Director's configuration}{DirectorChapter} file. The
default is 9101 so this record is not normally specified.
\item [Address = \lt{}address\gt{}]
by this Monitor.
You must create a Director resource in the
-\ilink{Client's configuration}{_ChapterStart25} file, using the
+\ilink{Client's configuration}{FiledConfChapter} file, using the
Director Name defined in the Monitor resource. To avoid security problems, you
should set the {\bf Monitor} directive to {\bf Yes} in this Director resource.
by this Monitor.
You must create a Director resource in the
-\ilink{Storage's configuration}{_ChapterStart31} file, using the
+\ilink{Storage's configuration}{StoredConfChapter} file, using the
Director Name defined in the Monitor resource. To avoid security problems, you
should set the {\bf Monitor} directive to {\bf Yes} in this Director resource.
%%
\chapter{Installing and Configuring MySQL}
-\label{_ChapterStart}
+\label{MySqlChapter}
\index[general]{MySQL!Installing and Configuring }
\index[general]{Installing and Configuring MySQL }
%%
\chapter{The Old FileSet Resource}
-\label{_ChapterStart}
+\label{OldFileSetChapter}
\label{FileSetResource}
\index[general]{Resource!Old FileSet }
\index[general]{Old FileSet Resource }
Ludovic Strappazon has pointed out that this feature can be used to backup a
full Microsoft Windows disk. Simply boot into the system using a Linux Rescue
disk, then load a statically linked Bacula as described in the
-\ilink{ Disaster Recovery Using Bacula}{rescue.tex#_ChapterStart} chapter of
+\ilink{ Disaster Recovery Using Bacula}{RescueChapter} chapter of
this manual. Then simply save the whole disk partition. In the case of a
disaster, you can then restore the desired partition.
\item If you explicitly specify a FIFO device name (created with mkfifo), and
%%
\chapter{Automated Disk Backup}
-\label{_ChapterStart11}
+\label{PoolsChapter}
\index[general]{Volumes!Using Pools to Manage}
\index[general]{Disk!Automated Backup}
\index[general]{Using Pools to Manage Volumes}
%%
\chapter{Installing and Configuring PostgreSQL}
-\label{_ChapterStart10}
+\label{PostgreSqlChapter}
\index[general]{PostgreSQL!Installing and Configuring }
\index[general]{Installing and Configuring PostgreSQL }
bootstrap} file is optional but recommended because it gives you the most
control over which files will be restored. For more details on the {\bf
bootstrap} file, please see
-\ilink{Restoring Files with the Bootstrap File}{_ChapterStart43}
+\ilink{Restoring Files with the Bootstrap File}{BootstrapChapter}
chapter of this document. Note, you may also use a bootstrap file produced by
the {\bf restore} command. For example:
storage device (tape drive) will permit {\bf Bacula} to function properly. You
only need to mount a blank tape, enter the command, and the output should be
reasonably self explanatory. Please see the
-\ilink{Tape Testing}{_ChapterStart27} Chapter of this manual for
+\ilink{Tape Testing}{TapeTestingChapter} Chapter of this manual for
the details.
\subsection{btape Commands}
%%
\chapter{Bacula Projects}
-\label{_ChapterStart28}
+\label{ProjectsChapter}
\index[general]{Projects!Bacula }
\index[general]{Bacula Projects }
%%
\chapter{Python Scripting}
-\label{_ChapterStart60}
+\label{PythonChapter}
\index[general]{Python Scripting}
\index[general]{Scripting!Python}
%%
\chapter{Getting Started with Bacula}
-\label{_ChapterStart37}
-% TODO: cleanup these labels to use descriptions not numbers
+\label{QuickStartChapter}
\index[general]{Getting Started with Bacula }
If you are like me, you want to get Bacula running immediately to get a feel
We assume that you have managed to build and install Bacula, if not, you might
want to first look at the
\ilink{System Requirements}{SysReqs} then at the
-\ilink{Compiling and Installing Bacula}{_ChapterStart17} chapter of
+\ilink{Compiling and Installing Bacula}{InstallChapter} chapter of
this manual.
\label{JobsandSchedules}
often. Most of the work will simply be in changing the tape when it is full.
\subsection{
-\ilink{Configuring the Console Program}{_ChapterStart36}}
+\ilink{Configuring the Console Program}{ConsoleConfChapter}}
\index[general]{Configuring the Console Program }
\index[general]{Program!Configuring the Console }
default settings.
\subsection{
-\ilink{Configuring the File daemon}{_ChapterStart25}}
+\ilink{Configuring the File daemon}{FiledConfChapter}}
\index[general]{Daemon!Configuring the File }
\index[general]{Configuring the File daemon }
% TODO: and creating the unique configuration file.
\subsection{
-\ilink{Configuring the Director}{_ChapterStart40}}
+\ilink{Configuring the Director}{DirectorChapter}}
\index[general]{Director!Configuring the }
\index[general]{Configuring the Director }
% TODO: why not check for that and not allow sharing working directory?
\subsection{
-\ilink{Configuring the Storage daemon}{_ChapterStart31}}
+\ilink{Configuring the Storage daemon}{StoredConfChapter}}
\index[general]{Daemon!Configuring the Storage }
\index[general]{Configuring the Storage daemon }
Before spending a lot of time on Bacula only to find that it doesn't work
with your tape drive, please read the \ilink{btape -- Testing Your Tape
-Drive}{_ChapterStart27} chapter of this manual. If you have a modern
+Drive}{TapeTestingChapter} chapter of this manual. If you have a modern
standard SCSI tape drive on a Linux or Solaris, most likely it will work,
but better test than be sorry. For FreeBSD (and probably other xBSD
flavors), reading the above mentioned tape testing chapter is a must.
To get a good idea how to use Bacula in a short time, we {\bf strongly}
recommend that you follow the example in the
-\ilink{Running Bacula Chapter}{_ChapterStart1} of this manual where
+\ilink{Running Bacula Chapter}{TutorialChapter} of this manual where
you will get detailed instructions on how to run Bacula.
\section{Log Rotation}
If you intend to use Bacula as a disaster recovery tool rather than simply a
program to restore lost or damaged files, you will want to read the
-\ilink{Disaster Recovery Using Bacula Chapter}{_ChapterRescue} of
+\ilink{Disaster Recovery Using Bacula Chapter}{RescueChapter} of
this manual.
In any case, you are strongly urged to carefully test restoring some files
%%
\chapter{Automatic Volume Recycling}
-\label{_ChapterStart22}
+\label{RecyclingChapter}
\index[general]{Recycling!Automatic Volume }
\index[general]{Automatic Volume Recycling }
\item Maximum Volume Bytes = mmm
\end{itemize}
Please see below and
-the \ilink{Basic Volume Management}{_ChapterStart39} chapter
+the \ilink{Basic Volume Management}{DiskChapter} chapter
of this manual for more complete examples.
Automatic recycling of Volumes is performed by Bacula only when it wants a
Although automatic recycling of Volumes is implemented in version 1.20 and
later (see the
-\ilink{Automatic Recycling of Volumes}{_ChapterStart22} chapter of
+\ilink{Automatic Recycling of Volumes}{RecyclingChapter} chapter of
this manual), you may want to manually force reuse (recycling) of a Volume.
Assuming that you want to keep the Volume name, but you simply want to write
In addition to what is presented here, there is more specific information
on restoring a \ilink{Client}{restore_client} and your
\ilink{Server}{restore_server} in the \ilink{Disaster Recovery Using
-Bacula}{_ChapterRescue} chapter of this manual.
+Bacula}{RescueChapter} chapter of this manual.
\begin{description}
\item[Problem]
You will then need to follow the instructions for your
database type to recreate the database from the ASCII backup file.
- See the \ilink {Catalog Maintenance}{_ChapterStart12} chapter of
+ See the \ilink {Catalog Maintenance}{CatMaintenanceChapter} chapter of
this manual for examples of the command needed to restore a
database from an ASCII dump (they are shown in the Compacting Your
XXX Database sections).
Once you have restored the ASCII dump of the database,
you will then to follow the instructions for your
database type to recreate the database from the ASCII backup file.
- See the \ilink {Catalog Maintenance}{_ChapterStart12} chapter of
+ See the \ilink {Catalog Maintenance}{CatMaintenanceChapter} chapter of
this manual for examples of the command needed to restore a
database from an ASCII dump (they are shown in the Compacting Your
XXX Database sections).
%%
\chapter{Bacula RPM Packaging FAQ}
-\label{_ChapterStart34}
+\label{RpmFaqChapter}
\index[general]{FAQ!Bacula\textsuperscript{\textregistered} - RPM Packaging }
\index[general]{Bacula\textsuperscript{\textregistered} - RPM Packaging FAQ }
%%
\chapter{Bacula Security Issues}
-\label{_ChapterStart14}
+\label{SecurityChapter}
\index[general]{Bacula Security Issues}
\index[general]{Security}
\index[general]{Issues!Bacula Security}
%%
\chapter{Installing and Configuring SQLite}
-\label{_ChapterStart33}
+\label{SqlLiteChapter}
\index[general]{Installing and Configuring SQLite }
\index[general]{SQLite!Installing and Configuring }
%%
\chapter{The Current State of Bacula}
-\label{_ChapterStart2}
+\label{StateChapter}
\index[general]{Current State of Bacula }
In other words, what is and what is not currently implemented and functional.
current backup or a backup prior to a specified time and date.
\item Restore of a complete system starting from bare metal. This is mostly
automated for Linux systems and partially automated for Solaris. See
- \ilink{Disaster Recovery Using Bacula}{_ChapterRescue}. This is also
+ \ilink{Disaster Recovery Using Bacula}{RescueChapter}. This is also
reported to work on Win2K/XP systems.
\item Listing and Restoration of files using stand-alone {\bf bls} and {\bf
bextract} tool programs. Among other things, this permits extraction of files
\begin{itemize}
\item Multi-threaded implementation.
\item A comprehensive and extensible
- \ilink{configuration file}{_ChapterStart40} for each daemon.
+ \ilink{configuration file}{DirectorChapter} for each daemon.
\end{itemize}
\end{itemize}
%%
\chapter{Storage Daemon Configuration}
-\label{_ChapterStart31}
+\label{StoredConfChapter}
\index[general]{Storage Daemon Configuration}
\index[general]{Configuration!Storage Daemon}
For a general discussion of configuration file and resources including the
data types recognized by {\bf Bacula}, please see the
-\ilink{Configuration}{_ChapterStart16} chapter of this manual. The
+\ilink{Configuration}{ConfigureChapter} chapter of this manual. The
following Storage Resource definitions must be defined:
\begin{itemize}
/dev/sg0} for the Changer Device name. Depending on your exact
configuration, and the number of autochangers or the type of
autochanger, what you specify here can vary. This directive is
- optional. See the \ilink{ Using Autochangers}{_ChapterStart18} chapter
+ optional. See the \ilink{ Using Autochangers}{AutochangersChapter} chapter
of this manual for more details of using this and the following
autochanger directives.
release). An example of this command is in the default bacula-sd.conf file.
For more details on the substitution characters that may be specified to
configure your autochanger please see the
- \ilink{Autochangers}{_ChapterStart18} chapter of this manual.
+ \ilink{Autochangers}{AutochangersChapter} chapter of this manual.
For FreeBSD users, you might want to see one of the several {\bf chio}
scripts in {\bf examples/autochangers}.
wrong with your tape drive (at least for most modern tape drives). The same
substitution characters that may be specified in the Changer Command may also
be used in this string. For more information, please see the
- \ilink{Autochangers}{_ChapterStart18} chapter of this manual.
+ \ilink{Autochangers}{AutochangersChapter} chapter of this manual.
Note, it is not necessary to have an autochanger to use this command. The
%%
\chapter{Backup Strategies}
-\label{_ChapterStart3}
+\label{StrategiesChapter}
\index[general]{Strategies!Backup }
\index[general]{Backup Strategies }
%%
\chapter{Using Stunnel to Encrypt Communications}
-\label{_ChapterStart6}
+\label{StunnelChapter}
\index[general]{Using Stunnel to Encrypt Communications to Clients }
Prior to version 1.37, Bacula did not have built-in communications encryption.
%%
\chapter{Testing Your Tape Drive With Bacula}
-\label{_ChapterStart27}
+\label{TapeTestingChapter}
\index[general]{Testing Your Tape Drive With Bacula}
This chapter is concerned with testing and configuring your tape drive to make
It isn't necessary to run the autochanger part of the test at this time, but
do not go past this point until the basic test succeeds. If you do have
an autochanger, please be sure to read the
-\ilink{Autochanger chapter}{_ChapterStart18} of this manual.
+\ilink{Autochanger chapter}{AutochangersChapter} of this manual.
\item Run the btape {\bf fill} command, preferably with two volumes. This
can take a long time. If you have an autochanger and it is configured, Bacula
%%
\chapter{Thanks}
-\label{_ChapterStart44}
+\label{ThanksChapter}
\index[general]{Thanks }
I thank everyone who has helped this project. Unfortunately, I cannot
thank everyone (bad memory). However, the AUTHORS file in the main source
%%
\chapter{Tips and Suggestions}
-\label{_ChapterStart8}
+\label{TipsChapter}
\index[general]{Tips and Suggestions }
\index[general]{Suggestions!Tips and }
\label{examples}
By using a
\ilink{ WriteBootstrap}{writebootstrap} record in each of your
Director's Job resources, you can constantly maintain a
-\ilink{bootstrap}{_ChapterStart43} file that will enable you to
+\ilink{bootstrap}{BootstrapChapter} file that will enable you to
recover the state of your system as of the last backup without having the
Bacula catalog. This permits you to more easily recover from a disaster that
destroys your Bacula catalog.
%%
\chapter{A Brief Tutorial}
-\label{_ChapterStart1}
+\label{TutorialChapter}
\index[general]{Brief Tutorial }
\index[general]{Tutorial!Brief }
Note, on Windows, currently only the File daemon is ported, and it must be
started differently. Please see the
-\ilink{Windows Version of Bacula}{_ChapterStart7} Chapter of this
+\ilink{Windows Version of Bacula}{Win32Chapter} Chapter of this
manual.
The rpm packages configure the daemons to run as user=root and group=bacula.
and then restart as noted above.
The
-\ilink{installation chapter}{_ChapterStart17} of this manual
+\ilink{installation chapter}{InstallChapter} of this manual
explains how you can install scripts that will automatically restart the
daemons when the system starts.
Periods and you will have all your tapes marked to be Recycled, and {\bf
Bacula} will automatically recycle the tapes in your pool requesting and
overwriting old Volumes. For more information on recycling, please see the
-\ilink{Recycling chapter}{_ChapterStart22} of this manual. If you
+\ilink{Recycling chapter}{RecyclingChapter} of this manual. If you
find that your Volumes were not properly recycled (usually because of a
configuration error), please see the
\ilink{Manually Recycling Volumes}{manualrecycling} section of
{\bf Bacula} requests them. This is most often done if you are cycling through
a set of tapes, for example using an autochanger. For more details on
recycling, please see the
-\ilink{Automatic Volume Recycling}{_ChapterStart22} chapter of
+\ilink{Automatic Volume Recycling}{RecyclingChapter} chapter of
this manual.
If you run a Bacula job, and you have no labeled tapes in the Pool, Bacula
%%
\chapter{Variable Expansion}
-\label{_ChapterStart50}
+\label{VarsChapter}
\index[general]{Variable Expansion }
\index[general]{Expansion!Variable }
% TODO: this chapter name is confusing ... maybe rename to
% TODO: "File Integrity Checking with Bacula"?
\chapter{Using Bacula to Improve Computer Security}
-\label{_ChapterStart45}
+\label{VerifyChapter}
\index[general]{Security!Using Bacula to Improve Computer }
\index[general]{Using Bacula to Improve Computer Security }
%%
\chapter{The Windows Version of Bacula}
-\label{_ChapterStart7}
+\label{Win32Chapter}
\index[general]{Windows Version of Bacula}
At the current time only the File daemon or Client program has been tested on
projects / bacula / docs / commitdiff