\item [Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}]
\index[general]{Allow Higher Duplicates}
- This directive never worked as expected, and was deprecated in version 5.0.1.
-% If this directive is set to {\bf yes} (default) the job with a higher
-% priority (lower priority number) will be permitted to run, and
-% the current job will be cancelled. If the
-% priorities of the two jobs are the same, the outcome is determined by
-% other directives (see below).
-%
+ This directive was implemented 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).
+
\item [Cancel Lower Level Duplicates = \lt{}yes\vb{}no\gt{}]
\index[general]{Cancel Lower Level Duplicates}
- If \textbf{Allow Duplicates Jobs} is set to \textbf{no} and this directives
- is set to \textbf{yes}, Bacula will choose between duplicated jobs
- the one with the highest level. For example, it will cancel a previous
- Incremental to run a Full Backup. It works only for Backup jobs.
- The default is \texttt{no}
+ If \textbf{Allow Duplicates Jobs} is set to \textbf{no} and this
+ directive is set to \textbf{yes}, Bacula will choose between duplicated
+ jobs the one with the highest level. For example, it will cancel a
+ previous Incremental to run a Full backup. It works only for Backup
+ jobs. The default is \texttt{no}. If the levels of the duplicated
+ jobs are the same, nothing is done and the other
+ Cancel XXX Duplicate directives will be examined.
\item [Cancel Queued Duplicates = \lt{}yes\vb{}no\gt{}]
\index[general]{Cancel Queued Duplicates}
5.0.1. This version mainly fixes a number of bugs found in version 5.0.0 during
the onging development process.
-\section{Truncate volume after purge}
+\section{Truncate Volume after Purge}
\label{sec:actiononpurge}
The Pool directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate
the volume when it is purged with the new command \texttt{purge volume
- action}.It is useful to prevent disk based volumes from consuming too much
+ action}. It is useful to prevent disk based volumes from consuming too much
space.
\begin{verbatim}
}
\end{verbatim}
-As usual You can also set this property with the \texttt{update volume} command
+As usual you can also set this property with the \texttt{update volume} command
\begin{verbatim}
-*update volume=xxx actiononpurge=Truncate
+*update volume=xxx ActionOnPurge=Truncate
*update volume=xxx actiononpurge=None
\end{verbatim}
\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}
+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.
+
+\section{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.
+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{Maximum Concurent Jobs for Devices}
root@localhost:~# bacula-fd -k -u nobody -g nobody
\end{verbatim}
-The code for this feature was contributed by AltLinux.
+The code for this feature was contributed by our friends at AltLinux.
\section{Bvfs API}
\label{sec:bvfs}
{\bf c:/Program Files/Bacula} as is the case with the 32
bit Windows installer.
-\section{Bare Metal Recovery USB Key}
+\section{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.
+it the {\bf rescue} release for more details.
+We are working on an equivalent USB key for Windows bare
+metal recovery, but it will take some time to develop it (best
+estimate 3Q2010 or 4Q2010)
\section{bconsole Timeout Option}
write to the same Volume.
\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
+ 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
+ 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}
- and \texttt{transfer}. Be sure to apply any custom changes on to the
- mtx-changer script, or better yet, use mtx-changer.conf to configure
- them.
+ and \texttt{transfer}. Please configure them as appropriate
+ in mtx-changer.conf.
\item To enhance security of the \texttt{BackupCatalog} job, we provide a new
script (\texttt{make\_catalog\_backup.pl}) that does not expose your catalog
password. If you want to use the new script, you will need to
Maximum Concurrent Jobs = 10
SpoolData = No
Allow Duplicate Jobs = Yes
- Allow Higher Duplicates = No
Cancel Queued Duplicates = No
Cancel Running Duplicates = No
Priority = 13
\subsection{Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}}
\index[general]{Allow Duplicate Jobs}
- If this directive is enabled duplicate jobs will be run. If
+ 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
may run at one time, and the action that Bacula takes to ensure only
one job runs is determined by the other directives (see below).
cancelling a job, then the current job (the second one started)
will be cancelled.
-
\subsection{Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}}
\index[general]{Allow Higher Duplicates}
- If this directive is set to {\bf yes} (default) the job with a higher
- priority (lower priority number) will be permitted to run, and
- the current job will be cancelled. If the
- priorities of the two jobs are the same, the outcome is determined by
- other directives (see below).
+ 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{}}
+\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{}}
\index[general]{Cancel Queued Duplicates}
already queued to run but not yet running will be canceled.
The default is {\bf no}.
-\subsection{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}.
-
\section{TLS Authentication}
\index[general]{TLS Authentication}
projects / bacula / docs / commitdiff