column=0
encoding=UTF-8
highlight=LaTeX
-line=191
+line=209
open=true
order=0
and give a better estimation.
You can set the accurate behavior on the command line by using
-\texttt{accurate=yes/no} or use the Job setting as default value.
+\texttt{accurate=yes\vb{}no} or use the Job setting as default value.
\begin{verbatim}
* estimate listing accurate=yes level=incremental job=BackupJob
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|no\gt{}}
-If the {\bf Accurate = \lt{}yes|no\gt{}} directive is enabled (default no) in
+\subsection{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
Incremental} backups, the Director will send a list of all previous files
They are:
-\subsection{Allow Duplicate Jobs = \lt{}yes|no\gt{}}
+\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
the directive is set to {\bf no} (default) then only one job of a given name
will be cancelled.
-\subsection{Allow Higher Duplicates = \lt{}yes|no\gt{}}
+\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
priorities of the two jobs are the same, the outcome is determined by
other directives (see below).
-\subsection{Cancel Queued Duplicates = \lt{}yes|no\gt{}}
+\subsection{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}.
-\subsection{Cancel Running Duplicates = \lt{}yes|no\gt{}}
+\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
{\bf Incremental}, it will be automatically
upgraded to a {\bf Differential} backup.
-\section{Honor No Dump Flag = \lt{}yes|no\gt{}}
+\section{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
obey this flag. The new directive is:
\begin{verbatim}
- Honor No Dump Flag = yes|no
+ Honor No Dump Flag = yes\vb{}no
\end{verbatim}
The default value is {\bf no}.
\section{Miscellaneous}
\index[general]{Misc New Features}
-\subsection{Allow Mixed Priority = \lt{}yes|no\gt{}}
+\subsection{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
There were no files inserted into the tree, so file selection
is not possible.Most likely your retention policy pruned the files
- Do you want to restore all the files? (yes|no): no
+ Do you want to restore all the files? (yes\vb{}no): no
Regexp matching files to restore? (empty to abort): /tmp/regress/(bin|tests)/
Bootstrap records written to /tmp/regress/working/zog4-dir.restore.1.bsr
\item To turn data spooling on/off at the Job level in the Job resource in
the Director's conf file (default {\bf no}).
-{\bf SpoolData = yes|no}
+{\bf SpoolData = yes\vb{}no}
\item To override the Job specification in a Schedule Run directive in the
Director's conf file.
-{\bf SpoolData = yes|no}
+{\bf SpoolData = yes\vb{}no}
\item To override the Job specification in a bconsole session using the \texttt{run}
command. Please note that this does {\bf not } refer to a configuration
statement, but to an argument for the run command.
-{\bf SpoolData=yes|no}
+{\bf SpoolData=yes\vb{}no}
\item To limit the the maximum spool file size for a particular job in the Job
resource
A 64 bit integer value. Typically these are values such as bytes that can
exceed 4 billion and thus require a 64 bit value.
-\item [yes|no]
+\item [yes\vb{}no]
\index[dir]{yes or no }
Either a {\bf yes} or a {\bf no}.
specify here followed by the date and time the job was scheduled for
execution. This directive is required.
-\item [Enabled = \lt{}yes|no\gt{}]
+\item [Enabled = \lt{}yes\vb{}no\gt{}]
\index[dir]{Enable}
\index[dir]{Directive!Enable}
This directive allows you to enable or disable automatic execution
have been deleted.
\end{description}
-\item [Accurate = \lt{}yes|no\gt{}]
+\item [Accurate = \lt{}yes\vb{}no\gt{}]
\index[dir]{Accurate}
In accurate mode, the File daemon knowns exactly which files were present
after the last backup. So it is able to handle deleted or renamed files.
considered.
\label{PreferMountedVolumes}
-\item [Prefer Mounted Volumes = \lt{}yes|no\gt{}]
+\item [Prefer Mounted Volumes = \lt{}yes\vb{}no\gt{}]
\index[dir]{Prefer Mounted Volumes}
\index[dir]{Directive!Prefer Mounted Volumes}
If the Prefer Mounted Volumes directive is set to {\bf yes} (default
pools so that Bacula will be forced to mount Volumes from those Pools
on different drives.
-\item [Prune Jobs = \lt{}yes|no\gt{}]
+\item [Prune Jobs = \lt{}yes\vb{}no\gt{}]
\index[dir]{Prune Jobs}
\index[dir]{Directive!Prune Jobs}
Normally, pruning of Jobs from the Catalog is specified on a Client by
default is {\bf no}.
-\item [Prune Files = \lt{}yes|no\gt{}]
+\item [Prune Files = \lt{}yes\vb{}no\gt{}]
\index[dir]{Prune Files}
\index[dir]{Directive!Prune Files}
Normally, pruning of Files from the Catalog is specified on a Client by
yes}, it will override the value specified in the Client resource. The
default is {\bf no}.
-\item [Prune Volumes = \lt{}yes|no\gt{}]
+\item [Prune Volumes = \lt{}yes\vb{}no\gt{}]
\index[dir]{Prune Volumes}
\index[dir]{Directive!Prune Volumes}
Normally, pruning of Volumes from the Catalog is specified on a Client
Note, please see the notes above in {\bf RunScript}
concerning Windows clients.
-\item [Rerun Failed Levels = \lt{}yes|no\gt{}]
+\item [Rerun Failed Levels = \lt{}yes\vb{}no\gt{}]
\index[dir]{Rerun Failed Levels}
\index[dir]{Directive!Rerun Failed Levels}
If this directive is set to {\bf yes} (default no), and Bacula detects that
when checking for failed levels, which means that any FileSet change will
trigger a rerun.
-\item [Spool Data = \lt{}yes|no\gt{}]
+\item [Spool Data = \lt{}yes\vb{}no\gt{}]
\index[dir]{Spool Data}
\index[dir]{Directive!Spool Data}
NOTE: When this directive is set to yes, Spool Attributes is also
automatically set to yes.
-\item [Spool Attributes = \lt{}yes|no\gt{}]
+\item [Spool Attributes = \lt{}yes\vb{}no\gt{}]
\index[dir]{Spool Attributes}
\index[dir]{Directive!Spool Attributes}
\index[dir]{slow}
if the backed up file already exists, Bacula skips restoring this file.
\end{description}
-\item [Prefix Links=\lt{}yes|no\gt{}]
+\item [Prefix Links=\lt{}yes\vb{}no\gt{}]
\index[dir]{Prefix Links}
\index[dir]{Directive!Prefix Links}
If a {\bf Where} path prefix is specified for a recovery job, apply it
documented under \ilink{ Maximum Concurrent Jobs}{DirMaxConJobs} in the
Director's resource.
-\item [Reschedule On Error = \lt{}yes|no\gt{}]
+\item [Reschedule On Error = \lt{}yes\vb{}no\gt{}]
\index[dir]{Reschedule On Error}
\index[dir]{Directive!Reschedule On Error}
If this directive is enabled, and the job terminates in error, the job
correct order, and that your priority scheme will be respected.
\label{AllowMixedPriority}
-\item [Allow Mixed Priority = \lt{}yes|no\gt{}]
+\item [Allow Mixed Priority = \lt{}yes\vb{}no\gt{}]
\index[dir]{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
be run until the priority 5 job has finished.
\label{WritePartAfterJob}
-\item [Write Part After Job = \lt{}yes|no\gt{}]
+\item [Write Part After Job = \lt{}yes\vb{}no\gt{}]
\index[dir]{Write Part After Job}
\index[dir]{Directive!Write Part After Job}
This directive is only implemented in version 1.37 and later.
specifies to use the Pool named {\bf Incremental} if the job is an
incremental backup.
-\item [SpoolData=yes|no]
+\item [SpoolData=yes\vb{}no]
\index[dir]{SpoolData}
\index[dir]{Directive!SpoolData}
tells Bacula to request the Storage daemon to spool data to a disk file
This directive is available only in Bacula version 2.3.5 or
later.
-\item [WritePartAfterJob=yes|no]
+\item [WritePartAfterJob=yes\vb{}no]
\index[dir]{WritePartAfterJob}
\index[dir]{Directive!WritePartAfterJob}
tells Bacula to request the Storage daemon to write the current part
The default is 180 days.
\label{AutoPrune}
-\item [AutoPrune = \lt{}yes|no\gt{}]
+\item [AutoPrune = \lt{}yes\vb{}no\gt{}]
\index[dir]{AutoPrune}
\index[dir]{Directive!AutoPrune}
If AutoPrune is set to {\bf yes} (default), Bacula (version 1.20 or greater)
check so that you don't try to write data for a DLT onto an 8mm device.
\label{Autochanger1}
-\item [Autochanger = \lt{}yes|no\gt{}]
+\item [Autochanger = \lt{}yes\vb{}no\gt{}]
\index[dir]{Autochanger}
\index[dir]{Directive!Autochanger}
If you specify {\bf yes} for this command (the default is {\bf no}),
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{}]
+\item [Use Volume Once = \lt{}yes\vb{}no\gt{}]
\index[dir]{Use Volume Once}
\index[dir]{Directive!Use Volume Once}
This directive if set to {\bf yes} specifies that each volume is to be
must use the
\ilink{\bf update volume}{UpdateCommand} command in the Console.
-\item [Catalog Files = \lt{}yes|no\gt{}]
+\item [Catalog Files = \lt{}yes\vb{}no\gt{}]
\index[dir]{Catalog Files}
\index[dir]{Directive!Catalog Files}
This directive defines whether or not you want the names of the files
restore} command nor any other command that references File entries.
\label{PoolAutoPrune}
-\item [AutoPrune = \lt{}yes|no\gt{}]
+\item [AutoPrune = \lt{}yes\vb{}no\gt{}]
\index[dir]{AutoPrune}
\index[dir]{Directive!AutoPrune}
If AutoPrune is set to {\bf yes} (default), Bacula (version 1.20 or
\label{PoolRecycle}
-\item [Recycle = \lt{}yes|no\gt{}]
+\item [Recycle = \lt{}yes\vb{}no\gt{}]
\index[dir]{Recycle}
\index[dir]{Directive!Recycle}
This directive specifies whether or not Purged Volumes may be recycled.
\label{RecycleOldest}
-\item [Recycle Oldest Volume = \lt{}yes|no\gt{}]
+\item [Recycle Oldest Volume = \lt{}yes\vb{}no\gt{}]
\index[dir]{Recycle Oldest Volume}
\index[dir]{Directive!Recycle Oldest Volume}
This directive instructs the Director to search for the oldest used
\label{RecycleCurrent}
-\item [Recycle Current Volume = \lt{}yes|no\gt{}]
+\item [Recycle Current Volume = \lt{}yes\vb{}no\gt{}]
\index[dir]{Recycle Current Volume}
\index[dir]{Directive!Recycle Current Volume}
If Bacula needs a new Volume, this directive instructs Bacula to Prune
\label{PurgeOldest}
-\item [Purge Oldest Volume = \lt{}yes|no\gt{}]
+\item [Purge Oldest Volume = \lt{}yes\vb{}no\gt{}]
\index[dir]{Purge Oldest Volume}
\index[dir]{Directive!Purge Oldest Volume}
This directive instructs the Director to search for the oldest used
by MySQL and PostgreSQL and is ignored by SQLite if provided. This
directive is optional.
-%% \item [Multiple Connections = \lt{}yes|no\gt{}]
+%% \item [Multiple Connections = \lt{}yes\vb{}no\gt{}]
%% \index[dir]{Multiple Connections}
%% \index[dir]{Directive!Multiple Connections}
%% By default, this directive is set to no. In that case, each job that uses
This password must be the same as the password specified in the Client
resource in the Director's configuration file. This directive is required.
-\item [Monitor = \lt{}yes|no\gt{}]
+\item [Monitor = \lt{}yes\vb{}no\gt{}]
\index[fd]{Monitor}
\index[fd]{Directive!Monitor}
If Monitor is set to {\bf no} (default), this director will have full access
\index[dir]{Directive!Name}
The name of the FileSet resource. This directive is required.
-\item [Ignore FileSet Changes = \lt{}yes|no\gt{}]
+\item [Ignore FileSet Changes = \lt{}yes\vb{}no\gt{}]
\index[dir]{Ignore FileSet Changes}
\index[dir]{Directive!Ignore FileSet Changes}
Normally, if you modify the FileSet Include or Exclude lists,
Exclude, Bacula will force a Full backup to ensure that everything is
properly backed up.
-\item [Enable VSS = \lt{}yes|no\gt{}]
+\item [Enable VSS = \lt{}yes\vb{}no\gt{}]
\index[dir]{Enable VSS}
\index[dir]{Directive!Enable VSS}
If this directive is set to {\bf yes} the File daemon will be notified
Level=DiskToCatalog} verify is {\bf pins5} i.e. compare permission bits,
inodes, number of links, size, and MD5 changes.
-\item [onefs=yes|no]
+\item [onefs=yes\vb{}no]
\index[dir]{onefs}
\index[dir]{Directive!onefs}
If set to {\bf yes} (the default), {\bf Bacula} will remain on a single
that it did not specify {\bf /var}, then {\bf /var} will not be backed up.
-\item [honor nodump flag=\lt{}yes|no\gt{}]
+\item [honor nodump flag=\lt{}yes\vb{}no\gt{}]
\index[dir]{honornodumpflag}
\index[dir]{Directive!honornodumpflag}
If your file system supports the {\bf nodump} flag (e. g. most
\label{portable}
-\item [portable=yes|no]
+\item [portable=yes\vb{}no]
\index[dir]{portable}
\index[dir]{Directive!portable}
If set to {\bf yes} (default is {\bf no}), the Bacula File daemon will
default ({\bf no}) so that the maximum information concerning your files
is saved.
-\item [recurse=yes|no]
+\item [recurse=yes\vb{}no]
\index[dir]{recurse}
\index[dir]{Directive!recurse}
If set to {\bf yes} (the default), Bacula will recurse (or descend) into
contained in the subdirectories. Normally, you will want the default
({\bf yes}).
-\item [sparse=yes|no]
+\item [sparse=yes\vb{}no]
\index[dir]{sparse}
\index[dir]{Directive!sparse}
Enable special code that checks for sparse files such as created by
really sparse.
\label{readfifo}
-\item [readfifo=yes|no]
+\item [readfifo=yes\vb{}no]
\index[dir]{readfifo}
\index[dir]{Directive!readfifo}
If enabled, tells the Client to read the data on a backup and write the
exec > /dev/null
\end{verbatim}
-\item [noatime=yes|no]
+\item [noatime=yes\vb{}no]
\index[dir]{noatime}
\index[dir]{Directive!noatime}
If enabled, and if your Operating System supports the O\_NOATIME file
silently ignored by Bacula.
-\item [mtimeonly=yes|no]
+\item [mtimeonly=yes\vb{}no]
\index[dir]{mtimeonly}
\index[dir]{Directive!mtimeonly}
If enabled, tells the Client that the selection of files during
st\_mtime and the st\_ctime values. In general, it is not recommended
to use this option.
-\item [keepatime=yes|no]
+\item [keepatime=yes\vb{}no]
\index[dir]{keepatime}
\index[dir]{Directive!keepatime}
The default is {\bf no}. When enabled, Bacula will reset the st\_atime
to use {\bf mtimeonly = yes} as well as keepatime (thanks to
Rudolf Cejka for this tip).
-\item [checkfilechanges=yes|no]
+\item [checkfilechanges=yes\vb{}no]
\index[dir]{checkfilechanges}
\index[dir]{Directive!checkfilechanges}
On versions 2.0.4 or greater,
In general, it is recommended to use this option.
-\item [hardlinks=yes|no]
+\item [hardlinks=yes\vb{}no]
\index[dir]{hardlinks}
\index[dir]{Directive!hardlinks}
When enabled (default), this directive will cause hard links to be
more.
-\item [exclude=yes|no]
+\item [exclude=yes\vb{}no]
\index[dir]{exclude}
\index[dir]{Directive!exclude}
The default is {\bf no}. When enabled, any files matched within the
Options will be excluded from the backup.
\label{ACLSupport}
-\item [aclsupport=yes|no]
+\item [aclsupport=yes\vb{}no]
\index[dir]{aclsupport}
\index[dir]{Directive!aclsupport}
The default is {\bf no}. If this option is set to yes, and you have the
filesystem with ACLs, then you restore them to a different filesystem
(perhaps reiserfs) that does not have ACLs, the ACLs will be ignored.
-\item [ignore case=yes|no]
+\item [ignore case=yes\vb{}no]
\index[dir]{ignore case}
\index[dir]{Directive!ignore case}
The default is {\bf no}. On Windows systems, you will almost surely
This option is not implemented in Unix/Linux systems.
-\item [hfsplussupport=yes|no]
+\item [hfsplussupport=yes\vb{}no]
\index[dir]{hfsplussupport}
\index[dir]{Directive!hfsplussupport}
This option allows you to turn on support for Mac OSX HFS plus
Specifies the password that must be supplied by the above named Director.
This directive is required.
-\item [Monitor = \lt{}yes|no\gt{}]
+\item [Monitor = \lt{}yes\vb{}no\gt{}]
\index[sd]{Monitor}
\index[sd]{Directive!Monitor}
If Monitor is set to {\bf no} (default), this director will have full
unique Media Type.
\label{Autochanger}
-\item [Autochanger = {\it Yes|No}]
+\item [Autochanger = {\it yes\vb{}no}]
\index[sd]{Autochanger}
\index[sd]{Directive!Autochanger}
If {\bf Yes}, this device belongs to an automatic tape changer, and you
the past -- the default mtx-changer script works for any number of
drives.
-\item [Autoselect = {\it Yes|No}]
+\item [Autoselect = {\it yes\vb{}no}]
\index[sd]{Autoselect}
\index[sd]{Directive!Autoselect}
If this directive is set to {\bf yes} (default), and the Device
for a open before timing out. If this time is exceeded,
Bacula will cancel the job. The default is 5 minutes.
-\item [Always Open = {\it Yes|No}]
+\item [Always Open = {\it yes\vb{}no}]
\index[sd]{Always Open}
\index[sd]{Directive!Always Open}
If {\bf Yes} (default), Bacula will always keep the device open unless
\ilink{description of Offline On Unmount}{NoTapeInDrive} in the Tape
Testing chapter.
-\item [Close on Poll= {\it Yes|No}]
+\item [Close on Poll= {\it yes\vb{}no}]
\index[sd]{Close on Poll}
\index[sd]{Directive!Close on Poll}
If {\bf Yes}, Bacula close the device (equivalent to an unmount except no
starts that needs the the drive.
\label{removablemedia}
-\item [Removable media = {\it Yes|No}]
+\item [Removable media = {\it yes\vb{}no}]
\index[sd]{Removable media}
\index[sd]{Directive!Removable media}
If {\bf Yes}, this device supports removable media (for example, tapes
{\bf Removable Media}.
-\item [Random access = {\it Yes|No}]
+\item [Random access = {\it yes\vb{}no}]
\index[sd]{Random access}
\index[sd]{Directive!Random access}
If {\bf Yes}, the archive device is assumed to be a random access medium
{\bf No} for non-random access devices such as tapes and named pipes.
-\item [Requires Mount = {\it Yes|No}]
+\item [Requires Mount = {\it yes\vb{}no}]
\index[sd]{Requires Mount }
When this directive is enabled, the Storage daemon will submit
a {\bf Mount Command} before attempting to open the device.
The maximum {\bf size-in-bytes} possible is 2,000,000.
-\item [Hardware End of Medium = {\it Yes|No}]
+\item [Hardware End of Medium = {\it yes\vb{}no}]
\index[sd]{Hardware End of Medium}
\index[sd]{Directive!Hardware End of Medium}
If {\bf No}, the archive device is not required to support end of medium
supports this function. All modern (after 1998) tape drives support this
feature.
-\item [Fast Forward Space File = {\it Yes|No}]
+\item [Fast Forward Space File = {\it yes\vb{}no}]
\index[sd]{Fast Forward Space File}
\index[sd]{Directive!Fast Forward Space File}
If {\bf No}, the archive device is not required to support keeping track of
Default setting for Fast Forward Space File is {\bf Yes}.
-\item [Use MTIOCGET = {\it Yes|No}]
+\item [Use MTIOCGET = {\it yes\vb{}no}]
\index[sd]{Use MTIOCGET}
\index[sd]{Directive!Use MTIOCGET}
If {\bf No}, the operating system is not required to support keeping track of
on a few *BSD systems. Operating systems known to work correctly are
Solaris, Linux and FreeBSD.
-\item [BSF at EOM = {\it Yes|No}]
+\item [BSF at EOM = {\it yes\vb{}no}]
\index[sd]{BSF at EOM}
\index[sd]{Directive!BSF at EOM}
If {\bf No}, the default, no special action is taken by Bacula with the End
the second EOF mark. Determination of whether or not you need this directive
is done using the {\bf test} command in the {\bf btape} program.
-\item [TWO EOF = {\it Yes|No}]
+\item [TWO EOF = {\it yes\vb{}no}]
\index[sd]{TWO EOF}
\index[sd]{Directive!TWO EOF}
If {\bf Yes}, Bacula will write two end of file marks when terminating a tape
-- i.e. after the last job or at the end of the medium. If {\bf No}, the
default, Bacula will only write one end of file to terminate the tape.
-\item [Backward Space Record = {\it Yes|No}]
+\item [Backward Space Record = {\it yes\vb{}no}]
\index[sd]{Backward Space Record}
\index[sd]{Directive!Backward Space Record}
If {\it Yes}, the archive device supports the {\tt MTBSR ioctl} to backspace
the test will not be done. This causes no harm as the re-read process is
precautionary rather than required.
-\item [Backward Space File = {\it Yes|No}]
+\item [Backward Space File = {\it yes\vb{}no}]
\index[sd]{Backward Space File}
\index[sd]{Directive!Backward Space File}
If {\it Yes}, the archive device supports the {\bf MTBSF} and {\bf MTBSF
advanced forward to the desired position. Default is {\bf Yes} for non
random-access devices.
-\item [Forward Space Record = {\it Yes|No}]
+\item [Forward Space Record = {\it yes\vb{}no}]
\index[sd]{Forward Space Record}
\index[sd]{Directive!Forward Space Record}
If {\it Yes}, the archive device must support the {\bf MTFSR ioctl} to
advance the position on the device. Default is {\bf Yes} for non
random-access devices.
-\item [Forward Space File = {\it Yes|No}]
+\item [Forward Space File = {\it yes\vb{}no}]
\index[sd]{Forward Space File}
\index[sd]{Directive!Forward Space File}
If {\bf Yes}, the archive device must support the {\tt MTFSF ioctl} to
forward space by file marks. If {\it No}, data must be read to advance the
position on the device. Default is {\bf Yes} for non random-access devices.
-\item [Offline On Unmount = {\it Yes|No}]
+\item [Offline On Unmount = {\it yes\vb{}no}]
\index[sd]{Offline On Unmount}
\index[sd]{Directive!Offline On Unmount}
The default for this directive is {\bf No}. If {\bf Yes} the archive device
{\bf Maximum Volume Bytes} directive in the Director's Pool resource,
which does the same thing but on a Pool (Volume) basis.
-\item [Block Positioning = {\it yes|no}]
+\item [Block Positioning = {\it yes\vb{}no}]
\index[sd]{Block Positioning}
\index[sd]{Directive!Block Positioning}
This directive tells Bacula not to use block positioning when doing restores.
\begin{description}
-\item [Requires Mount = {\it Yes|No}]
+\item [Requires Mount = {\it yes\vb{}no}]
\index[sd]{Requires Mount}
\index[sd]{Directive!Requires Mount}
You must set this directive to {\bf yes} for DVD-writers, and to {\bf no} for
\begin{description}
-\item [Label media = {\it Yes|No}]
+\item [Label media = {\it yes\vb{}no}]
\index[sd]{Label media}
\index[sd]{Directive!Label media}
If {\bf Yes}, permits this device to automatically label blank media
when the tape has been recycled. The automatic labeling feature is most
useful when writing to disk rather than tape volumes.
-\item [Automatic mount = {\it Yes|No}]
+\item [Automatic mount = {\it yes\vb{}no}]
\index[sd]{Automatic mount}
\index[sd]{Directive!Automatic mount}
If {\bf Yes} (the default), permits the daemon to examine the device to
projects / bacula / docs / commitdiff