Clarify some restrictions

diff --git a/docs/manual/state.tex b/docs/manual/state.tex
index e30cd2a280253363a441cee36ea2fc67821cf6a5..bf5d17205ac9d8be0854d648d0e3a31a5710faac 100644 (file)
--- a/docs/manual/state.tex
+++ b/docs/manual/state.tex
@@ -208,13 +208,28 @@ In other words, what is and what is not currently implemented and functional.
    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 File System Modules (configurable routines for saving/restoring special
-   files) are not yet implemented.  
+   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 File System Modules (configurable routines for
+   saving/restoring special files) are not yet implemented.
+\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.
+\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
+   contents of both jobs. In other terms, Bacula cannot restore
+   two jobs in the same restore if the jobs' data blocks were
+   intermixed on the backup medium. This poses no restrictions
+   for normal backup jobs even if they are run simultaneously.
 \end{itemize}
 
 \section{Design Limitations or Restrictions}