Start 6.6 new features section in doc

diff --git a/docs/manuals/en/main/newbsfeatures.tex b/docs/manuals/en/main/newbsfeatures.tex
index e8bed3bc2c87123cc6110b40da718e5670fad6e3..6248b2c74805ee4d7831a752dd6a466ece8f219e 100644 (file)
--- a/docs/manuals/en/main/newbsfeatures.tex
+++ b/docs/manuals/en/main/newbsfeatures.tex
@@ -7,6 +7,60 @@ In addition to the features in this chapter, the Enterprise version
 includes all the Community features described in the Community new Features
 chapter.
 
+\section{Bacula Enterprise 6.6.0}
+\subsection{Comm Line Compression}
+This version of Bacula now include communication
+line compression. It is turned on by default, and if the
+two Bacula components (Dir, FD, SD, bconsole) are both 
+version 6.6.0 or greater, by default, comm line compression
+will be enabled. If for some reason, you do not want
+comm line compression, you may disable it with the
+following directive:
+
+\begin{lstlisting}
+Comm Compression = no
+\end{lstlisting}
+
+\smallskip
+This directive can appear in the following resources:
+bacula-dir.conf: Director; bacula-fd.conf Client (or FileDaemon);
+bacula-sd.conf: Storage; bconsole.conf: Console; bat.conf: Console.
+
+\smallskip
+In many cases, the volume of data transmitted across the
+communications line can be reduced by a factor of three when 
+this directive is enabled (default).
+
+\subsection{Read Only Devices}
+This version of Bacula permits defining a Storage deamon device
+to be read-only. That is if this directive is specified and
+enabled, the drive can only be used for read operations.
+The the ReadOnly directive can be defined in any bacula-sd.conf
+Device resource, and can be used to reserve one or more 
+drives for restores. An example is:
+
+\begin{lstlisting}
+Read Only = yes
+\end{lstlisting.
+
+\subsection{Catalog Performance Improvement}
+There is a new Bacula database format (schema) in this version
+of Bacula that eliminates the FileName table by placing the
+Filename into the File record of the File table. The
+update_xxx_catalog script will automatically update the
+Bacula database format, but you should realize that for 
+very large databases (greater than 1GB), it may take some
+time, and there are several different options for doing the
+update: 1. Shudown the database and update it. 2. Update the
+database while production jobs are running.  See the Bacula Systems
+White Paper on this subject.
+
+\smallskip
+This change can provide very significant improvements in the
+speed of metadata insertion into the database, and in some cases
+(backup of large email servers) can significantly reduce the size
+of the database.
+
 \section{Bacula Enterprise 6.4.0}
 \subsection{Deduplication Optimized Volumes}
 This version of Bacula includes a new alternative (or additional)