update Current limitation chapter

diff --git a/docs/manuals/en/concepts/state.tex b/docs/manuals/en/concepts/state.tex
index 066d8f2fda915d376aed28f1e061b5ff80023721..4d954b8718bdae31819413bbacabaefe8aa898ef 100644 (file)
--- a/docs/manuals/en/concepts/state.tex
+++ b/docs/manuals/en/concepts/state.tex
@@ -203,32 +203,15 @@ In other words, what is and what is not currently implemented and functional.
 \index[general]{Restrictions!Current Implementation }
 
 \begin{itemize}
-\item If you have over 4 billion file entries stored in your database,  the
-   database FileId is likely to overflow. This is a monster database,  but still
-   possible. Bacula's FileId fields have been modified so that they can be
-   upgraded from 32 to 64 bits in version 1.39 or later, but you must
-   manually do so. 
-\item Files deleted after a Full save will be included in a restoration. This  
-   is typical for most similar backup programs (we have a project to 
-   correct this).
-\item Bacula's Differential and Incremental backups are based on
-   time stamps.  Consequently, if you move files into an existing
-   directory or move a whole directory into the backup fileset
-   after a Full backup, those files will probably not be backed
-   up by an Incremental save because they will have old dates.
-   You must explicitly update the date/time stamp on all moved
-   files (we have a project to correct this).
+\item Bacula's Differential and Incremental \textsl{normal} backups are based
+  on time stamps.  Consequently, if you move files into an existing directory
+  or move a whole directory into the backup fileset after a Full backup, those
+  files will probably not be backed up by an Incremental save because they will
+  have old dates.  You must run backups in Accurate mode or explicitly update
+  the date/time stamp on all moved files. % TODO: remove it ?
 \item File System Modules (configurable routines for
    saving/restoring special files) are not yet implemented.  However,
    this feature is easily implemented using RunScripts.
-\item Bacula supports doing backups and restores to multiple
-   devices of different media type and multiple Storage daemons.
-   However, if you have backed up a job to multiple storage
-   devices, Bacula can do a restore from only one device, which
-   means that you will need to manually edit the bootstrap file
-   to split it into two restores if you split the backup across 
-   storage devices.  This restriction has been removed in version
-   2.2.0 and later, but it is not yet fully tested.
 \item Bacula cannot restore two different jobs in the same
    restore if those jobs were run simultaneously, unless you had
    data spooling turned on and the spool file held the full
@@ -243,6 +226,10 @@ In other words, what is and what is not currently implemented and functional.
    on other Unix/Linux machines; there are reports that Zlib compression
    written with 64 bit machines does not always read correctly on a 32 bit
    machine).
+\item In older version of Bacula ($<=$ 3.x), if you have over 4 billion file
+  entries stored in your database, the database FileId is likely to overflow.
+\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.
 \end{itemize}
 
 \section{Design Limitations or Restrictions}