%%
-\chapter{New Features in 3.0.3}
+\chapter{New Features in 3.1.4 (Development Version}
\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 or early
-2010.
+This chapter presents the new features that are currently under development
+in the 3.1.x versions to be released as Bacula version 3.2.0 sometime in
+late 2009 or early 2010.
+\section{Truncate volume after purge}
+\label{sec:actiononpurge}
-\section{Maximum concurent jobs for Devices}
+The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
+the volume when it is purged. It is useful to prevent disk based volumes from
+consuming too much space.
+
+\begin{verbatim}
+Pool {
+ Name = Default
+ Action On Purge = Truncate
+ ...
+}
+\end{verbatim}
+
+\section{Maximum Concurent Jobs for Devices}
\label{sec:maximumconcurentjobdevice}
-A new Device directive in the Storage Daemon configuration permits to set the
-maximum number of Jobs that can run concurrently on specified Device. This
-directive permits to dispatch jobs on multiple drives, and when this limit is
-reached, the Storage Daemon will start new jobs on any other available
-compatible drive. So it's possible to use the same pool on multiple drives like
-with the broken \textsl{Prefer Mounted Volume} option.
+{\bf Maximum Concurrent Jobs} is a new Device directive in the Storage
+Daemon configuration permits setting the maximum number of Jobs that can
+run concurrently on a specified Device. Using this directive, it is
+possible to have different Jobs using multiple drives, because when the
+Maximum Concurrent Jobs limit is reached, the Storage Daemon will start new
+Jobs on any other available compatible drive. This facilitates writing to
+multiple drives with multiple Jobs that all use the same Pool.
\section{Restore from Multiple Storage Daemons}
\index[general]{Restore}
will switch automatically from one Storage Daemon to an other within the same
Restore job.
-You must upgrade your File Daemon to version 3.0.3 to use this feature.
+You must upgrade your File Daemon to version 3.1.3 or greater to use this feature.
This project was funded by Bacula Systems with the help of Equiinet.
This project was funded by Bacula Systems.
+
+\section{Accurate Fileset Options}
+\label{sec:accuratefileset}
+
+In previous versions, the accurate code used the file creation and
+modification times to determine if a file was modified or not. Now you can specify
+which attributes to use (time, size, checksum, permission, owner, group,
+\dots), similar to the Verify options.
+
+\begin{verbatim}
+FileSet {
+ Name = Full
+ Include = {
+ Options {
+ Accurate = mcs5
+ Verify = pin5
+ }
+ File = /
+ }
+}
+\end{verbatim}
+
+\begin{description}
+\item {\bf i}
+ compare the inodes
+
+\item {\bf p}
+ compare the permission bits
+
+\item {\bf n}
+ compare the number of links
+
+\item {\bf u}
+ compare the user id
+
+\item {\bf g}
+ compare the group id
+
+\item {\bf s}
+ compare the size
+
+\item {\bf a}
+ compare the access time
+
+\item {\bf m}
+ compare the modification time (st\_mtime)
+
+\item {\bf c}
+ compare the change time (st\_ctime)
+
+\item {\bf d}
+ report file size decreases
+
+\item {\bf 5}
+ compare the MD5 signature
+
+\item {\bf 1}
+ compare the SHA1 signature
+\end{description}
+
+\textbf{Important note:} If you decide to use checksum in Accurate jobs,
+the File Daemon will have to read all files even if they normally would not
+be saved. This increases the I/O load, but also the accuracy of the
+deduplication. By default, Bacula will check modification/creation time
+and size.
+
+\section{Tab-completion for Bconsole}
+\label{sec:tabcompletion}
+
+If you build \texttt{bconsole} with readline support, you will be able to use
+the new auto-completion mode. This mode supports all commands, gives help
+inside command, and lists resources when required.
+
\section{Bvfs API}
\label{sec:bvfs}
-To help developers in restore GUI interfaces, we have added new \textsl{dot
- commands} that permit to browse the catalog in a very simple way.
+To help developers of restore GUI interfaces, we have added new \textsl{dot
+ commands} that permit browsing the catalog in a very simple way.
\begin{itemize}
-\item \texttt{.update [jobid=x,y,z]} This command is required to update the
+\item \texttt{.bvfs\_update [jobid=x,y,z]} This command is required to update the
Bvfs cache in the catalog. You need to run it before any access to the Bvfs
layer.
-\item \texttt{.lsdirs jobid=x,y,z path=/path | pathid=101} This command will
- list all directories in the specified \texttt{path} or \texttt{pathid}. Using
- \texttt{pathid} avoids problems with caracters encoding.
-\item \texttt{.lsfiles jobid=x,y,z path=/path | pathid=101} This command will
- list all files in the specified \texttt{path} or \texttt{pathid}. Using
- \texttt{pathid} avoids problems with caracters encoding.
+
+\item \texttt{.bvfs\_lsdirs jobid=x,y,z path=/path | pathid=101} This command
+ will list all directories in the specified \texttt{path} or
+ \texttt{pathid}. Using \texttt{pathid} avoids problems with character
+ encoding of path/filenames.
+
+\item \texttt{.bvfs\_lsfiles jobid=x,y,z path=/path | pathid=101} This command
+ will list all files in the specified \texttt{path} or \texttt{pathid}. Using
+ \texttt{pathid} avoids problems with character encoding.
\end{itemize}
You can use \texttt{limit=xxx} and \texttt{offset=yyy} to limit the amount of
data that will be displayed.
\begin{verbatim}
-* .update jobid=1,2
-* .update
-* .lsdir path=/ jobid=1,2
+* .bvfs_update jobid=1,2
+* .bvfs_update
+* .bvfs_lsdir path=/ jobid=1,2
\end{verbatim}
-\section{Testing your tape drive}
+\section{Testing your Tape Drive}
\label{sec:btapespeed}
To determine the best configuration of your tape drive, you can run the new
-\texttt{speed} command available in \texttt{btape}.
+\texttt{speed} command available in the \texttt{btape} program.
This command can have the following arguments:
\begin{itemize}
You can change the block size in the Storage Daemon configuration file.
-\section{New {\bf Block Checksum} Device directive}
+\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:
Block Checksum = no
\end{verbatim}
-doing so can reduce the Storage daemon CPU speed slightly. It
+doing so can reduce the Storage daemon CPU usage 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
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.
+to go undetected.
\section{New Bat Features}
-\subsection{Media information view}
+\subsection{Media List View}
+
+By clicking on ``Media'', you can see the list of all your volumes. You will be
+able to filter by Pool, Media Type, Location,\dots And sort the result directly
+in the table. The old ``Media'' view is now known as ``Pool''.
+\begin{figure}[htbp]
+ \centering
+ \includegraphics[width=13cm]{\idir bat-mediaview.eps}
+ \label{fig:mediaview}
+\end{figure}
+
+
+\subsection{Media Information View}
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
\label{fig:mediainfo}
\end{figure}
-\subsection{Job information view}
+\subsection{Job Information View}
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
\label{fig:jobinfo}
\end{figure}
-\subsection{Autochanger content view}
+\subsection{Autochanger Content View}
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}.)
\label{fig:achcontent}
\end{figure}
-\chapter{New Features in 3.0.2}
+\section{Console Timeout Option}
+You can now use the -u option of bconsole to set a timeout for each command.
+
+\chapter{New Features in Released Version 3.0.2}
-This chapter presents the new features added to the development 3.0.2
-versions to be released as Bacula version 3.0.2 in july 2009.
+This chapter presents the new features added to the
+Released Bacula Version 3.0.2.
-\section{Full restore from a given JobId}
+\section{Full Restore from a Given JobId}
\index[general]{Restore menu}
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.
+and including the selected date (through JobId).
Assume we start with the following jobs:
\begin{verbatim}
1: List last 20 Jobs run
2: List Jobs where a given File is saved
...
- 12: Select full restore to a specified JobId
+ 12: Select full restore to a specified Job date
13: Cancel
Select item: (1-13): 12
-Enter JobId to restore: 5
+Enter JobId to get the state to restore: 5
+Selecting jobs to build the Full state at 2009-07-15 11:45:45
You have selected the following JobIds: 1,3,5
Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++
projects / bacula / docs / blobdiff