added some sections from the bacula faq document

manuals/en/main/bareos-manual-main-reference.tex

@@ -133,12 +133,14 @@ \chapter{Accurate Mode}
 
 \include{basejob}
 
-\chapter{Concurrent Jobs}
-    \label{ConcurrentJobs}
-    \TODO{to be written}
-
 %tape
 \include{win32}
+
+\chapter{Network setup}
+    \subsection{Passive Clients}
+        \label{PassiveClient}
+        \TODO{to be written}
+
 \include{tls}
 \include{dataencryption}
 
@@ -188,7 +190,7 @@ \chapter{Howtos}
 \include{rescue}
 
 \chapter{Troubleshooting}
-\include{troubleshooting}
+\input{troubleshooting}
 
 \chapter{Bareos Copyright, Trademark, and Licenses}
 \label{LicenseChapter}

manuals/en/main/dirdconf.tex

@@ -203,8 +203,9 @@ \section{Director Resource}
 that provide the {\bf setsockopt} TCP\_KEEPIDLE function (Linux, ...).
 The default value is zero, which means no change is made to the socket.
 
+\directive{dir}{Maximum Concurrent Jobs}{number}{}{1}
 \label{DirMaxConJobs}
-\item [Maximum Concurrent Jobs = {\textless}number{\textgreater}] \hfill \\
+%\item [Maximum Concurrent Jobs = {\textless}number{\textgreater}] \hfill \\
 \index[dir]{Maximum Concurrent Jobs}
 \index[dir]{Directive!Maximum Concurrent Jobs}
 \index[general]{Simultaneous Jobs}
@@ -221,6 +222,8 @@ \section{Director Resource}
 to disk simultaneously, then write one spool file at a time to the volume
 thus avoiding excessive interleaving of the different job blocks.
 
+See also the section about \ilink{Concurrent Jobs}{ConcurrentJobs}.
+
 \item [FD Connect Timeout = {\textless}time{\textgreater}] \hfill \\
 \index[dir]{FD Connect Timeout}
 \index[dir]{Directive!FD Connect Timeout}

manuals/en/main/howto.tex

@@ -1,3 +1,30 @@
+
+\section{Use a dummy device to test the backup}
+\label{testbackup}
+If your are testing your configuration, but don't want to store the backup data,
+it is possible to use a dummy FIFO device to test your configuration, see \ilink{Stored configuration}{SetupFifo}.
+
+Obviously, it can not be used to do a restore.
+
+\footnotesize
+\begin{verbatim}
+Device {
+  Name = NULL
+  Media Type = NULL
+  Device Type = Fifo
+  Archive Device = /dev/null
+  LabelMedia = yes
+  Random Access = no
+  AutomaticMount = no
+  RemovableMedia = no
+  MaximumOpenWait = 60
+  AlwaysOpen = no
+}
+\end{verbatim}
+\normalsize
+
+
+
 \section{Backing Up Third Party Databases}
 \index[general]{Backing Up Third Party Databases}
 \index[general]{Database!Backing Up Third Party}

manuals/en/main/troubleshooting.tex

@@ -1,4 +1,152 @@
 
+\section{Client Access Problems}
+\label{AccessProblems}
+\index[general]{Cannot Access a Client}
+   There are several reasons why Bareos could not contact a client  on a
+   different machine. They are:  
+
+\begin{itemize}
+\item Check if the client file daemon is really running.
+\item The Client address or port is incorrect or not resolved by  DNS. See if
+   you can ping the client machine using the same  address as in the Client
+   record.  
+\item You have a firewall, and it is blocking traffic on port  9102 between
+   the Director's machine and the Client's  machine (or on port 9103 between the
+   Client and the Storage daemon  machines). 
+\item If your system is using Tcpwrapper ({\bf hosts.allow} or {\bf hosts.deny} file), verify that is
+   permitting access.
+\item Your password or names are not correct in both the Director and  the
+   Client machine. Try configuring everything identical to  how you run the
+   client on the same machine as the Director, but  just change the address. If
+   that works, make the other changes  one step at a time until it works.  
+\item You may also be having problems between your File daemon and your
+   Storage daemon. The name you use in the Storage resource of your
+   Director's conf file must be known (resolvable) by the File daemon, 
+   because it is passed symbolically to the File daemon, which then
+   resolves it to get an IP address used to contact the Storage daemon.
+\end{itemize}
+
+Some of the DNS and Firewall problems can be circumvented by configuring clients in network passive mode, see the section about \ilink{Passive Clients}{PassiveClient}.
+
+\subsection{Authorization Errors}
+\index[general]{Authorization Errors}
+\index[general]{Concurrent Jobs}
+\label{AuthorizationErrors}
+
+   For security reasons, Bareos 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
+   the corresponding change in the Storage daemon's and  in the File daemon's
+   configuration files.  
+
+   During the authorization process, the Storage daemon and File daemon
+   also require that the Director authenticates itself, so both ends
+   require the other to have the correct name and password.
+
+   If you have edited the configuration files and modified any name or any password,
+   and you are getting authentication errors, then your best bet is to go
+   back to the original configuration files generated by the Bareos 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 Bareos}{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 configuration files.
+
+   Another reason that you can get authentication errors is if you are
+   running Multiple Concurrent Jobs in the Director, but you have not set
+   them in the File daemon or the Storage daemon.  Once you reach their
+   limit, they will reject the connection producing authentication (or
+   connection) errors.
+
+   Some users report that authentication fails if there is not a proper
+   reverse DNS lookup entry for the machine.  This seems to be a
+   requirement of gethostbyname(), which is what Bareos uses to translate
+   names into IP addresses.  If you cannot add a reverse DNS entry, or you
+   don't know how to do so, you can avoid the problem by specifying an IP
+   address rather than a machine name in the appropriate Bareos configuration file.
+
+   Here is a picture that indicates what names/passwords in which
+   files/Resources must match up:
+
+   \includegraphics{\idir Conf-Diagram.eps}  
+
+   In the left column, you will find the Director, Storage, and  Client
+   resources, with their names and passwords -- these  are all in {\bf
+   bareos-dir.conf}. The right column is where the corresponding values
+   should be found in the  Console, Storage daemon (SD), and File daemon (FD)
+   configuration  files.  
+
+   Another thing to check is to ensure that the Bareos component you are
+   trying to access has {\bf Maximum Concurrent Jobs} set large enough to
+   handle each of the Jobs and the Console that want to connect
+   simultaneously.  Once the maximum connections has been reached, each
+   Bareos component will reject all new connections.
+
+\section{Concurrent Jobs}
+\label{ConcurrentJobs}
+\index[general]{Jobs!Concurrent}
+\index[general]{Running Concurrent Jobs}
+\index[general]{Concurrent Jobs}
+
+Bareos can run multiple concurrent jobs. 
+Using the {\bf Maximum Concurrent Jobs} directive, you
+can configure how many and which jobs can be run simultaneously. 
+The Director's default value for {\bf Maximum Concurrent Jobs} is "1".
+
+To initially setup concurrent jobs you need to define {\bf Maximum Concurrent Jobs} in 
+the Director's configuration file (bareos-dir.conf) in the 
+Director, Job, Client, and Storage resources.
+
+Additionally the File daemon, and the Storage daemon each have their own
+{\bf Maximum Concurrent Jobs} directive that sets the overall maximum
+number of concurrent jobs the daemon will run.  The default for both the
+File daemon and the Storage daemon is "20".
+
+For example, if you want two different jobs to run simultaneously backing up
+the same Client to the same Storage device, they will run concurrently only if
+you have set {\bf Maximum Concurrent Jobs} greater than one in the Director
+resource, the Client resource, and the Storage resource in bareos-dir.conf. 
+
+We recommend that you read the \ilink{Data
+Spooling}{SpoolingChapter} of this manual first, then test your multiple
+concurrent backup including restore testing before you put it into
+production.
+
+Below is a super stripped down bareos-dir.conf file showing you the four
+places where the the file must be modified to allow the same job {\bf
+NightlySave} to run up to four times concurrently. The change to the Job
+resource is not necessary if you want different Jobs to run at the same time,
+which is the normal case. 
+
+\begin{bconfig}{Concurrent Jobs Example}
+#
+# Bareos Director Configuration file -- bareos-dir.conf
+#
+Director {
+  Name = rufus-dir
+  Maximum Concurrent Jobs = 4
+  ...
+}
+Job {
+  Name = "NightlySave"
+  Maximum Concurrent Jobs = 4
+  Client = rufus-fd
+  Storage = File
+  ...
+}
+Client {
+  Name = rufus-fd
+  Maximum Concurrent Jobs = 4
+  ...
+}
+Storage {
+  Name = File
+  Maximum Concurrent Jobs = 4
+  ...
+}
+\end{bconfig}
+
+
 \input{ansi-labels}
 
 \section{Tape Drive}