where \lt{}string\gt{} is an identifier which can be used for support purpose.
This string is displayed using the \texttt{version} command.
-\item[MaxConsoleConnections = \lt{}number\gt{}]
+\item[MaximumConsoleConnections = \lt{}number\gt{}]
\index[dir]{MaximumConsoleConnections}
- \index[dir]{MaxConsoleConnections}
- \index[dir]{Directive!MaxConsoleConnections}
+ \index[dir]{Directive!MaximumConsoleConnections}
\index[dir]{Console}
where \lt{}number\gt{} is the maximum number of Console Connections that
could run concurrently. The default is set to 20, but you may set it to a
your catalog database.
If the {\bf bootstrap-file-specification} begins with a vertical bar
- (|), Bacula will use the specification as the name of a program to which
+ (\verb+|+), Bacula will use the specification as the name of a program to which
it will pipe the bootstrap record. It could for example be a shell
script that emails you the bootstrap record.
when the job starts, ({\bf not} necessarily the same as when the job was
scheduled). This directive works as expected since bacula 2.3.18.
-\addcontentsline{lof}{figure}{Job time control directives}
-\includegraphics{\idir different_time.eps}
+\begin{figure}[htbp]
+ \centering
+ \includegraphics[width=13cm]{\idir different_time.eps}
+ \caption{Job time control directives}
+ \label{fig:differenttime}
+\end{figure}
+
\item [Max Full Interval = \lt{}time\gt{}]
\index[dir]{Max Full Interval}
job. If it is set to zero (the default) the job will be rescheduled an
indefinite number of times.
+\item [Allow Duplicate Jobs = \lt{}yes\vb{}no\gt{}]
+\index[general]{Allow Duplicate Jobs}
+
+\begin{figure}[htbp]
+ \centering
+ \includegraphics[width=13cm]{\idir duplicate-real.eps}
+ \caption{Allow Duplicate Jobs usage}
+ \label{fig:allowduplicatejobs}
+\end{figure}
+
+A duplicate job in the sense we use it here means a second or subsequent job
+with the same name starts. This happens most frequently when the first job
+runs longer than expected because no tapes are available.
+
+ If this directive is enabled 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).
+
+ 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.
+
+\item [Allow Higher Duplicates = \lt{}yes\vb{}no\gt{}]
+\index[general]{Allow Higher Duplicates}
+ 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
+ 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}
+ If {\bf Allow Duplicate Jobs} is set to {\bf no} and
+ if this directive is set to {\bf yes} any job that is
+ already queued to run but not yet running will be canceled.
+ The default is {\bf no}.
+
+\item[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}.
+
+
+\item[DuplicateJobProximity = \lt{}time-specification\gt{}]
+\index[general]{Duplicate Job Proximity}
+ This directive permits to determine if two jobs are really duplicated.
+ If the first one is running for long time, this is probably not a good
+ idea to cancel it.
+
\item [Run = \lt{}job-name\gt{}]
\index[dir]{Run}
\index[dir]{Directive!Run}
\label{FileRetention}
\item [File Retention = \lt{}time-period-specification\gt{}]
+ \label{FileRetention}
\index[dir]{File Retention}
\index[dir]{Directive!File Retention}
The File Retention directive defines the length of time that Bacula will
\label{JobRetention}
\item [Job Retention = \lt{}time-period-specification\gt{}]
+ \label{JobRetention}
\index[dir]{Job Retention}
\index[dir]{Directive!Job Retention}
The Job Retention directive defines the length of time that Bacula will keep
\item [Action On Purge = \lt{Truncate}]
\index[dir]{actiononpurge}
-This 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.
+This directive \textbf{ActionOnPurge=Truncate} instructs Bacula to truncate the
+volume when it is purged with the \texttt{purge volume action=truncate}
+command. It is useful to prevent disk based volumes from consuming too much
+space.
\begin{verbatim}
Pool {
}
\end{verbatim}
+You can schedule the truncate operation at the end of your CatalogBackup job
+like in this example:
+
+\begin{verbatim}
+Job {
+ Name = CatalogBackup
+ ...
+ RunScript {
+ RunsWhen=After
+ RunsOnClient=No
+ Console = "purge volume action=all allpools storage=File"
+ }
+}
+\end{verbatim}
+
\label{PoolScratchPool}
\item [ScratchPool = \lt{}pool-resource-name\gt{}]
\index[dir]{ScrachPool}
sure that some day, Bacula will recycle a Volume that contains current
data. The default is {\bf no}.
+\item [File Retention = \lt{}time-period-specification\gt{}]
+ \index[dir]{File Retention}
+ \index[dir]{Directive!File Retention}
+ The File Retention directive defines the length of time that Bacula will
+ keep File records in the Catalog database after the End time of the
+ Job corresponding to the File records.
+
+ This directive takes precedence over Client directives of the same name. For
+ example, you can decide to increase Retention times for Archive or OffSite
+ Pool.
+
+ Note, this affects only records in the catalog database. It does not affect
+ your archive backups.
+
+ For more information see Client documentation about
+ \ilink{FileRetention}{FileRetention}
+
+\item [Job Retention = \lt{}time-period-specification\gt{}]
+ \index[dir]{Job Retention}
+ \index[dir]{Directive!Job Retention}
+
+ The Job Retention directive defines the length of time that Bacula will keep
+ Job records in the Catalog database after the Job End time. As with the
+ other retention periods, this affects only records in the catalog and not
+ data in your archive backup.
+
+ This directive takes precedence over Client directives of the same name.
+ For example, you can decide to increase Retention times for Archive or
+ OffSite Pool.
+
+ For more information see Client side documentation
+ \ilink{JobRetention}{JobRetention}
+
\item [Cleaning Prefix = \lt{}string\gt{}]
\index[dir]{Cleaning Prefix}
\index[dir]{Directive!Cleaning Prefix}
projects / bacula / docs / blobdiff