ebl Update accurate note

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index d2338dea493c93cc4f976a6dcb0e5f35b88e3a60..6e658db4b480ffaa59aa308acadf1dd5c71898ff 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -10,27 +10,28 @@ versions to be released as Bacula version 3.0.0 near the end of 2008.
 
 \section{Accurate}
 \index[general]{Accurate Backup}
-As with most other backup programs, Bacula decides what files to backup 
-for Incremental and Differental backup by comparing the change (st\_ctime)
-and modification (st\_mtime) times of the file to the time the last backup completed.
-If one of those two times is later than the last backup time, then the file
-will be backed up.  This does not, however, permit tracking what files have
-been deleted and will miss any file with an old time that may have been
-restored or moved on the client filesystem.
-
-If the {\bf Accurate = \lt{}yes|no\gt{}} directive is enabled (default no) in the
-Job resource, the job will be run as an Accurate Job. For a {\bf Full}
-backup, there is no difference, but for {\bf Differential} and {\bf Incremental}
-backups, the Director will send a list of all previous files backed up, and the 
-File daemon will use that list to determine if any new files have been added or
-or moved and if any files have been deleted. This allows Bacula to make an accurate
-backup of your system to that point in time so that if you do a restore, it
-will restore your system exactly.  One note of caution about using Accurate backup is that
-it requires more resources (CPU and memory) on both the Director and
-the Client machines to create the list of previous files backed up, to send that
-list to the File daemon, for the File daemon to keep the list (possibly very big)
-in memory, and for the File daemon to do comparisons between every file in the 
-FileSet and the list.
+
+As with most other backup programs, Bacula decides what files to backup for
+Incremental and Differental backup by comparing the change (st\_ctime) and
+modification (st\_mtime) times of the file to the time the last backup
+completed.  If one of those two times is different than from last backup time,
+then the file will be backed up.  This does not, however, permit tracking what
+files have been deleted and will miss any file with an old time that may have
+been restored or moved on the client filesystem.
+
+If the {\bf Accurate = \lt{}yes|no\gt{}} directive is enabled (default no) in
+the Job resource, the job will be run as an Accurate Job. For a {\bf Full}
+backup, there is no difference, but for {\bf Differential} and {\bf
+  Incremental} backups, the Director will send a list of all previous files
+backed up, and the File daemon will use that list to determine if any new files
+have been added or or moved and if any files have been deleted. This allows
+Bacula to make an accurate backup of your system to that point in time so that
+if you do a restore, it will restore your system exactly.  One note of caution
+about using Accurate backup is that it requires more resources (CPU and memory)
+on both the Director and the Client machines to create the list of previous
+files backed up, to send that list to the File daemon, for the File daemon to
+keep the list (possibly very big) in memory, and for the File daemon to do
+comparisons between every file in the FileSet and the list.
 
 
 \section{Copy Jobs}