\label{AuthorizationErrors}
\subsection*{I'm Getting Authorization Errors. What is Going On? }
\item [I'm Getting Authorization Errors. What is Going On? ]
- \index[general]{I'm Getting Authorization Errors. What is Going On? }
+\index[general]{Authorization Errors}
+\index[general]{Concurrent Jobs}
For security reasons, Bacula requires that both the File daemon and the
Storage daemon know the name of the Director as well as its password. As a
consequence, if you change the Director's name or password, you must make
Why? }
\item [Bacula Runs Fine but Cannot Access a Client on a Different Machine.
Why? ]
- \index[general]{Bacula Runs Fine but Cannot Access a Client on a Different
- Machine. Why? }
+\index[general]{Cannot Access a Client}
There are several reasons why Bacula could not contact a client on a
different machine. They are:
problems?}
\item [All my Jobs are scheduled for the same time. Will this cause
problems? ]
- \index[general]{All my Jobs are scheduled for the same time. Will this cause
- problems? }
+\index[general]{Schedule problems}
No, not at all. Bacula will schedule all the Jobs at the same time, but will
run them one after another unless you have increased the number of
simultaneous jobs in the configuration files for the Director, the File
\subsection*{Can Bacula Backup and Restore Files Greater than 2 Gigabytes?}
\item [Can Bacula Backup and Restore Files Greater than 2 Gigabytes in
Size? ]
-\index[general]{Can Bacula Backup and Restore Files Greater than 2 Gigabytes in
-Size? }
+\index[general]{Large file support}
If your operating system permits it, and you are running Bacula version 1.26
or later, the answer is yes. To the best of our knowledge all client system
supported by Bacula can handle files larger than 2 Gigabytes.
there a better way than {\bf ./bacula stop} to stop it?}
\item [I Started A Job then Decided I Really Did Not Want to Run It. Is
there a better way than {\bf ./bacula stop} to stop it?]
- \index[general]{I Started A Job then Decided I Really Did Not Want to
- Run It. Is there a better way than ./bacula stop to stop it? } Yes,
+\index[general]{Cancelling jobs}
+ Yes,
you normally should use the Console command {\bf cancel} to cancel a Job
that is either scheduled or running. If the Job is scheduled, it will
be marked for cancellation and will be canceled when it is scheduled to
Bacula\raisebox{.6ex}{{\footnotesize \textsuperscript{\textregistered}}}?}
\item [Why have You Trademarked the Name
Bacula\raisebox{.6ex}{{\footnotesize \textsuperscript{\textregistered}}}?]
-\index[general]{Why have You Trademarked the Name
-Bacula\textsuperscript{\textregistered}? }
+\index[general]{Bacula Trademark}
We have trademarked the name Bacula to ensure that all media written by any
program named Bacula will always be compatible. Anyone may use the name
Bacula, even in a derivative product as long as it remains totally compatible
\subsection*{Why is Your Online Document for Version 1.37 but the Released Version is 1.36?}
\item [Why is Your Online Document for Version 1.37 of Bacula when the
Currently Release Version is 1.36?]
-\index[general]{Why is Your Online Document for Version 1.37 but Released Version is 1.36? }
+\index[general]{Multiple manuals}
As Bacula is being developed, the document is also being enhanced, more often
than not it has clarifications of existing features that can be very useful
to our users, so we publish the very latest document. Fortunately it is rare
\subsection*{My retention periods don't work}
\item [I Change Recycling, Retention Periods, or File Sizes in my Pool
Resource and they Still Don't Work.]
- \index[general]{I Change Recycling, Retention Periods, or File Sizes in my
-Pool
- Resource and they Still Don't Work. }
+\index[general]{Recycling}
+\index[general]{Retention Periods}
+\index[general]{Pool changes}
The different variables associated with a Pool are defined in the Pool
Resource, but are actually read by Bacula from the Catalog database. On
Bacula versions prior to 1.30, after changing your Pool Resource, you must
\subsection*{Why aren't my files compressed?}
\item [I Have Configured Compression On, But None of My Files Are
Compressed. Why?]
- \index[general]{I Have Configured Compression On, But None of My Files Are
- Compressed. Why? }
+\index[general]{Compression}
There are two kinds of compression. One is tape compression. This is done by
the tape drive hardware, and you either enable or disable it with system
tools such as {\bf mt}. This compression works independently of Bacula.
\label{NewTape}
\item [Bacula is Asking for a New Tape After 2 GB of Data but My Tape
holds 33 GB. Why?]
-\index[general]{Bacula is Asking for a New Tape After 2 GB of Data but My Tape
-holds 33 GB. Why? }
+\index[general]{Tape capacity}
There are several reasons why Bacula will request a new tape.
\begin{itemize}
\subsection*{Incremental backups are not working}
\item [Bacula is Not Doing the Right Thing When I Request an Incremental
Backup. Why?]
- \index[general]{Bacula is Not Doing the Right Thing When I Request an
-Incremental
- Backup. Why? }
+ \index[general]{Incremental backups}
As explained in one of the previous questions, Bacula will automatically
upgrade an Incremental or Differential job to a Full backup if it cannot
find
projects / bacula / docs / blobdiff