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
+The Bacula Storage daemon now permits multiple jobs to simultaneously read
+the same disk Volume, which 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 faster with this version of Bacula. This is
+built-in to the Storage daemon, so it happens automatically and
transparently.
\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.
+however, you may want to create the Virtual backup based on a
+particular backup (point in time) that exists.
For example, if you have the following backup Jobs in your catalog:
\begin{lstlisting}
+-------+---------+-------+----------+----------+-----------+
\end{lstlisting}
-If you want to consolidate only the first 3 jobs and create a virtual backup
-equivalent to Job 1 + Job 2 + Job 3, you will use \texttt{jobid=3} in the
-\texttt{run} command, then Bacula will select the previous Full backup, the
-previous Differential (if any) and all subsequent Incremental jobs.
+For example, if you want to consolidate only the first 3 jobs and create a
+virtual backup equivalent to Job 1 + Job 2 + Job 3, you will use
+\texttt{jobid=3} in the \texttt{run} command, then Bacula will select the
+previous Full backup, the previous Differential (if any) and all subsequent
+Incremental jobs.
\begin{lstlisting}
run job=Vbackup jobid=3 level=VirtualFull
run job=Vbackup jobid=4-7 level=VirtualFull
\end{lstlisting}
-When using this feature, Bacula will automatically discard jobs that are not
-related to the current Job. For example, specifying \texttt{jobid=7,8},
-Bacula will discard the jobid 8.
+When using this feature, Bacula will automatically discard jobs that are
+not related to the current Job. For example, specifying
+\texttt{jobid=7,8}, Bacula will discard JobId 8 because it is not
+part of the same backup Job.
-If you know what you are doing and still want to consolidate jobs that have
+We do not recommend it, but really want to consolidate jobs that have
different names (so probably different clients, filesets, etc...), you must
use \texttt{alljobid=} keyword instead of \texttt{jobid=}.
\end{lstlisting}
\subsection{New Prune ``Expired'' Volume Command}
-
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.
+combined with the Truncate On Purge option. The Expired Prune option can
+be used instead of the \texttt{manual\_prune.pl} script.
\begin{lstlisting}
* prune expired volumes
\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
-current PID and the \%C to know if the current job is a cloned job.
+current Bacula process ID (PID) and \%C to know if the current job is a
+cloned job.
\section{Bacula Enterprise 6.2.0}
\subsection{BWeb Bacula Configuration GUI}
-
In Bacula Enterprise version 6.2, the BWeb Management Suite integrates a
Bacula configuration GUI module which is designed to help you create and
modify the Bacula configuration files such as bacula-dir.conf,
projects / bacula / docs / commitdiff