Update to separate manual versions

[bacula/docs] / docs / manuals / en / concepts / newfeatures.tex

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index 3914e835cde8196ddd242b0d4438ef7c19bbb599..dab12d10a96aa39ccf14782854bca36a47d34d52 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -2,12 +2,24 @@
 
 %%
 
-\chapter{New Features in 3.0.3}
+\chapter{New Features in 3.1.4 (Development Version}
 \label{NewFeaturesChapter}
 
-This chapter presents the new features added to the development 3.0.3
-versions to be released as Bacula version 3.0.3 sometime in 2009 or early
-2010.
+This chapter presents the new features that are currently under development
+in the 3.1.x versions to be released as Bacula version 3.2.0 sometime in
+late 2009 or early 2010.
+
+
+\section{Maximum concurent jobs for Devices}
+\label{sec:maximumconcurentjobdevice}
+
+{\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
+Daemon configuration permits setting the maximum number of Jobs that can
+run concurrently on a specified Device.  Using this directive, it is
+possible to have different Jobs using multiple drives, because when the
+Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
+Jobs on any other available compatible drive.  This facilitates writing to
+multiple drives with multiple Jobs that all use the same Pool.
 
 \section{Restore from Multiple Storage Daemons}
 \index[general]{Restore}
@@ -16,8 +28,8 @@ Previously, you were able to restore from multiple devices in a single Storage
 Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
 example, if your full backup runs on a Storage Daemon with an autochanger, and
 your incremental jobs use another Storage Daemon with lots of disks, Bacula
-will switch automatically from one Storage Daemon to an other within the same Restore
-job.
+will switch automatically from one Storage Daemon to an other within the same
+Restore job.
 
 You must upgrade your File Daemon to version 3.0.3 to use this feature.
 
@@ -86,6 +98,71 @@ FileSet {
 
 This project was funded by Bacula Systems.
 
+
+\section{Accurate Fileset options}
+\label{sec:accuratefileset}
+
+In previous version, the accurate code was using file time creation and
+modification to determine if a file was modified or not. Now you can specify
+witch attribute to use (time, size, checksum, permission, owner, group,
+\dots).
+
+\begin{verbatim}
+FileSet {
+  Name = Full
+  Include = {
+    Options {
+       Accurate = mcs5
+       Verify   = pin5
+    }
+    File = /
+  }
+}
+\end{verbatim}
+
+\begin{description}  
+\item {\bf i}
+  compare the inodes  
+  
+\item {\bf p}
+  compare the permission bits  
+  
+\item {\bf n}
+  compare the number of links  
+  
+\item {\bf u}
+  compare the user id  
+  
+\item {\bf g}
+  compare the group id  
+  
+\item {\bf s}
+  compare the size  
+  
+\item {\bf a}
+  compare the access time  
+  
+\item {\bf m}
+  compare the modification time (st\_mtime)  
+  
+\item {\bf c}
+  compare the change time (st\_ctime)  
+  
+\item {\bf d}
+  report file size decreases  
+  
+\item {\bf 5}
+  compare the MD5 signature  
+  
+\item {\bf 1}
+  compare the SHA1 signature  
+\end{description}
+
+\textbf{Important note:} If you decide to use checksum in Accurate jobs, the
+File Daemon will have to read all files even if they won't be saved. It
+increases the I/O load, but also the security. By default, Bacula will 
+check modification/creation time and size.
+
 \section{Bvfs API}
 \label{sec:bvfs}
 
@@ -217,10 +294,10 @@ access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
   \label{fig:achcontent}
 \end{figure}
 
-\chapter{New Features in 3.0.2}
+\chapter{New Features in Released Version 3.0.2}
 
-This chapter presents the new features added to the development 3.0.2
-versions to be released as Bacula version 3.0.2 in july 2009.
+This chapter presents the new features added to the
+Released Bacula Version 3.0.2.
 
 \section{Full restore from a given JobId}
 \index[general]{Restore menu}