Tweak newfeature chapter

diff --git a/docs/manuals/en/main/newbsfeatures.tex b/docs/manuals/en/main/newbsfeatures.tex
index d8c86ddf0331712a71aa4e5eccffc53f82d18afd..d3dc5bf188948393c48ccd6e73fbc296af841d24 100644 (file)
--- a/docs/manuals/en/main/newbsfeatures.tex
+++ b/docs/manuals/en/main/newbsfeatures.tex
@@ -9,11 +9,11 @@ chapter.
 
 \section{Bacula Enterprise 6.6.0}
 \subsection{Comm Line Compression}
-This version of Bacula now include communication
+Bacula Enterprise version 6.6.0 and later now includes 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
+version 6.6.0 or greater, comm line compression
+will be enabled, by default. If for some reason, you do not want
 comm line compression, you may disable it with the
 following directive:
 
@@ -21,33 +21,40 @@ following directive:
 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.
+\begin{lstlisting}
+bacula-dir.conf: Director resource
+bacula-fd.conf Client (or FileDaemon) resource
+bacula-sd.conf: Storage resource
+bconsole.conf: Console resource
+bat.conf: Console resource
+\end{lstlisting}
 
 \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
+\subsection{Read Only Storage Devices}
+This version of Bacula permits tdefining a Storage deamon device
+to be read-only. That is if the {\bf ReadOnly} 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 
+The the {\bf ReadOnly} directive can be defined in any bacula-sd.conf
+Device resource, and is most useful to reserve one or more 
 drives for restores. An example is:
 
 \begin{lstlisting}
 Read Only = yes
 \end{lstlisting}
 
-\subsection{Catalog Performance Improvement}
+\subsection{Catalog Performance Improvements}
 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
+Filename into the File record of the File table. 
+This permits some substantial performance improvements
+particularly for large (1GB or greater) databases.
+
+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
@@ -56,18 +63,23 @@ database while production jobs are running.  See the Bacula Systems
 White Paper ``Migration-to-6.6'' 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.
+This database format 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.
 
 \subsection{Plugin Restore Options}
-This version of Bacula permits to configure Plugins at the restore time. For
-example, it is now possible to choose the \texttt{datastore} where your VMware
-image will be restored, or for example to choose \texttt{pg\_restore} options
-directly. See specific Plugin whitepaper to get information about new restore
-options.
-
+This version of Bacula permits user configuration of Plugins at restore
+time.  For example, it is now possible to choose the \texttt{datastore}
+where your VMware image will be restored, or for example to choose
+\texttt{pg\_restore} options directly.  See specific Plugin whitepaper
+for more information about new restore options.
+
+The restore options, if implemented in a plugin, will be 
+presented to you during initiation of a restore either by
+command line or if available by a GUI such
+as BWeb.  For examples of the command line interface and
+the GUI interface, please see below:
 
 \begin{lstlisting}
 Run Restore job
@@ -102,12 +114,11 @@ Use above plugin configuration? (yes/mod/no): yes
 
 \end{lstlisting}
 
-Or via BMS restore interface (see Fig \vref{fig:bms-restore})
+Or via the BWeb restore interface (see Fig \vref{fig:bms-restore})
 
-%% turn me back on when vsphere-restore-gui image committed
-%%\bsysimageH{vsphere-restore-gui}{Choose datastore, ESXi or hostname at restore time}{fig:bms-restore}
+\bsysimageH{vsphere-restore-gui}{Choose datastore, ESXi or hostname at restore time}{fig:bms-restore}
 
-\subsection{Alldrives Plugin Improvement}
+\subsection{Alldrives Plugin Improvements}
 The \texttt{alldrives} plugin permits to simplify the FileSet creation of
 Windows Clients, the plugin will generate automatically a FileSet including all
 local drives.
@@ -115,8 +126,9 @@ local drives.
 \smallskip{}
 
 The \texttt{alldrives} plugin now accepts the \texttt{snapshot} option that
-permits to generate snapshots for all local drives but without adding them to
-the FileSet. It can be combined with the \texttt{vss} plugin.
+permits generating snapshots for all local Windows drives but without
+explicitly adding them to the FileSet.  It can be combined with the
+\texttt{vss} plugin. For example:
 
 \begin{lstlisting}
 FileSet {
@@ -128,12 +140,30 @@ FileSet {
 }
 \end{lstlisting}
 
-\subsection{Miscellaneous Additions}
+\subsection{New Truncate Command}
+We have added a new truncate command to bconsole, which
+will truncate a Volume if the Volume is purged and if
+the Volume is also marked {\bf Action On Purge = Truncate}.
+This feature was originally added in Bacula version 5.0.1,
+but the mechanism for actually doing the truncate required
+the user to enter a command such as:
 
-\begin{itemize}
-\item \texttt{truncate} command
-\item \texttt{resume} command
-\end{itemize}
+\begin{lstlisting}
+purge volume action=truncate storage=File pool=Default
+\end{lstlisting}
+
+The above command is now simplified to be:
+
+\begin{lstlisting}
+truncate storage=File pool=Default
+\end{lstlisting}
+
+\subsection{New Resume Command}
+This command does exactly the same thing as a 
+{\bf restart} command but for some users the
+name may be more logical since in general the 
+{\bf restart} command is used to resume running
+a Job that was incompleted.
 
 \section{Bacula Enterprise 6.4.x}
 
@@ -269,8 +299,8 @@ definition.
 
 \section{Bacula Enterprise 6.2.3}
 
-\subsection{New Job Edit Code \%P \%C}
-In various places such as RunScript, you have now access to \%P to get the
+\subsection{New Job Edit Codes \%P \%C}
+In various places such as RunScripts, you have now access to \%P to get the
 current Bacula process ID (PID) and \%C to know if the current job is a
 cloned job.
 

diff --git a/docs/upload b/docs/upload
index c80b70b6b971a1f3a57d9dc3a0d430086ac2c56f..7a11fa5b3b17e64c5b5970281eca46a291f8e79f 100755 (executable)
--- a/docs/upload
+++ b/docs/upload
@@ -7,7 +7,7 @@ fi
 cwd=`pwd`
 lang=$1
 src=$cwd/manuals/${lang}
-ver=6.2.0
+ver=6.5.2
 repo=release
 
 echo "ver=${ver}"
@@ -24,11 +24,11 @@ sendit()
   done
 }
 
-#dest=bacula:/var/www/bacula/6.2.x-manuals/${lang}
+#dest=bacula:/var/www/bacula/6.5.x-manuals/${lang}
 #echo "Sending to $dest"
 #sendit $src $dest
 
-dest=bsweb:/var/www/docs/6.2.x-manuals/${lang}
+dest=bsweb:/var/www/docs/6.5.x-manuals/${lang}
 echo "Sending to $dest"
 sendit $src $dest