will include the Community features described in the Community new Features
chapter.
+\section{Restart Incomplete Job}
+
+
+\medskip
+This project was funded by Bacula Systems and is available with Bacula
+Enterprise Edition.
+
\section{Support for MSSQL Block Level Backup}
This project was funded by Bacula Systems and is available with the Bacula
This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
+\section{Job Bandwidth Limitation}
+
+The new {\bf Job Bandwidth Limitation} directive may be added to the File
+daemon's and/or Director's configuration to limit the bandwidth used by a Job
+on a Client. It can be set in the File daemon's conf file for all Jobs run in
+that File daemon, or it can be set for each Job in the Director's conf file.
+
+For example:
+\begin{verbatim}
+FileDaemon {
+ Name = localhost-fd
+ Working Directory = /some/path
+ Pid Directory = /some/path
+ ...
+ Maximum Bandwidth Per Job = 5Mb/s
+}
+\end{verbatim}
+
+The above example would cause any jobs running with the FileDaemon to not
+exceed 5Mb/s of throughput when sending data to the Storage Daemon.
+
+You can specify the speed parameter in k/s, Kb/s, m/s, Mb/s.
+
+For example:
+\begin{verbatim}
+Job {
+ Name = locahost-data
+ FileSet = FS_localhost
+ Accurate = yes
+ ...
+ Maximum Bandwidth = 5Mb/s
+ ...
+}
+\end{verbatim}
+
+The above example would cause Job \texttt{localhost-data} to not exceed 5MB/s
+of throughput when sending data from the File daemon to the Storage daemon.
+
+A new console command \texttt{setbandwidth} permits to set dynamically the
+maximum throughput of a running Job or for future jobs of a Client.
+
+\begin{verbatim}
+* setbandwidth limit=1000000 jobid=10
+\end{verbatim}
+
+The \texttt{limit} parameter is in Kb/s.
+
+\medskip
+This project was funded by Bacula Systems and is available in
+the Enterprise Edition.
+
\section{Incremental/Differential Block Level Difference Backup}
The new \texttt{delta} Plugin is able to compute and apply signature-based file
that are described in another chapter. A subscription to Bacula Systems
is required for the Enterprise version.
-\section{Restart Incomplete Job}
-
-
-\medskip
-This project was funded by Bacula Systems and is available with Bacula
-Enterprise Edition and Community Edition.
-
\section{New Tray Monitor}
Since the old integrated Windows tray monitor doesn't work anymore with
This project was submited by Dunlap Blake, testing and documentation was funded
by Bacula Systems.
-\section{Job Bandwidth Limitation}
-
-The new {\bf Job Bandwidth Limitation} directive may be added to the File
-daemon's and/or Director's configuration to limit the bandwidth used by a Job
-on a Client. It can be set in the File daemon's conf file for all Jobs run in
-that File daemon, or it can be set for each Job in the Director's conf file.
-
-For example:
-\begin{verbatim}
-FileDaemon {
- Name = localhost-fd
- Working Directory = /some/path
- Pid Directory = /some/path
- ...
- Maximum Bandwidth Per Job = 5Mb/s
-}
-\end{verbatim}
-
-The above example would cause any jobs running with the FileDaemon to not
-exceed 5Mb/s of throughput when sending data to the Storage Daemon.
-
-You can specify the speed parameter in k/s, Kb/s, m/s, Mb/s.
-
-For example:
-\begin{verbatim}
-Job {
- Name = locahost-data
- FileSet = FS_localhost
- Accurate = yes
- ...
- Maximum Bandwidth = 5Mb/s
- ...
-}
-\end{verbatim}
-
-The above example would cause Job \texttt{localhost-data} to not exceed 5MB/s
-of throughput when sending data from the File daemon to the Storage daemon.
-
-A new console command \texttt{setbandwidth} permits to set dynamically the
-maximum throughput of a running Job or for future jobs of a Client.
-
-\begin{verbatim}
-* setbandwidth limit=1000000 jobid=10
-\end{verbatim}
-
-The \texttt{limit} parameter is in Kb/s.
-
-\medskip
-This project was funded by Bacula Systems and is available in
-the Enterprise Edition and the Community Edition.
-
\section{SQL Catalog Enhancements}