From: Kern Sibbald <kern@sibbald.com>
Date: Sun, 12 May 2013 15:41:47 +0000 (+0200)
Subject: Add more to the new features chapter
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=4a73e0d2cbb8d4065b8cd3a3b506b03a513b14dc;p=bacula%2Fdocs

Add more to the new features chapter
---

diff --git a/docs/manuals/en/main/newbsfeatures.tex b/docs/manuals/en/main/newbsfeatures.tex
index 5347face..c2d3c9ac 100644
--- a/docs/manuals/en/main/newbsfeatures.tex
+++ b/docs/manuals/en/main/newbsfeatures.tex
@@ -8,12 +8,32 @@ will include the Community features described in the Community new Features
 chapter.
 
 \section{Bacula Enterprise 6.4.0}
-\subsection{VirtualFull Backup Consolidation Enhancements}
+\subsection{Deduplication Optimized Volumes}
+This version of Bacula includes a new alternative (or additional)
+Volume format that optimized the placement of files such
+that an underlying deduplicating filesystem such as ZFS
+can optimally deduplicate the backup data that is written
+by Bacula. These are called Deduplication Optimized Volumes
+or Aligned Volumes for short. The details of how to use this
+feature and its considerations are in the Bacula Systems
+Deduplication Optimized Volumes white paper.
+
+\subsection{Migration/Copy/VirtualFull Performance Enhancements}
+The new feature that permits the Bacula Storage daemon
+to read the same disk Volume gives substantial performance 
+enhancements when running Migration, Copy, or VirtualFull jobs
+that read disk Volumes. Our testing shows that when running
+multiple simultaneous jobs, the jobs can finish up to ten
+times as fast with this version of Bacula. This is built-in
+to the Storage daemon, so it happens automatically and 
+transparently.
 
-By default Bacula is selecting jobs automatically, however, you may want to
-choose any point in time to create the Virtual backup.
+\subsection{VirtualFull Backup Consolidation Enhancements}
+By default Bacula selects jobs automatically for a VirtualFull,
+however, you may want to choose any point in time to create the
+Virtual backup.
 
-For example, if you have the following Jobs in your catalog:
+For example, if you have the following backup Jobs in your catalog:
 \begin{lstlisting}
 +-------+---------+-------+----------+----------+-----------+
 | JobId | Name    | Level | JobFiles | JobBytes | JobStatus |
@@ -41,7 +61,7 @@ run job=Vbackup jobid=3 level=VirtualFull
 If you want to consolidate a specific job list, you must specify the exact
 list of jobs to merge in the run command line.  For example, to consolidate
 the last Differential and all subsequent Incremental, you will use
-\texttt{jobid=4,5,6,7} or \texttt{jobid=4-7} in the run command line. As one
+\texttt{jobid=4,5,6,7} or \texttt{jobid=4-7} on the run command line. As one
 of the Job in the list is a Differential backup, Bacula will set the new job
 level to Differential. If the list is composed only with Incremental jobs,
 the new job will have a level set to Incremental.
@@ -64,11 +84,11 @@ run job=Vbackup alljobid=1-3,6-8 level=VirtualFull
 
 \subsection{New Prune ``Expired'' Volume Command}
 
-In Bacula Enterprise 6.4, this is now possible to prune all volumes (from a
-pool, or globally) that are ``expired''. This option can be scheduled after or
-before the backup of the Catalog and can be combined with the Truncate On Purge
-option. This option can be used instead of the \texttt{manual\_prune.pl}
-script.
+In Bacula Enterprise 6.4, it is now possible to prune all volumes
+(from a pool, or globally) that are ``expired''.  This option can be
+scheduled after or before the backup of the Catalog and can be
+combined with the Truncate On Purge option.  This option can be used
+instead of the \texttt{manual\_prune.pl} script.
 
 \begin{lstlisting}
 * prune expired volumes