update with new Maximum Concurent jobs for devices

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index 3914e835cde8196ddd242b0d4438ef7c19bbb599..d5c6d0f1ebb1ad8f9bbe080a10f66732ec82577d 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -9,6 +9,17 @@ 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.
 
+
+\section{Maximum concurent jobs for Devices}
+\label{sec:maximumconcurentjobdevice}
+
+A new Device directive in the Storage Daemon configuration permits to set the
+maximum number of Jobs that can run concurrently on specified Device. This
+directive permits to dispatch jobs on multiple drives, and when this limit is
+reached, the Storage Daemon will start new jobs on any other available
+compatible drive. So it's possible to use the same pool on multiple drives like
+with the broken \textsl{Prefer Mounted Volume} option.
+
 \section{Restore from Multiple Storage Daemons}
 \index[general]{Restore}
 
@@ -16,8 +27,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.