\chapter{New Features in 5.1.x}
This chapter presents the new features that have been added to the
current version of Bacula that is under development. This version will be
-released at some later date, probably near the end of 2010.
+released at some later date, probably near the end of April 2011.
\section{Restart Incomplete Job}
\section{New Tray Monitor}
-As the default Windows tray monitor doesn't work anymore with recent windows
-version, we added a new QT Tray Monitor that is available for both Linux and
-Windows. This new version allows you to run Backup from the menu.
+Since the old integrated Windows tray monitor doesn't work anymore with
+recent Windows versions, we have written a new Qt Tray Monitor that is available
+for both Linux and Windows. This new version allows you to run Backup from
+the tray monitor menu.
\begin{figure}[htbp]
\centering
\medskip
This project was funded by Bacula Systems and is available with Bacula
-Enterprise Edition and Community Edition.
+the Enterprise Edition and the Community Edition.
-\section{Purge Migration Job when Completed}
+\section{Purge Migration Job}
-A new directive may be added to the Migration Job definition in the Director
-configuration file to purge the job migrated at the end of a migration.
+The new {\bf Purge Migration Job} directive may be added to the Migration
+Job definition in the Director's configuration file. When it is enabled
+the Job that was migrated during a migration will be purged at
+the end of the migration job.
For example:
\begin{verbatim}
\section{Job Bandwidth Limitation}
-A new directive may be added to FileDaemon or Director to allow users to limit
-the bandwidth used by a Job on a Client. It can be set for all Jobs globally,
-per Directors in the File Daemon configuration, or per Job in the Director
-configuration file.
+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}
}
\end{verbatim}
-The above example would cause job \texttt{localhost-data} to not exceed 5MB/s
-of throughput when sending data to the Storage Daemon.
+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.
The \texttt{limit} parameter is in KB/s.
\medskip
-This project was funded by Bacula Systems and is available with Bacula
-Enterprise Edition and Community Edition.
+This project was funded by Bacula Systems and is available in
+the Enterprise Edition and the Community Edition.
\section{Support for MSSQL Block Level Backup}
-This project was funded by Bacula Systems and is available with Bacula
+This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
\section{Support for NDMP protocol}
}
\end{verbatim}
-This project was funded by Bacula Systems and is available with Bacula
+This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
\section{Incremental/Differential Block Level Difference Backup}
}
\end{verbatim}
-This project was funded by Bacula Systems and is available with Bacula
+This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
\section{Include All Windows Drives in FileSet}
\end{verbatim}
-This project was funded by Bacula Systems and is available with Bacula
+This project was funded by Bacula Systems and is available with the Bacula
Enterprise Edition.
\section{SQL Catalog Enhancements}