From: Kern Sibbald Date: Sat, 29 Sep 2012 08:55:06 +0000 (+0200) Subject: Pull updated newfeatures chapter X-Git-Tag: Release-5.2.13~14 X-Git-Url: https://git.sur5r.net/?p=bacula%2Fdocs;a=commitdiff_plain;h=37caa268ff7ee65b79484c48c451d9f83c97dac4 Pull updated newfeatures chapter --- diff --git a/docs/manuals/en/main/newfeatures.tex b/docs/manuals/en/main/newfeatures.tex index 1ad2af5a..88f4f8cc 100644 --- a/docs/manuals/en/main/newfeatures.tex +++ b/docs/manuals/en/main/newfeatures.tex @@ -2,11 +2,11 @@ This chapter presents the new features that have been added to the next Community version of Bacula that is not yet released. -\chapter{New Features in 5.2.2} +\section{New Features in 5.2.2} This chapter presents the new features that have been added to the current Community version of Bacula that is now released. -\section{Additions to RunScript variables} +\subsection{Additions to RunScript variables} You can have access to Director name using \%D in your runscript command. @@ -14,7 +14,7 @@ command. RunAfterJob = "/bin/echo Director=%D \end{verbatim} -\chapter{New Features in 5.2.1} +\section{New Features in 5.2.1} This chapter presents the new features were added in the Community release version 5.2.1. @@ -22,9 +22,9 @@ There are additional features (plugins) available in the Enterprise version that are described in another chapter. A subscription to Bacula Systems is required for the Enterprise version. -\section{LZO Compression} +\subsection{LZO Compression} -LZO compression was added in the Unix File Daemon. From the user point of view, +LZO compression has been to the File daemon. From the user's point of view, it works like the GZIP compression (just replace {\bf compression=GZIP} with {\bf compression=LZO}). @@ -37,12 +37,12 @@ Include { } \end{verbatim} -LZO provides much faster compression and decompression speed but lower +LZO provides a much faster compression and decompression speed but lower compression ratio than GZIP. It is a good option when you backup to disk. For -tape, the built-in compression may be a better option. +tape, the hardware compression is almost always a better option. -LZO is a good altenative for GZIP1 when you don't want to slow down your -backup. On a modern CPU it should be able to run almost as fast as: +LZO is a good alternative for GZIP1 when you don't want to slow down your +backup. With a modern CPU it should be able to run almost as fast as: \begin{itemize} \item your client can read data from disk. Unless you have very fast disks like @@ -51,12 +51,12 @@ backup. On a modern CPU it should be able to run almost as fast as: a 1Gb/s link. \end{itemize} -Note that bacula only use one compression level LZO1X-1. +Note, Bacula uses compression level LZO1X-1. \medskip The code for this feature was contributed by Laurent Papier. -\section{New Tray Monitor} +\subsection{New Tray Monitor} Since the old integrated Windows tray monitor doesn't work with recent Windows versions, we have written a new Qt Tray Monitor that is available @@ -101,7 +101,7 @@ Console { This project was funded by Bacula Systems and is available with Bacula the Enterprise Edition and the Community Edition. -\section{Purge Migration Job} +\subsection{Purge Migration Job} The new {\bf Purge Migration Job} directive may be added to the Migration Job definition in the Director's configuration file. When it is enabled @@ -128,10 +128,10 @@ Job { \medskip -This project was submited by Dunlap Blake; testing and documentation was funded +This project was submitted by Dunlap Blake; testing and documentation was funded by Bacula Systems. -\section{Changes in Bvfs (Bacula Virtual FileSystem)} +\subsection{Changes in Bvfs (Bacula Virtual FileSystem)} Bat has now a bRestore panel that uses Bvfs to display files and directories. @@ -148,7 +148,7 @@ the Bvfs module works correctly with BaseJobs, Copy and Migration jobs. \medskip This project was funded by Bacula Systems. -\subsection*{General notes} +\subsubsection*{General notes} \begin{itemize} \item All fields are separated by a tab @@ -159,13 +159,13 @@ This project was funded by Bacula Systems. can contribute new faster SQL queries we will be happy, else don't complain about speed. \item The cache creation is dependent of the number of directories. As Bvfs - shares information accross jobs, the first creation can be slow + shares information across jobs, the first creation can be slow \item All fields are separated by a tab -\item Due to potential encoding problem, it's advised to allways use pathid in +\item Due to potential encoding problem, it's advised to always use pathid in queries. \end{itemize} -\subsection*{Get dependent jobs from a given JobId} +\subsubsection*{Get dependent jobs from a given JobId} Bvfs allows you to query the catalog against any combination of jobs. You can combine all Jobs and all FileSet for a Client in a single session. @@ -190,7 +190,7 @@ compute a complete restore of the system. With the \texttt{all} option, the Director will use all defined FileSet for this client. -\subsection*{Generating Bvfs cache} +\subsubsection*{Generating Bvfs cache} The \texttt{.bvfs\_update} command computes the directory cache for jobs specified in argument, or for all jobs if unspecified. @@ -206,7 +206,7 @@ Example: You can run the cache update process in a RunScript after the catalog backup. -\subsection*{Get all versions of a specific file} +\subsubsection*{Get all versions of a specific file} Bvfs allows you to find all versions of a specific file for a given Client with the \texttt{.bvfs\_version} command. To avoid problems with encoding, this @@ -227,7 +227,7 @@ Example: 1 47 52 12 gD HRid IGk D Po Po A P BAA I A /uPgWaxMgKZlnMti7LChyA Vol1 1 \end{verbatim} -\subsection*{List directories} +\subsubsection*{List directories} Bvfs allows you to list directories in a specific path. \begin{verbatim} @@ -257,7 +257,7 @@ In this example, to list directories present in \texttt{regress/}, you can use 2 0 0 0 A A A A A A A A A A A A A A tmp/ \end{verbatim} -\subsection*{List files} +\subsubsection*{List files} Bvfs allows you to list files in a specific path. \begin{verbatim} @@ -289,7 +289,7 @@ In this example, to list files present in \texttt{regress/}, you can use 1 46 56 12 gD HRie IGk BAA I BMqe/K BMqcPE BMqe+3 D ficheriro2.txt \end{verbatim} -\subsection*{Restore set of files} +\subsubsection*{Restore set of files} Bvfs allows you to create a SQL table that contains files that you want to restore. This table can be provided to a restore command with the file option. @@ -303,7 +303,7 @@ restore file=?b2num ... To include a directory (with \texttt{dirid}), Bvfs needs to run a query to select all files. This query could be time consuming. -\texttt{hardlink} list is always composed of a serie of two numbers (jobid, +\texttt{hardlink} list is always composed of a series of two numbers (jobid, fileindex). This information can be found in the LinkFI field of the LStat packet. @@ -318,7 +318,7 @@ Example: OK \end{verbatim} -\subsection*{Cleanup after Restore} +\subsubsection*{Cleanup after Restore} To drop the table used by the restore command, you can use the \texttt{.bvfs\_cleanup} command. @@ -327,7 +327,7 @@ To drop the table used by the restore command, you can use the .bvfs_cleanup path=b20001 \end{verbatim} -\subsection*{Clearing the BVFS Cache} +\subsubsection*{Clearing the BVFS Cache} To clear the BVFS cache, you can use the \texttt{.bvfs\_clear\_cache} command. @@ -336,7 +336,7 @@ To clear the BVFS cache, you can use the \texttt{.bvfs\_clear\_cache} command. OK \end{verbatim} -\section{Changes in the Pruning Algorithm} +\subsection{Changes in the Pruning Algorithm} We rewrote the job pruning algorithm in this version. Previously, in some users reported that the pruning process at the end of jobs was very long. It should @@ -360,7 +360,7 @@ and will prune only JobId 2 and 3. Job and the \texttt{prune jobs} Bconsole command. If a volume expires after the \texttt{VolumeRetention} period, important jobs can be pruned. -\section{Ability to Verify any specified Job} +\subsection{Ability to Verify any specified Job} You now have the ability to tell Bacula which Job should verify instead of automatically verify just the last one. @@ -388,7 +388,7 @@ OK to run? (yes/mod/no): This project was funded by Bacula Systems and is available with Bacula Enterprise Edition and Community Edition. -\section{Additions to RunScript variables} +\subsection{Additions to RunScript variables} You can have access to JobBytes and JobFiles using \%b and \%F in your runscript command. The Client address is now available through \%h. @@ -396,7 +396,7 @@ command. The Client address is now available through \%h. RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h" \end{verbatim} -%\section{Changes in drivetype.exe} +%\subsection{Changes in drivetype.exe} % %Now the \texttt{drivetype.exe} program allows you to list all local hard %drives. It can help to build dynamic FileSet on Windows. @@ -406,11 +406,11 @@ RunAfterJob = "/bin/echo Job=%j JobBytes=%b JobFiles=%F ClientAddress=%h" %\end{verbatim} % -\section{Additions to the Plugin API} +\subsection{Additions to the Plugin API} The bfuncs structure has been extended to include a number of new entrypoints. -\subsection{bfuncs} +\subsubsection{bfuncs} The bFuncs structure defines the callback entry points within Bacula that the plugin can use register events, get Bacula values, set Bacula values, and send messages to the Job output or debug output. @@ -452,6 +452,12 @@ typedef struct s_baculaFuncs { or files matched by the rather simple fnmatch mechanism. See below for information on doing wild-card and regex excludes. +\item [NewPreInclude] can be called to create a new Include block. This + block will be added after the current defined Include block. This + function can be called multiple times, but each time, it will create + a new Include section (not normally needed). This function should + be called only if you want to add an entirely new Include block. + \item [NewInclude] can be called to create a new Include block. This block will be added before any user defined Include blocks. This function can be called multiple times, but each time, it will create @@ -511,7 +517,7 @@ typedef struct s_baculaFuncs { \end{description} \item [AddRegex] adds a regex expression to the current Options block. - The fillowing options are permitted: + The following options are permitted: \begin{description} \item [ ] (a blank) regex applies to whole path and filename. \item [F] regex applies only to the filename (directory or path stripped). @@ -519,7 +525,7 @@ typedef struct s_baculaFuncs { \end{description} \item [AddWild] adds a wildcard expression to the current Options block. - The fillowing options are permitted: + The following options are permitted: \begin{description} \item [ ] (a blank) regex applies to whole path and filename. \item [F] regex applies only to the filename (directory or path stripped). @@ -535,7 +541,7 @@ typedef struct s_baculaFuncs { \end{description} -\subsection{Bacula events} +\subsubsection{Bacula events} The list of events has been extended to include: \begin{verbatim} @@ -569,7 +575,7 @@ typedef enum { \begin{description} \item [bEventCancelCommand] is called whenever the currently - running Job is cancelled */ + running Job is canceled */ \item [bEventVssBackupAddComponents] @@ -580,7 +586,7 @@ typedef enum { for this purpose. \end{description} -\section{ACL enhancements} +\subsection{ACL enhancements} The following enhancements are made to the Bacula Filed with regards to Access Control Lists (ACLs) @@ -594,7 +600,7 @@ Access Control Lists (ACLs) \item Fix for acl storage on OSX \item Cleanup of configure checks for ACL detection, now configure only tests for a certain interface type based on the operating system - this should give less false possitives on detection. Also when acls + this should give less false positives on detection. Also when ACLs are detected no other acl checks are performed anymore. \end{itemize} @@ -602,7 +608,7 @@ Access Control Lists (ACLs) This project was funded by Planets Communications B.V. and ELM Consultancy B.V. and is available with Bacula Enterprise Edition and Community Edition. -\section{XATTR enhancements} +\subsection{XATTR enhancements} The following enhancements are made to the Bacula Filed with regards to Extended Attributes (XATTRs) @@ -617,7 +623,7 @@ Extended Attributes (XATTRs) debug. \item Cleanup of configure checks for XATTR detection, now configure only tests for a certain interface type based on the operating system - this should give less false possitives on detection. Also when xattrs + this should give less false positives on detection. Also when xattrs are detected no other xattr checks are performed anymore. \end{itemize} @@ -625,7 +631,7 @@ Extended Attributes (XATTRs) This project was funded by Planets Communications B.V. and ELM Consultancy B.V. and is available with Bacula Enterprise Edition and Community Edition. -\section{Class Based Database Backend Drivers} +\subsection{Class Based Database Backend Drivers} The main Bacula Director code is independent of the SQL backend in version 5.2.0 and greater. This means that the Bacula Director can be @@ -689,8 +695,8 @@ one it will be lost. All current database backend drivers for catalog information are rewritten to use a set of multi inherited C++ classes which abstract the specific database specific internals and make sure we have a more stable generic -interface with the rest of sql code. From now on there is a strict -boundery between the SQL code and the low-level database functions. This +interface with the rest of SQL code. From now on there is a strict +boundary between the SQL code and the low-level database functions. This new interface should also make it easier to add a new backend for a currently unsupported database. As part of the rewrite the SQLite 2 code was removed (e.g. only SQLite 3 is now supported). An extra bonus of the @@ -710,7 +716,7 @@ This project was implemented by Planets Communications B.V. and ELM Consultancy B.V. and Bacula Systems and is available with both the Bacula Enterprise Edition and the Community Edition. -\section{Hash List Enhancements} +\subsection{Hash List Enhancements} The htable hash table class has been extended with extra hash functions for handling next to char pointer hashes also 32 bits and 64 bits hash keys. @@ -733,28 +739,28 @@ Community Edition. %% -\chapter{Release Version 5.0.3} +\section{Release Version 5.0.3} There are no new features in version 5.0.2. This version simply fixes a -number of bugs found in version 5.0.1 during the onging development +number of bugs found in version 5.0.1 during the ongoing development process. -\chapter{Release Version 5.0.2} +\section{Release Version 5.0.2} There are no new features in version 5.0.2. This version simply fixes a -number of bugs found in version 5.0.1 during the onging development +number of bugs found in version 5.0.1 during the ongoing development process. %% %% -\chapter{New Features in 5.0.1} +\section{New Features in 5.0.1} This chapter presents the new features that are in the released Bacula version 5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during -the onging development process. +the ongoing development process. -\section{Truncate Volume after Purge} +\subsection{Truncate Volume after Purge} \label{sec:actiononpurge} The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate @@ -803,12 +809,12 @@ Job { \textbf{Important note}: This feature doesn't work as expected in version 5.0.0. Please do not use it before version 5.0.1. -\section{Allow Higher Duplicates} +\subsection{Allow Higher Duplicates} This directive did not work correctly and has been depreciated (disabled) in version 5.0.1. Please remove it from your bacula-dir.conf -file as it will be removed in a future rlease. +file as it will be removed in a future release. -\section{Cancel Lower Level Duplicates} +\subsection{Cancel Lower Level Duplicates} This directive was added in Bacula version 5.0.1. It compares the level of a new backup job to old jobs of the same name, if any, and will kill the job which has a lower level than the other one. @@ -816,9 +822,9 @@ If the levels are the same (i.e. both are Full backups), then nothing is done and the other Cancel XXX Duplicate directives will be examined. -\chapter{New Features in 5.0.0} +\section{New Features in 5.0.0} -\section{Maximum Concurrent Jobs for Devices} +\subsection{Maximum Concurrent Jobs for Devices} \label{sec:maximumconcurrentjobdevice} {\bf Maximum Concurrent Jobs} is a new Device directive in the Storage @@ -831,7 +837,7 @@ multiple drives with multiple Jobs that all use the same Pool. This project was funded by Bacula Systems. -\section{Restore from Multiple Storage Daemons} +\subsection{Restore from Multiple Storage Daemons} \index[general]{Restore} Previously, you were able to restore from multiple devices in a single Storage @@ -846,7 +852,7 @@ feature. This project was funded by Bacula Systems with the help of Equiinet. -\section{File Deduplication using Base Jobs} +\subsection{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, @@ -868,7 +874,7 @@ See the \ilink{Base Job Chapter}{basejobs} for more information. This project was funded by Bacula Systems. -\section{AllowCompression = \lt{}yes\vb{}no\gt{}} +\subsection{AllowCompression = \lt{}yes\vb{}no\gt{}} \index[dir]{AllowCompression} This new directive may be added to Storage resource within the Director's @@ -897,7 +903,7 @@ daemon and possibly speed up tape backups. This project was funded by Collaborative Fusion, Inc. -\section{Accurate Fileset Options} +\subsection{Accurate Fileset Options} \label{sec:accuratefileset} In previous versions, the accurate code used the file creation and modification @@ -941,7 +947,7 @@ and size. This project was funded by Bacula Systems. -\section{Tab-completion for Bconsole} +\subsection{Tab-completion for Bconsole} \label{sec:tabcompletion} If you build \texttt{bconsole} with readline support, you will be able to use @@ -959,7 +965,7 @@ The new bconsole won't be able to tab-complete with older directors. This project was funded by Bacula Systems. -\section{Pool File and Job Retention} +\subsection{Pool File and Job Retention} \label{sec:poolfilejobretention} We added two new Pool directives, \texttt{FileRetention} and @@ -969,15 +975,15 @@ example, you can decide to increase Retention times for Archive or OffSite Pool. It seems obvious to us, but apparently not to some users, that given the definition above that the Pool File and Job Retention periods is a global -override for the normal Client based prunning, which means that when the -Job is prunned, the prunning will apply globally to that particular Job. +override for the normal Client based pruning, which means that when the +Job is pruned, the pruning will apply globally to that particular Job. Currently, there is a bug in the implementation that causes any Pool retention periods specified to apply to {\bf all} Pools for that particular Client. Thus we suggest that you avoid using these two directives until this implementation problem is corrected. -\section{Read-only File Daemon using capabilities} +\subsection{Read-only File Daemon using capabilities} \label{sec:fdreadonly} This feature implements support of keeping \textbf{ReadAll} capabilities after UID/GID switch, this allows FD to keep root read but drop write permission. @@ -991,7 +997,7 @@ root@localhost:~# bacula-fd -k -u nobody -g nobody The code for this feature was contributed by our friends at AltLinux. -\section{Bvfs API} +\subsection{Bvfs API} \label{sec:bvfs} To help developers of restore GUI interfaces, we have added new \textsl{dot @@ -1023,7 +1029,7 @@ data that will be displayed. This project was funded by Bacula Systems. -\section{Testing your Tape Drive} +\subsection{Testing your Tape Drive} \label{sec:btapespeed} To determine the best configuration of your tape drive, you can run the new @@ -1067,11 +1073,11 @@ btape.c:383 Total Volume bytes=9.664 GB. Total Write rate = 7.365 MB/s When using compression, the random test will give your the minimum throughput of your drive . The test using constant string will give you the maximum speed -of your hardware chain. (cpu, memory, scsi card, cable, drive, tape). +of your hardware chain. (CPU, memory, SCSI card, cable, drive, tape). You can change the block size in the Storage Daemon configuration file. -\section{New {\bf Block Checksum} Device Directive} +\subsection{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: @@ -1090,11 +1096,11 @@ 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 go undetected. -\section{New Bat Features} +\subsection{New Bat Features} Those new features were funded by Bacula Systems. -\subsection{Media List View} +\subsubsection{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 @@ -1106,7 +1112,7 @@ in the table. The old ``Media'' view is now known as ``Pool''. \end{figure} -\subsection{Media Information View} +\subsubsection{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 @@ -1118,7 +1124,7 @@ Volume. (cf \ref{fig:mediainfo}.) \label{fig:mediainfo} \end{figure} -\subsection{Job Information View} +\subsubsection{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 @@ -1130,7 +1136,7 @@ information panel), you can access a detailed overview of your Job. (cf \label{fig:jobinfo} \end{figure} -\subsection{Autochanger Content View} +\subsubsection{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}.) @@ -1144,15 +1150,15 @@ access a detailed overview of your Autochanger. (cf \ref{fig:jobinfo}.) To use this feature, you need to use the latest mtx-changer script version. (With new \texttt{listall} and \texttt{transfer} commands) -\section{Bat on Windows} +\subsection{Bat on Windows} We have ported {\bf bat} to Windows and it is now installed by default when the installer is run. It works quite well on Win32, but has not had a lot of testing there, so your -feedback would be welcome. Unfortunately, eventhough it is +feedback would be welcome. Unfortunately, even though it is installed by default, it does not yet work on 64 bit Windows operating systems. -\section{New Win32 Installer} +\subsection{New Win32 Installer} The Win32 installer has been modified in several very important ways. \begin{itemize} @@ -1177,7 +1183,7 @@ they have not been ported to 64 bits), or you can contact Bacula Systems about this. \end{itemize} -\section{Win64 Installer} +\subsection{Win64 Installer} We have corrected a number of problems that required manual editing of the conf files. In most cases, it should now install and work. {\bf bat} is by default installed in @@ -1185,7 +1191,7 @@ install and work. {\bf bat} is by default installed in {\bf c:/Program Files/Bacula} as is the case with the 32 bit Windows installer. -\section{Linux Bare Metal Recovery USB Key} +\subsection{Linux Bare Metal Recovery USB Key} We have made a number of significant improvements in the Bare Metal Recovery USB key. Please see the README files it the {\bf rescue} release for more details. @@ -1195,12 +1201,12 @@ metal recovery, but it will take some time to develop it (best estimate 3Q2010 or 4Q2010) -\section{bconsole Timeout Option} +\subsection{bconsole Timeout Option} You can now use the -u option of {\bf bconsole} to set a timeout in seconds for commands. This is useful with GUI programs that use {\bf bconsole} to interface to the Director. -\section{Important Changes} +\subsection{Important Changes} \label{sec:importantchanges} \begin{itemize} @@ -1210,12 +1216,12 @@ to interface to the Director. \item The \texttt{Device Poll Interval} is now 5 minutes. (previously did not poll by default). \item Virtually all the features of {\bf mtx-changer} have - now been parameterized, which allows you to configure + now been parametrized, which allows you to configure mtx-changer without changing it. There is a new configuration file {\bf mtx-changer.conf} that contains variables that you can set to configure mtx-changer. This configuration file will not be overwritten during upgrades. We encourage you to submit any changes - that are made to mtx-changer and to parameterize it all in + that are made to mtx-changer and to parametrize it all in mtx-changer.conf so that all configuration will be done by changing only mtx-changer.conf. \item The new \texttt{mtx-changer} script has two new options, \texttt{listall} @@ -1236,7 +1242,7 @@ to interface to the Director. Note that the Truncate Volume after purge feature doesn't work as expected in 5.0.0 version. Please, don't use it before version 5.0.1. -\subsection{Custom Catalog queries} +\subsubsection{Custom Catalog queries} If you wish to add specialized commands that list the contents of the catalog, you can do so by adding them to the \texttt{query.sql} file. This @@ -1244,7 +1250,7 @@ you can do so by adding them to the \texttt{query.sql} file. This \texttt{examples/sample-query.sql} has an a number of sample commands you might find useful. -\subsection{Deprecated parts} +\subsubsection{Deprecated parts} The following items have been \textbf{deprecated} for a long time, and are now removed from the code. @@ -1253,7 +1259,7 @@ removed from the code. \item Support for SQLite 2 \end{itemize} -\section{Misc Changes} +\subsection{Misc Changes} \label{sec:miscchanges} \begin{itemize} @@ -1276,15 +1282,15 @@ removed from the code. \chapter{Released Version 3.0.3 and 3.0.3a} There are no new features in version 3.0.3. This version simply fixes a -number of bugs found in version 3.0.2 during the onging development +number of bugs found in version 3.0.2 during the ongoing development process. -\chapter{New Features in Released Version 3.0.2} +\section{New Features in Released Version 3.0.2} This chapter presents the new features added to the Released Bacula Version 3.0.2. -\section{Full Restore from a Given JobId} +\subsection{Full Restore from a Given JobId} \index[general]{Restore menu} This feature allows selecting a single JobId and having Bacula @@ -1326,7 +1332,7 @@ Building directory tree for JobId(s) 1,3,5 ... +++++++++++++++++++ This project was funded by Bacula Systems. -\section{Source Address} +\subsection{Source Address} \index[general]{Source Address} A feature has been added which allows the administrator to specify the address @@ -1361,7 +1367,7 @@ from, while system services listen and act from the unique interface addresses. This project was funded by Collaborative Fusion, Inc. -\section{Show volume availability when doing restore} +\subsection{Show volume availability when doing restore} When doing a restore the selection dialog ends by displaying this screen: @@ -1388,7 +1394,7 @@ waiting for the operator to discover that he must change tapes in the library. This project was funded by Bacula Systems. -\section{Accurate estimate command} +\subsection{Accurate estimate command} The \texttt{estimate} command can now use the accurate code to detect changes and give a better estimation. @@ -1402,25 +1408,25 @@ You can set the accurate behavior on the command line by using This project was funded by Bacula Systems. -\chapter{New Features in 3.0.0} +\section{New Features in 3.0.0} \label{NewFeaturesChapter} \index[general]{New Features} This chapter presents the new features added to the development 2.5.x versions to be released as Bacula version 3.0.0 sometime in April 2009. -\section{Accurate Backup} +\subsection{Accurate Backup} \index[general]{Accurate Backup} As with most other backup programs, by default Bacula decides what files to -backup for Incremental and Differental backup by comparing the change +backup for Incremental and Differential backup by comparing the change (st\_ctime) and modification (st\_mtime) times of the file to the time the last backup completed. If one of those two times is later than the last backup time, then the file will be backed up. This does not, however, permit tracking what files have been deleted and will miss any file with an old time that may have been restored to or moved onto the client filesystem. -\subsection{Accurate = \lt{}yes\vb{}no\gt{}} +\subsubsection{Accurate = \lt{}yes\vb{}no\gt{}} If the {\bf Accurate = \lt{}yes\vb{}no\gt{}} directive is enabled (default no) in the Job resource, the job will be run as an Accurate Job. For a {\bf Full} backup, there is no difference, but for {\bf Differential} and {\bf @@ -1447,7 +1453,7 @@ This project was funded by Bacula Systems. -\section{Copy Jobs} +\subsection{Copy Jobs} \index[general]{Copy Jobs} A new {\bf Copy} job type 'C' has been implemented. It is similar to the @@ -1590,7 +1596,7 @@ The command \texttt{list copies [jobid=x,y,z]} lists copies for a given +-------+------------------------------------+-----------+------------------+ \end{verbatim} -\section{ACL Updates} +\subsection{ACL Updates} \index[general]{ACL Updates} The whole ACL code had been overhauled and in this version each platforms has different streams for each type of acl available on such an platform. As ACLs @@ -1599,7 +1605,7 @@ some use an other draft or a completely different format) we currently only allow certain platform specific ACL streams to be decoded and restored on the same platform that they were created on. The old code allowed to restore ACL cross platform but the comments already mention that not being to wise. For -backward compatability the new code will accept the two old ACL streams and +backward compatibility the new code will accept the two old ACL streams and handle those with the platform specific handler. But for all new backups it will save the ACLs using the new streams. @@ -1651,20 +1657,20 @@ part of the stream numbers): \end{itemize} In future versions we might support conversion functions from one type of acl -into an other for types that are either the same or easily convertable. For now -the streams are seperate and restoring them on a platform that doesn't +into an other for types that are either the same or easily convertible. For now +the streams are separate and restoring them on a platform that doesn't recognize them will give you a warning. -\section{Extended Attributes} +\subsection{Extended Attributes} \index[general]{Extended Attributes} Something that was on the project list for some time is now implemented for platforms that support a similar kind of interface. Its the support for backup and restore of so called extended attributes. As extended attributes are so -platform specific these attributes are saved in seperate streams for each +platform specific these attributes are saved in separate streams for each platform. Restores of the extended attributes can only be performed on the same platform the backup was done. There is support for all types of extended attributes, but restoring from one type of filesystem onto an other type of -filesystem on the same platform may lead to supprises. As extended attributes +filesystem on the same platform may lead to surprises. As extended attributes can contain any type of data they are stored as a series of so called value-pairs. This data must be seen as mostly binary and is stored as such. As security labels from selinux are also extended attributes this option also @@ -1679,9 +1685,9 @@ Currently the following platforms support extended attributes: \item {\bf NetBSD} \end{itemize} -On linux acls are also extended attributes, as such when you enable ACLs on a +On Linux acls are also extended attributes, as such when you enable ACLs on a Linux platform it will NOT save the same data twice e.g. it will save the ACLs -and not the same exteneded attribute. +and not the same extended attribute. To enable the backup of extended attributes please add the following to your fileset definition. @@ -1698,7 +1704,7 @@ fileset definition. } \end{verbatim} -\section{Shared objects} +\subsection{Shared objects} \index[general]{Shared objects} A default build of Bacula will now create the libraries as shared objects (.so) rather than static libraries as was previously the case. @@ -1749,7 +1755,7 @@ libtool on the configure command line with: \end{verbatim} -\section{Building Static versions of Bacula} +\subsection{Building Static versions of Bacula} \index[general]{Static linking} In order to build static versions of Bacula, in addition to configuration options that were needed you now must @@ -1760,7 +1766,7 @@ also add --disable-libtool. Example \end{verbatim} -\section{Virtual Backup (Vbackup)} +\subsection{Virtual Backup (Vbackup)} \index[general]{Virtual Backup} \index[general]{Vbackup} @@ -1886,7 +1892,7 @@ Full was actually run. -\section{Catalog Format} +\subsection{Catalog Format} \index[general]{Catalog Format} Bacula 3.0 comes with some changes to the catalog format. The upgrade operation will convert the FileId field of the File table from 32 bits (max 4 @@ -1898,7 +1904,7 @@ minutes to upgrade on a normal machine. Please don't forget to make a valid backup of your database before executing the upgrade script. See the ReleaseNotes for additional details. -\section{64 bit Windows Client} +\subsection{64 bit Windows Client} \index[general]{Win64 Client} Unfortunately, Microsoft's implementation of Volume Shadown Copy (VSS) on their 64 bit OS versions is not compatible with a 32 bit Bacula Client. @@ -1943,7 +1949,7 @@ Compared to the Win32 Bacula Client, the 64 bit release contains a few differenc This project was funded by Bacula Systems. -\section{Duplicate Job Control} +\subsection{Duplicate Job Control} \index[general]{Duplicate Jobs} The new version of Bacula provides four new directives that give additional control over what Bacula does if duplicate jobs @@ -1957,7 +1963,7 @@ are specified in the Job resource. They are: -\subsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}} +\subsubsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}} \index[general]{Allow Duplicate Jobs} If this directive is set to {\bf yes}, duplicate jobs will be run. If the directive is set to {\bf no} (default) then only one job of a given name @@ -1966,22 +1972,22 @@ They are: If {\bf Allow Duplicate Jobs} is set to {\bf no} and two jobs are present and none of the three directives given below permit - cancelling a job, then the current job (the second one started) - will be cancelled. + Canceling a job, then the current job (the second one started) + will be canceled. -\subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}} +\subsubsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}} \index[general]{Allow Higher Duplicates} This directive was in version 5.0.0, but does not work as expected. If used, it should always be set to no. In later versions of Bacula the directive is disabled (disregarded). -\subsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}} +\subsubsection{Cancel Running Duplicates = \lt{}yes\vb{}no\gt{}} \index[general]{Cancel Running Duplicates} If {\bf Allow Duplicate Jobs} is set to {\bf no} and if this directive is set to {\bf yes} any job that is already running will be canceled. The default is {\bf no}. -\subsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}} +\subsubsection{Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}} \index[general]{Cancel Queued Duplicates} If {\bf Allow Duplicate Jobs} is set to {\bf no} and if this directive is set to {\bf yes} any job that is @@ -1989,7 +1995,7 @@ They are: The default is {\bf no}. -\section{TLS Authentication} +\subsection{TLS Authentication} \index[general]{TLS Authentication} In Bacula version 2.5.x and later, in addition to the normal Bacula CRAM-MD5 authentication that is used to authenticate each Bacula @@ -2002,7 +2008,7 @@ specify all the TLS directives normally used to enable communications encryption (TLS Enable, TLS Verify Peer, TLS Certificate, ...) and a new directive: -\subsection{TLS Authenticate = yes} +\subsubsection{TLS Authenticate = yes} \begin{verbatim} TLS Authenticate = yes \end{verbatim} @@ -2018,14 +2024,14 @@ the two Bacula daemons will be done without encryption. If you want to encrypt communications data, use the normal TLS directives but do not turn on {\bf TLS Authenticate}. -\section{bextract non-portable Win32 data} +\subsection{bextract non-portable Win32 data} \index[general]{bextract handles Win32 non-portable data} {\bf bextract} has been enhanced to be able to restore non-portable Win32 data to any OS. Previous versions were unable to restore non-portable Win32 data to machines that did not have the Win32 BackupRead and BackupWrite API calls. -\section{State File updated at Job Termination} +\subsection{State File updated at Job Termination} \index[general]{State File} In previous versions of Bacula, the state file, which provides a summary of previous jobs run in the {\bf status} command output was @@ -2033,7 +2039,7 @@ updated only when Bacula terminated, thus if the daemon crashed, the state file might not contain all the run data. This version of the Bacula daemons updates the state file on each job termination. -\section{MaxFullInterval = \lt{}time-interval\gt{}} +\subsection{MaxFullInterval = \lt{}time-interval\gt{}} \index[general]{MaxFullInterval} The new Job resource directive {\bf Max Full Interval = \lt{}time-interval\gt{}} can be used to specify the maximum time interval between {\bf Full} backup @@ -2042,7 +2048,7 @@ greater than the specified interval, and the job would normally be an {\bf Incremental} or {\bf Differential}, it will be automatically upgraded to a {\bf Full} backup. -\section{MaxDiffInterval = \lt{}time-interval\gt{}} +\subsection{MaxDiffInterval = \lt{}time-interval\gt{}} \index[general]{MaxDiffInterval} The new Job resource directive {\bf Max Diff Interval = \lt{}time-interval\gt{}} can be used to specify the maximum time interval between {\bf Differential} backup @@ -2051,7 +2057,7 @@ greater than the specified interval, and the job would normally be an {\bf Incremental}, it will be automatically upgraded to a {\bf Differential} backup. -\section{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}} +\subsection{Honor No Dump Flag = \lt{}yes\vb{}no\gt{}} \index[general]{MaxDiffInterval} On FreeBSD systems, each file has a {\bf no dump flag} that can be set by the user, and when it is set it is an indication to backup programs @@ -2066,7 +2072,7 @@ obey this flag. The new directive is: The default value is {\bf no}. -\section{Exclude Dir Containing = \lt{}filename-string\gt{}} +\subsection{Exclude Dir Containing = \lt{}filename-string\gt{}} \index[general]{IgnoreDir} The {\bf ExcludeDirContaining = \lt{}filename\gt{}} is a new directive that can be added to the Include section of the FileSet resource. If the specified @@ -2110,7 +2116,7 @@ applies to the two directories in question and any children (be they files, directories, etc). -\section{Bacula Plugins} +\subsection{Bacula Plugins} \index[general]{Plugin} Support for shared object plugins has been implemented in the Linux, Unix and Win32 File daemons. The API will be documented separately in @@ -2121,7 +2127,7 @@ get control to backup and restore a file. Plugins are also planned (partially implemented) in the Director and the Storage daemon. -\subsection{Plugin Directory} +\subsubsection{Plugin Directory} \index[general]{Plugin Directory} Each daemon (DIR, FD, SD) has a new {\bf Plugin Directory} directive that may be added to the daemon definition resource. The directory takes a quoted @@ -2130,10 +2136,10 @@ find the Bacula plugins. If this directive is not specified, Bacula will not load any plugins. Since each plugin has a distinctive name, all the daemons can share the same plugin directory. -\subsection{Plugin Options} +\subsubsection{Plugin Options} \index[general]{Plugin Options} The {\bf Plugin Options} directive takes a quoted string -arguement (after the equal sign) and may be specified in the +argument (after the equal sign) and may be specified in the Job resource. The options specified will be passed to all plugins when they are run. This each plugin must know what it is looking for. The value defined in the Job resource can be modified @@ -2144,7 +2150,7 @@ Note: this directive may be specified, and there is code to modify the string in the run command, but the plugin options are not yet passed to the plugin (i.e. not fully implemented). -\subsection{Plugin Options ACL} +\subsubsection{Plugin Options ACL} \index[general]{Plugin Options ACL} The {\bf Plugin Options ACL} directive may be specified in the Director's Console resource. It functions as all the other ACL commands @@ -2153,7 +2159,7 @@ do by permitting users running restricted consoles to specify a definition. Without this directive restricted consoles may not modify the Plugin Options. -\subsection{Plugin = \lt{}plugin-command-string\gt{}} +\subsubsection{Plugin = \lt{}plugin-command-string\gt{}} \index[general]{Plugin} The {\bf Plugin} directive is specified in the Include section of a FileSet resource where you put your {\bf File = xxx} directives. @@ -2184,7 +2190,7 @@ rest of the string as he wishes. Please see the next section for information about the {\bf bpipe} Bacula plugin. -\section{The bpipe Plugin} +\subsection{The bpipe Plugin} \index[general]{The bpipe Plugin} The {\bf bpipe} plugin is provided in the directory src/plugins/fd/bpipe-fd.c of the Bacula source distribution. When the plugin is compiled and linking into @@ -2267,16 +2273,16 @@ By using different command lines to {\bf bpipe}, you can backup any kind of data (ASCII or binary) depending on the program called. -\section{Microsoft Exchange Server 2003/2007 Plugin} +\subsection{Microsoft Exchange Server 2003/2007 Plugin} \index[general]{Microsoft Exchange Server 2003/2007 Plugin} -\subsection{Background} +\subsubsection{Background} The Exchange plugin was made possible by a funded development project between Equiinet Ltd -- www.equiinet.com (many thanks) and Bacula Systems. The code for the plugin was written by James Harper, and the Bacula core code by Kern Sibbald. All the code for this funded development has become part of the Bacula project. Thanks to everyone who made it happen. -\subsection{Concepts} +\subsubsection{Concepts} Although it is possible to backup Exchange using Bacula VSS the Exchange plugin adds a good deal of functionality, because while Bacula VSS completes a full backup (snapshot) of Exchange, it does @@ -2303,7 +2309,7 @@ of entire storage groups or individual databases. Backing up and restoring at the individual mailbox or email item is not supported but can be simulated by use of the "Recovery" Storage Group (see below). -\subsection{Installing} +\subsubsection{Installing} The Exchange plugin requires a DLL that is shipped with Microsoft Exchanger Server called {\bf esebcli2.dll}. Assuming Exchange is installed correctly the Exchange plugin should find this automatically and run @@ -2315,7 +2321,7 @@ directory (eg C:\verb+\+Program Files\verb+\+Bacula\verb+\+bin). The Exchange AP named esebcli2.dll and is found in C:\verb+\+Program Files\verb+\+Exchsrvr\verb+\+bin on a default Exchange installation. -\subsection{Backing Up} +\subsubsection{Backing Up} To back up an Exchange server the Fileset definition must contain at least {\bf Plugin = "exchange:/@EXCHANGE/Microsoft Information Store"} for the backup to work correctly. The 'exchange:' bit tells Bacula to look @@ -2345,7 +2351,7 @@ the plugin and Exchange's shared ideas of when the last full backup was done, and may also truncate log files incorrectly. It is important, therefore, that the Exchange database files be excluded from the backup, although the folders the files are in should be included, or they will -have to be recreated manually if a baremetal restore is done. +have to be recreated manually if a bare metal restore is done. \begin{verbatim} FileSet { @@ -2370,7 +2376,7 @@ reduce the size of your backup since all the important Exchange files will be properly saved by the Plugin. -\subsection{Restoring} +\subsubsection{Restoring} The restore operation is much the same as a normal Bacula restore, with the following provisos: @@ -2391,7 +2397,7 @@ the following provisos: as Exchange can get confused by stray log files lying around. \end{itemize} -\subsection{Restoring to the Recovery Storage Group} +\subsubsection{Restoring to the Recovery Storage Group} The concept of the Recovery Storage Group is well documented by Microsoft \elink{http://support.microsoft.com/kb/824126}{http://support.microsoft.com/kb/824126}, @@ -2416,15 +2422,15 @@ Recovery Storage Group. Exchange will redirect the restore to the Recovery Storage Group automatically. Then run the restore. -\subsection{Restoring on Microsoft Server 2007} +\subsubsection{Restoring on Microsoft Server 2007} Apparently the {\bf Exmerge} program no longer exists in Microsoft Server -2007, and henc you use a new proceedure for recovering a single mail box. -This procedure is ducomented by Microsoft at: +2007, and hence you use a new procedure for recovering a single mail box. +This procedure is documented by Microsoft at: \elink{http://technet.microsoft.com/en-us/library/aa997694.aspx}{http://technet.microsoft.com/en-us/library/aa997694.aspx}, and involves using the {\bf Restore-Mailbox} and {\bf -Get-MailboxStatistics} shell commands. +Get-Mailbox Statistics} shell commands. -\subsection{Caveats} +\subsubsection{Caveats} This plugin is still being developed, so you should consider it currently in BETA test, and thus use in a production environment should be done only after very careful testing. @@ -2458,7 +2464,7 @@ estimate} command, and so anything that would be backed up by the plugin will not be added to the estimate total that is displayed. -\section{libdbi Framework} +\subsection{libdbi Framework} \index[general]{libdbi Framework} As a general guideline, Bacula has support for a few catalog database drivers (MySQL, PostgreSQL, SQLite) @@ -2536,10 +2542,10 @@ following packages are needed: You can download them and compile them on your system or install the packages from your OS distribution. -\section{Console Command Additions and Enhancements} +\subsection{Console Command Additions and Enhancements} \index[general]{Console Additions} -\subsection{Display Autochanger Content} +\subsubsection{Display Autochanger Content} \index[general]{StatusSlots} The {\bf status slots storage=\lt{}storage-name\gt{}} command displays @@ -2560,7 +2566,7 @@ If you an asterisk ({\bf *}) appears after the slot number, you must run an {\bf update slots} command to synchronize autochanger content with your catalog. -\subsection{list joblog job=xxx or jobid=nnn} +\subsubsection{list joblog job=xxx or jobid=nnn} \index[general]{list joblog} A new list command has been added that allows you to list the contents of the Job Log stored in the catalog for either a Job Name (fully qualified) @@ -2576,7 +2582,7 @@ such as: In your Director's {\bf Messages} resource. -\subsection{Use separator for multiple commands} +\subsubsection{Use separator for multiple commands} \index[general]{Command Separator} When using bconsole with readline, you can set the command separator with \textbf{@separator} command to one @@ -2585,7 +2591,7 @@ In your Director's {\bf Messages} resource. !$%&'()*+,-/:;<>?[]^`{|}~ \end{verbatim} -\subsection{Deleting Volumes} +\subsubsection{Deleting Volumes} The delete volume bconsole command has been modified to require an asterisk (*) in front of a MediaId otherwise the value you enter is a taken to be a Volume name. This is so that @@ -2595,7 +2601,7 @@ assumed that all input that started with a number was a MediaId. This new behavior is indicated in the prompt if you read it carefully. -\section{Bare Metal Recovery} +\subsection{Bare Metal Recovery} The old bare metal recovery project is essentially dead. One of the main features of it was that it would build a recovery CD based on the kernel on your system. The problem was that @@ -2639,10 +2645,10 @@ The disadvantages are: The documentation and the code can be found in the {\bf rescue} package in the directory {\bf linux/usb}. -\section{Miscellaneous} +\subsection{Miscellaneous} \index[general]{Misc New Features} -\subsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}} +\subsubsection{Allow Mixed Priority = \lt{}yes\vb{}no\gt{}} \index[general]{Allow Mixed Priority} This directive is only implemented in version 2.5 and later. When set to {\bf yes} (default {\bf no}), this job may run even if lower @@ -2658,7 +2664,7 @@ in the directory {\bf linux/usb}. the running jobs finishes. However, new priority 10 jobs will not be run until the priority 5 job has finished. -\subsection{Bootstrap File Directive -- FileRegex} +\subsubsection{Bootstrap File Directive -- FileRegex} \index[general]{Bootstrap File Directive} {\bf FileRegex} is a new command that can be added to the bootstrap (.bsr) file. The value is a regular expression. When specified, only @@ -2681,7 +2687,7 @@ in the directory {\bf linux/usb}. Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr \end{verbatim} -\subsection{Bootstrap File Optimization Changes} +\subsubsection{Bootstrap File Optimization Changes} In order to permit proper seeking on disk files, we have extended the bootstrap file format to include a {\bf VolStartAddr} and {\bf VolEndAddr} records. Each takes a 64 bit unsigned integer range (i.e. nnn-mmm) which defines the start @@ -2693,7 +2699,7 @@ may read completely to the end of a disk volume during a restore. With the new format (automatically generated by the new Director), restores will seek properly and stop reading the volume when all the files have been restored. -\subsection{Solaris ZFS/NFSv4 ACLs} +\subsubsection{Solaris ZFS/NFSv4 ACLs} This is an upgrade of the previous Solaris ACL backup code to the new library format, which will backup both the old POSIX(UFS) ACLs as well as the ZFS ACLs. @@ -2703,7 +2709,7 @@ The new code can also restore POSIX(UFS) ACLs to a ZFS filesystem be used to transfer from UFS to ZFS filesystems. -\subsection{Virtual Tape Emulation} +\subsubsection{Virtual Tape Emulation} \index[general]{Virtual Tape Emulation} We now have a Virtual Tape emulator that allows us to run though 99.9\% of the tape code but actually reading and writing to a disk file. Used with the @@ -2713,7 +2719,7 @@ by using {\bf Device Type = vtape} in the Storage daemon's Device directive. This feature is only implemented on Linux machines and should not be used for production. -\subsection{Bat Enhancements} +\subsubsection{Bat Enhancements} \index[general]{Bat Enhancements} Bat (the Bacula Administration Tool) GUI program has been significantly enhanced and stabilized. In particular, there are new table based status @@ -2724,7 +2730,7 @@ GUI handling. Note, you {\bf must} use a the bat that is distributed with the Director you are using otherwise the communications protocol will not work. -\subsection{RunScript Enhancements} +\subsubsection{RunScript Enhancements} \index[general]{RunScript Enhancements} The {\bf RunScript} resource has been enhanced to permit multiple commands per RunScript. Simply specify multiple {\bf Command} directives @@ -2752,17 +2758,17 @@ carefully tested and debugged and is known to easily crash the Director. We would appreciate feedback. Due to the recursive nature of this command, we may remove it before the final release. -\subsection{Status Enhancements} +\subsubsection{Status Enhancements} \index[general]{Status Enhancements} The bconsole {\bf status dir} output has been enhanced to indicate Storage daemon job spooling and despooling activity. -\subsection{Connect Timeout} +\subsubsection{Connect Timeout} \index[general]{Connect Timeout} The default connect timeout to the File daemon has been set to 3 minutes. Previously it was 30 minutes. -\subsection{ftruncate for NFS Volumes} +\subsubsection{ftruncate for NFS Volumes} \index[general]{ftruncate for NFS Volumes} If you write to a Volume mounted by NFS (say on a local file server), in previous Bacula versions, when the Volume was recycled, it was not @@ -2771,13 +2777,13 @@ truncate). This is now corrected in the new version because we have written code (actually a kind user) that deletes and recreates the Volume, thus accomplishing the same thing as a truncate. -\subsection{Support for Ubuntu} +\subsubsection{Support for Ubuntu} The new version of Bacula now recognizes the Ubuntu (and Kubuntu) version of Linux, and thus now provides correct autostart routines. Since Ubuntu officially supports Bacula, you can also obtain any recent release of Bacula from the Ubuntu repositories. -\subsection{Recycle Pool = \lt{}pool-name\gt{}} +\subsubsection{Recycle Pool = \lt{}pool-name\gt{}} \index[general]{Recycle Pool} The new \textbf{RecyclePool} directive defines to which pool the Volume will be placed (moved) when it is recycled. Without this directive, a Volume will @@ -2786,21 +2792,21 @@ moved automatically to any existing pool during a recycle. This directive is probably most useful when defined in the Scratch pool, so that volumes will be recycled back into the Scratch pool. -\subsection{FD Version} +\subsubsection{FD Version} \index[general]{FD Version} The File daemon to Director protocol now includes a version number, which although there is no visible change for users, will help us in future versions automatically determine if a File daemon is not compatible. -\subsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}} +\subsubsection{Max Run Sched Time = \lt{}time-period-in-seconds\gt{}} \index[general]{Max Run Sched Time} The time specifies the maximum allowed time that a job may run, counted from when the job was scheduled. This can be useful to prevent jobs from running during working hours. We can see it like \texttt{Max Start Delay + Max Run Time}. -\subsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}} +\subsubsection{Max Wait Time = \lt{}time-period-in-seconds\gt{}} \index[general]{Max Wait Time} Previous \textbf{MaxWaitTime} directives aren't working as expected, instead of checking the maximum allowed time that a job may block for a resource, @@ -2810,14 +2816,14 @@ their job depending on the level. Now, they have to use \textbf{Incr/Diff/Full Max Run Time}. \textbf{Incr/Diff/Full Max Wait Time} directives are now deprecated. -\subsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}} +\subsubsection{Incremental|Differential Max Wait Time = \lt{}time-period-in-seconds\gt{}} \index[general]{Incremental Max Wait Time} \index[general]{Differential Max Wait Time} These directives have been deprecated in favor of \texttt{Incremental|Differential Max Run Time}. -\subsection{Max Run Time directives} +\subsubsection{Max Run Time directives} \index[general]{Max Run Time directives} Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the maximum allowed time that a job can run depending on the level. @@ -2825,7 +2831,7 @@ maximum allowed time that a job can run depending on the level. \addcontentsline{lof}{figure}{Job time control directives} \includegraphics{\idir different_time.eps} -\subsection{Statistics Enhancements} +\subsubsection{Statistics Enhancements} \index[general]{Statistics Enhancements} If you (or probably your boss) want to have statistics on your backups to provide some \textit{Service Level Agreement} indicators, you could use a few @@ -2877,35 +2883,35 @@ Job { } \end{verbatim} -\subsection{ScratchPool = \lt{}pool-resource-name\gt{}} +\subsubsection{ScratchPool = \lt{}pool-resource-name\gt{}} \index[general]{ScratchPool} This directive permits to specify a specific \textsl{Scratch} pool for the current pool. This is useful when using multiple storage sharing the same mediatype or when you want to dedicate volumes to a particular set of pool. -\subsection{Enhanced Attribute Despooling} +\subsubsection{Enhanced Attribute Despooling} \index[general]{Attribute Despooling} If the storage daemon and the Director are on the same machine, the spool file that contains attributes is read directly by the Director instead of being transmitted across the network. That should reduce load and speedup insertion. -\subsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}} +\subsubsection{SpoolSize = \lt{}size-specification-in-bytes\gt{}} \index[general]{SpoolSize} A new Job directive permits to specify the spool size per job. This is used in advanced job tunning. {\bf SpoolSize={\it bytes}} -\subsection{MaximumConsoleConnections = \lt{}number\gt{}} +\subsubsection{MaximumConsoleConnections = \lt{}number\gt{}} \index[general]{MaximumConsoleConnections} A new director directive permits to specify the maximum number of Console Connections that could run concurrently. The default is set to 20, but you may set it to a larger number. -\subsection{VerId = \lt{}string\gt{}} +\subsubsection{VerId = \lt{}string\gt{}} \index[general]{VerId} A new director directive permits to specify a personnal identifier that will be displayed in the \texttt{version} command. -\subsection{dbcheck enhancements} +\subsubsection{dbcheck enhancements} \index[general]{dbcheck enhancements} If you are using Mysql, dbcheck will now ask you if you want to create temporary indexes to speed up orphaned Path and Filename elimination. @@ -2928,20 +2934,20 @@ text based format. This is useful to backup it in a secure way. You can now specify the database connection port in the command line. -\subsection{{-}{-}docdir configure option} +\subsubsection{{-}{-}docdir configure option} \index[general]{{-}{-}docdir configure option} You can use {-}{-}docdir= on the ./configure command to specify the directory where you want Bacula to install the LICENSE, ReleaseNotes, ChangeLog, ... files. The default is {\bf /usr/share/doc/bacula}. -\subsection{{-}{-}htmldir configure option} +\subsubsection{{-}{-}htmldir configure option} \index[general]{{-}{-}htmldir configure option} You can use {-}{-}htmldir= on the ./configure command to specify the directory where you want Bacula to install the bat html help files. The default is {\bf /usr/share/doc/bacula/html} -\subsection{{-}{-}with-plugindir configure option} +\subsubsection{{-}{-}with-plugindir configure option} \index[general]{{-}{-}plugindir configure option} You can use {-}{-}plugindir= on the ./configure command to specify the directory where you want Bacula to install