\ilink{Client}{ClientResource2} -- to define what Client is to be
backed up.
\item
- \ilink{Storage}{StorageResource2} -- to define on what physical
+ \ilink{Storage}{StorageResource2} -- to define on what physical
device the Volumes should be mounted.
\item
\ilink{Pool}{PoolResource} -- to define the pool of Volumes
The Storage directive defines the name of the storage services where you
want to backup the FileSet data. For additional details, see the
\ilink{Storage Resource Chapter}{StorageResource2} of this manual.
- This directive is required.
+ The Storage resource may also be specified in the Job's Pool resource,
+ in which case the value in the Pool resource overrides any value
+ in the Job. This Storage resource definition is not required by either
+ the Job resource or in the Pool, but it must be specified in
+ one or the other. If not configuration error will result.
\item [Max Start Delay = \lt{}time\gt{}]
\index[dir]{Max Start Delay}
Client) resource, and in bacula-sd.conf in the Storage resource. If any
one is missing, it will throttle the jobs to one at a time. You may, of
course, set the Maximum Concurrent Jobs to more than 2.
+
\item Bacula concurrently runs jobs of only one priority at a time. It
will not simultaneously run a priority 1 and a priority 2 job.
+
\item If Bacula is running a priority 2 job and a new priority 1 job is
scheduled, it will wait until the running priority 2 job terminates even
if the Maximum Concurrent Jobs settings would otherwise allow two jobs
to run simultaneously.
+
\item Suppose that bacula is running a priority 2 job and a new priority 1
job is scheduled and queued waiting for the running priority 2 job to
terminate. If you then start a second priority 2 job, the waiting
the device when the job is finished (see
\ilink{Write Part After Job directive in the Job
resource}{WritePartAfterJob}). Please note, this directive is implemented
- only in version 1.37 and later.
+ only in version 1.37 and later. The default is yes. We strongly
+ recommend that you keep this set to yes otherwise, when the last job
+ has finished one part will remain in the spool file and restore may
+ or may not work.
\end{description}
\index[dir]{Storage}
\index[dir]{Directive!Storage}
Start of the Storage resources. At least one storage resource must be
-specified.
+ specified.
\item [Name = \lt{}name\gt{}]
\index[dir]{Name}
associated with the Job, Bacula can decide to use any Storage daemon
that supports Media Type {\bf DDS-4} and on any drive that supports it.
+ If you are writing to disk Volumes, you must make doubly sure that each
+ Device resource defined in the Storage daemon (and hence in the
+ Director's conf file) has a unique media type. Otherwise for Bacula
+ versions 1.38 and older, your restores may not work because Bacula
+ will assume that you can mount any Media Type with the same name on
+ any Device associated with that Media Type. This is possible with
+ tape drives, but with disk drives, unless you are very clever you
+ cannot mount a Volume in any directory -- this can be done by creating
+ an appropriate soft link.
+
Currently Bacula permits only a single Media Type. Consequently, if
you have a drive that supports more than one Media Type, you can
give a unique string to Volumes with different intrinsic Media
Job being run. It is required and may be one of the following:
\begin{itemize}
-\item [Backup]
-\item [*Archive]
-\item [*Cloned]
-\item [*Migration]
-\item [*Copy]
-\item [*Save]
- \end{itemize}
+ \item [Backup]
+ \item [*Archive]
+ \item [*Cloned]
+ \item [*Migration]
+ \item [*Copy]
+ \item [*Save]
+\end{itemize}
+ Note, only Backup is current implemented.
+
+\item [Storage = \lt{}storage-resource-name\gt{}]
+\index[dir]{Storage}
+\index[dir]{Directive!Storage}
+ The Storage directive defines the name of the storage services where you
+ want to backup the FileSet data. For additional details, see the
+ \ilink{Storage Resource Chapter}{StorageResource2} of this manual.
+ The Storage resource may also be specified in the Job resource,
+ but the value, if any, in the Pool resource overrides any value
+ in the Job. This Storage resource definition is not required by either
+ the Job resource or in the Pool, but it must be specified in
+ one or the other. If not configuration error will result.
\item [Use Volume Once = \lt{}yes|no\gt{}]
\index[dir]{Use Volume Once}
projects / bacula / docs / commitdiff