From 2c8aad3c0e4fa1c32a525824ccb4fefa3e404fa3 Mon Sep 17 00:00:00 2001 From: Kern Sibbald Date: Sun, 5 Oct 2008 19:09:15 +0000 Subject: [PATCH] ADoc for new changes from Kjetil that were just iintegrated --- docs/manuals/en/concepts/bootstrap.tex | 5 ++++ docs/manuals/en/concepts/newfeatures.tex | 29 ++++++++++++++++++++++-- docs/manuals/en/install/dirdconf.tex | 22 +++++++++++++++++- 3 files changed, 53 insertions(+), 3 deletions(-) diff --git a/docs/manuals/en/concepts/bootstrap.tex b/docs/manuals/en/concepts/bootstrap.tex index b69cdfbf..a5923f20 100644 --- a/docs/manuals/en/concepts/bootstrap.tex +++ b/docs/manuals/en/concepts/bootstrap.tex @@ -148,6 +148,11 @@ matched against the Volume records are: To restore a particular file, this value (or a range of FileIndexes) is required. +\item [FileRegex] + \index[general]{FileRegex } + The value is a regular expression. When specified, only matching + filenames will be restored. + \item [Slot] \index[general]{Slot } The value specifies the autochanger slot. There may be only a single {\bf diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex index e9cc2e1d..4c8a1ad7 100644 --- a/docs/manuals/en/concepts/newfeatures.tex +++ b/docs/manuals/en/concepts/newfeatures.tex @@ -542,8 +542,34 @@ catalog. \section{Miscellaneous} \index[general]{Misc New Features} -\subsection{Virtual Tape Emulation} +\subsection{Allow Mixed Priority = \lt{}yes|no\g{}} + 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 + priority jobs are already running. This means a high priority job + will not have to wait for other jobs to finish before starting. + The scheduler will only mix priorities when all running jobs have + this set to true. + + Note that only higher priority jobs will start early. Suppose the + director will allow two concurrent jobs, and that two jobs with + priority 10 are running, with two more in the queue. If a job with + priority 5 is added to the queue, it will be run as soon as one of + 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} + {\bf FileRegex} is a new command that can be added to the bootstrap + (.bsr) file. The value is a regular expression. When specified, only + matching filenames will be restored. + + During a restore, if all File records are pruned from the catalog + for a Job, normally Bacula can restore only all files saved. That + is there is no way using the catalog to select individual files. + With this new command, Bacula will ask if you want to specify a Regex + expression for extracting only a part of the full backup. + +\subsection{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 \textbf{disk-changer} script, you can now emulate an autochanger with 10 drives @@ -1395,4 +1421,3 @@ should return: \end{description} - diff --git a/docs/manuals/en/install/dirdconf.tex b/docs/manuals/en/install/dirdconf.tex index 41e79f74..4c88d7a9 100644 --- a/docs/manuals/en/install/dirdconf.tex +++ b/docs/manuals/en/install/dirdconf.tex @@ -1647,7 +1647,8 @@ RunScript { The priority only affects waiting jobs that are queued to run, not jobs that are already running. If one or more jobs of priority 2 are already running, and a new job is scheduled with priority 1, the currently - running priority 2 jobs must complete before the priority 1 job is run. + running priority 2 jobs must complete before the priority 1 job is + run, unless Allow Mixed Priority is set. The default priority is 10. @@ -1685,6 +1686,25 @@ avoid it by starting any higher priority jobs a few seconds before lower priority ones. This insures that Bacula will examine the jobs in the correct order, and that your priority scheme will be respected. +\label{AllowMixedPriority} +\item [Allow Mixed Priority = \lt{}yes|no\g{}] +\index[dir]{Allow Mixed Priority} +\index[dir]{Directive|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 + priority jobs are already running. This means a high priority job + will not have to wait for other jobs to finish before starting. + The scheduler will only mix priorities when all running jobs have + this set to true. + + Note that only higher priority jobs will start early. Suppose the + director will allow two concurrent jobs, and that two jobs with + priority 10 are running, with two more in the queue. If a job with + priority 5 is added to the queue, it will be run as soon as one of + the running jobs finishes. However, new priority 10 jobs will not + be run until the priority 5 job has finished. + \label{WritePartAfterJob} \item [Write Part After Job = \lt{}yes|no\gt{}] \index[dir]{Write Part After Job} -- 2.39.5