Tweak Bacula restrictions

[bacula/docs] / docs / manuals / en / main / state.tex

diff --git a/docs/manuals/en/main/state.tex b/docs/manuals/en/main/state.tex
index 547be054148091397438fa7693b82dc5f6443de8..a9b37c94c5d8b0e9588b599dc0b84f6d580c1706 100644 (file)
--- a/docs/manuals/en/main/state.tex
+++ b/docs/manuals/en/main/state.tex
@@ -212,6 +212,8 @@ In other words, what is and what is not currently implemented and functional.
    two jobs in the same restore if the Jobs' data blocks were
    intermixed on the backup medium. The problem is resolved by
    simply doing two restores, one for each Job. 
+   Normally this can happen only if you manually enter specific
+   JobIds to be restored in a single restore Job.
 \item Bacula can generally restore any backup made from one client
    to any other client. However, if the architecture is significantly
    different (i.e. 32 bit architecture to 64 bit or Win32 to Unix),
@@ -232,6 +234,18 @@ In other words, what is and what is not currently implemented and functional.
    this does not apply to filenames, which may be arbitrarily long.
 \item Command line input to some of the stand alone tools -- e.g. btape,
    bconsole is restricted to several hundred characters maximum.
+   Normally, this is not a restriction, except in the case of listing
+   multiple Volume names for programs such as {\bf bscan}. To avoid
+   this command line length restriction, please use a {\bf .bsr} 
+   file to specify the Volume names.
+\item Bacula configuration files for each of the components can be
+   any length. However, the length of an individual line is limited
+   to 500 characters after which it is truncated.  If you need lines
+   longer than 500 characters for directives such as ACLs where
+   they permit a list of names are character strings simply
+   specify multiple short lines repeating the directive on
+   each line but with different list values.
+
 \end{itemize}
 
 \section{Items to Note}
@@ -245,6 +259,8 @@ In other words, what is and what is not currently implemented and functional.
   or by explicitly updating the date/time stamp on all moved files.
 \item In older versions of Bacula ($<=$ 3.0.x), if you have over 4 billion file
   entries stored in your database, the database FileId is likely to overflow.
+  This limitation does not apply to current Bacula versions.
 \item In non \textsl{Accurate} mode, files deleted after a Full save will be
   included in a restoration. This is typical for most similar backup programs.
+  To avoid this, use Accurate mode backup.
 \end{itemize}