\label{NewFeaturesChapter}
This chapter presents the new features added to the development 3.0.3
-versions to be released as Bacula version 3.0.3 sometime in 2009.
+versions to be released as Bacula version 3.0.3 sometime in 2009 or early
+2010.
-\section{Restore from multiple Storage Daemon}
+\section{Restore from Multiple Storage Daemons}
\index[general]{Restore}
Previously, you were able to restore from multiple devices in a single Storage
-Daemon. Now, Bacula is able to restore from multiple Storage Daemon. For
+Daemon. Now, Bacula is able to restore from multiple Storage Daemons. For
example, if your full backup runs on a Storage Daemon with an autochanger, and
-your incremental jobs use an other Storage Daemon with lots of disks, Bacula
-will switch automatically from a Storage Daemon to an other in the same Restore
+your incremental jobs use another Storage Daemon with lots of disks, Bacula
+will switch automatically from one Storage Daemon to an other within the same Restore
job.
-You need to upgrade your File Daemon to use this feature.
+You must upgrade your File Daemon to version 3.0.3 to use this feature.
This project was funded by Bacula Systems with the help of Equiinet.
-\section{File deduplication using Base jobs}
-
+\section{File Deduplication using Base Jobs}
A base job is sort of like a Full save except that you will want the FileSet to
contain only files that are unlikely to change in the future (i.e. a snapshot
of most of your system after installing it). After the base job has been run,
btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
++++++++++++++++++++++++++++++++++++++++++
btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
-btape.c:406 Volume bytes=3.221 GB. Write rate = 44128.0 KB/s
+btape.c:406 Volume bytes=3.221 GB. Write rate = 44.128 GB/s
...
-btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43531.7 KB/s
+btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 43.531 GKB/s
btape.c:1090 Test with random data, should give the minimum throughput.
btape.c:956 Begin writing 3 files of 3.221 GB with blocks of 129024 bytes.
+++++++++++++++++++++++++++++++++++++++++++
btape.c:604 Wrote 1 EOF to "Drive-0" (/dev/nst0)
-btape.c:406 Volume bytes=3.221 GB. Write rate = 7271.7 KB/s
+btape.c:406 Volume bytes=3.221 GB. Write rate = 7.271 GB/s
+++++++++++++++++++++++++++++++++++++++++++
...
-btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7365.9 KB/s
+btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 GB/s
\end{verbatim}
You can change the block size in the Storage Daemon configuration file.
-\section{Bat new features}
+\section{New {\bf Block Checksum} Device directive}
+You may now turn off the Block Checksum (CRC32) code
+that Bacula uses when writing blocks to a Volume. This is
+done by adding:
+
+\begin{verbatim}
+Block Checksum = no
+\end{verbatim}
+
+doing so can reduce the Storage daemon CPU speed slightly. It
+will also permit Bacula to read a Volume that has corrupted data.
+
+The default is {\bf yes} -- i.e. the checksum is computed on write
+and checked on read.
+
+We do not recommend to turn this off particularly on older tape
+drives or for disk Volumes where doing so may allow corrupted data
+to be undetected.
+
+\section{New Bat Features}
\subsection{Media information view}
-When double-clicking on a volume (on the Media list, in the Autochanger content
-or in the Job information panel), you can access to a detailed overview of your
-volume. (cf \ref{fig:mediainfo}.)
+By double-clicking on a volume (on the Media list, in the Autochanger content
+or in the Job information panel), you can access a detailed overview of your
+Volume. (cf \ref{fig:mediainfo}.)
\begin{figure}[htbp]
\centering
\includegraphics[width=13cm]{\idir bat11.eps}
\subsection{Job information view}
-When double-clicking on a Job record (on the Job run list or in the Media
-information panel), you can access to a detailed overview of your Job. (cf
+By double-clicking on a Job record (on the Job run list or in the Media
+information panel), you can access a detailed overview of your Job. (cf
\ref{fig:jobinfo}.)
\begin{figure}[htbp]
\centering
\subsection{Autochanger content view}
-When double-clicking on a Storage record (on the Storage list panel), you can
-access to a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
+By double-clicking on a Storage record (on the Storage list panel), you can
+access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.)
\begin{figure}[htbp]
\centering
\includegraphics[width=13cm]{\idir bat13.eps}
\section{Full restore from a given JobId}
\index[general]{Restore menu}
-This feature allows selecting a JobId and having Bacula automatically select all
-other jobs that comprise a full backup up to and including the selected JobId.
+This feature allows selecting a single JobId and having Bacula
+automatically select all the other jobs that comprise a full backup up to
+and including the selected JobId.
Assume we start with the following jobs:
\begin{verbatim}
+-------+--------------+---------------------+-------+----------+------------+
\end{verbatim}
-Below is an example of selecting this new feature (which is number 12 in the
+Below is an example of this new feature (which is number 12 in the
menu).
\begin{verbatim}
\index[general]{Source Address}
A feature has been added which allows the administrator to specify the address
-from which the director and file daemons will attempt connections from. This
+from which the Director and File daemons will establish connections. This
may be used to simplify system configuration overhead when working in complex
networks utilizing multi-homing and policy-routing.
}
\end{verbatim}
-Simply adding specific host routes would have an undesirable side-effect: any
+Simply adding specific host routes on the OS
+would have an undesirable side-effect: any
application trying to contact the destination host would be forced to use the
-more specific route, possibly diverting management traffic onto a backup VLAN.
+more specific route possibly diverting management traffic onto a backup VLAN.
Instead of adding host routes for each client connected to a multi-homed backup
server (for example where there are management and backup VLANs), one can
use the new directives to specify a specific source address at the application
\section{Show volume availability when doing restore}
-When doing a restore the restore selection dialog ends by displaying this
+When doing a restore the selection dialog ends by displaying this
screen:
\begin{verbatim}
001762L3 LTO-4 LTO3
001767L3 LTO-4 LTO3
-Volumes marked with ``*'' are online.
+Volumes marked with ``*'' are online (in the autochanger).
\end{verbatim}
-This should help getting large restores through minimizing the time spent
-waiting for operator to drop by and change tapes in the library.
+This should help speed up large restores by minimizing the time spent
+waiting for the operator to discover that he must change tapes in the library.
This project was funded by Bacula Systems.
The \texttt{estimate} command can now use the accurate code to detect changes
and give a better estimation.
-You can set the accurate behavior on command line using
+You can set the accurate behavior on the command line by using
\texttt{accurate=yes/no} or use the Job setting as default value.
\begin{verbatim}
projects / bacula / docs / commitdiff