\item [directors]
Used in the show command. Takes no arguments.
\item [directory]
- Used in the restore command.
+ Used in the restore command. Its argument specifies the directory
+ to be restored.
+\item [enabled]
+ This keyword can appear on the {\bf update volume} command, and can
+ allows one of the following arguments: yes, true, no, false, archived,
+ 0, 1, 2. Where 0 corresponds to no or false, 1 corresponds to yes or true, and
+ 2 corresponds to archived. Archived volumes will not be used, nor will
+ the Media record in the catalog be pruned. Volumes that are not enabled,
+ will not be used for backup or restore.
\item [done]
Used in the restore command. Takes no argument.
\item [file]
\begin{verbatim}
update volume=xxx pool=yyy slots volstatus=xxx VolRetention=ddd
VolUse=ddd MaxVolJobs=nnn MaxVolBytes=nnn Recycle=yes|no
- slot=nnn
+ slot=nnn enabled=n
\end{verbatim}
\normalsize
use to control the DVD writing.
\label{DVDdirectives}
-
\subsection*{DVD Specific SD Directives}
\index[general]{Directives!DVD}
\index[general]{DVD Specific SD Directives }
\end{verbatim}
\normalsize
+However, if you have defined a mount point in /etc/fstab, you might be
+able to use a mount command such as:
+
+\footnotesize
+\begin{verbatim}
+ Mount Command = "/bin/mount /media/dvd"
+\end{verbatim}
+\normalsize
+
+
\item [Unmount Command = {\it name-string}]
\index[sd]{Unmount Command}
Command that must be executed to unmount the device. Before the command is
\index[sd]{Free Space Command }
Command that must be executed to check how much free space is left on the
device. Before the command is executed,\%a is replaced with the Archive
- Device, \%m with the Mount Point, \%e is replaced with 1 if we are writing
- the first part, and with 0 otherwise, and \%v with the current part filename.
+ Device.
For a DVD, you will most frequently specify the Bacula supplied {\bf
dvd-handler} script as follows:
{\bf /dev/dvd} depending on your system. It will not be a name such
as {\bf /mnt/cdrom}.
+\subsection*{Edit Codes for DVD Directives}
+\index[general]{Directives!DVD Edit Codes}
+\index[general]{Edit Codes for DVD Directives }
+\addcontentsline{toc}{subsection}{Edit Codes fro DVD Directives}
+
+Before submitting the {\bf Mount Command}, {\bf Unmount Command},
+{\bf Write Part Command}, or {\bf Free Space Command} directives
+to the operating system, Bacula performs character substitution of the
+following characters:
+
+\footnotesize
+\begin{verbatim}
+ %% = %
+ %a = Archive device name
+ %e = erase (set if cannot mount and first part)
+ %n = part number
+ %m = mount point
+ %v = last part name (i.e. filename)
+\end{verbatim}
+\normalsize
+
+
\subsection*{DVD Specific Director Directives}
\index[general]{Directives!DVD}
\item DVD+RW and DVD-RW support only about 1000 overwrites (i.e. don't use the
same medium for years if you don't want to have problems...).
-\item For more informations about DVD writing, please look at the
+To write to the DVD the first time use:
+\begin{verbatim}
+ growisofs -Z /dev/xxx filename
+\end{verbatim}
+
+To add additional files (more parts use):
+
+\begin{verbatim}
+ growisofs -M /dev/xxx filename
+\end{verbatim}
+
+The option {\bf -use-the-force-luke=4gms} was added in growisofs 5.20 to
+override growisofs' behavior of always checking for the 4GB limit.
+Normally, this option is recommended for all Linux kernels 2.6.8 or
+greater, since these newer kernels can handle writing more than 4GB.
+See below for more details on this subject.
+
+\item For more information about DVD writing, please look at the
\elink{dvd+rw-tools homepage}{http://fy.chalmers.se/~appro/linux/DVD+RW/}.
+
+
\end{itemize}
\item [hardlinks=yes|no]
\index[dir]{hardlinks}
\index[dir]{Directive!hardlinks}
- When enabled (default), this directive will cause hard inks to be
+ When enabled (default), this directive will cause hard links to be
backed up. However, the File daemon keeps track of hard linked files and
will backup the data only once. The process of keeping track of the
hard links can be quite expensive if you have lots of them (tens of
\index[general]{program!bextract}
\addcontentsline{toc}{subsection}{bextract}
+If you find yourself using {\bf bextract}, you probably have done
+something wrong. For example, if you are trying to recover a file
+but are having problems, please see the \ilink {Restoring When Things Go
+Wrong}{database_restore} section of the Restore chapter of this manual.
+
Normally, you will restore files by running a {\bf Restore} Job from the {\bf
Console} program. However, {\bf bextract} can be used to extract a single file
or a list of files from a Bacula tape or file. In fact, {\bf bextract} can be
\index[general]{program!bscan}
\addcontentsline{toc}{subsection}{bscan}
-The {\bf bscan} program can be used to re-create a database (catalog) from the
-backup information written to one or more Volumes. This is normally needed
-only if one or more Volumes have been pruned or purged from your catalog so
-that the records on the Volume are no longer in the catalog.
If you find yourself using this program, you have probably done something
wrong. For example, the best way to recover a lost or damaged Bacula
database is to reload the database from using the bootstrap file that
was written when you saved it.
+The {\bf bscan} program can be used to re-create a database (catalog) from
+the backup information written to one or more Volumes. This is normally
+needed only if one or more Volumes have been pruned or purged from your
+catalog so that the records on the Volume are no longer in the catalog, or
+for Volumes that you have archived.
+
With some care, it can also be used to synchronize your existing catalog with
a Volume. Although we have never seen a case of bscan damaging a
catalog, since bscan modifies your catalog, we recommend that
encryption code to provide secure network transport similar to
that offered by {\bf stunnel} or {\bf ssh}. The data written to
Volumes by the Storage daemon is not encrypted by this code.
-The Bacula encryption code was written by Landon Fuller.
+For data encryption, please see the \ilink{Data Encryption
+Chapter}{DataEncryption} of this manual.
+
+The Bacula encryption implementations were written by Landon Fuller.
Supported features of this code include:
\begin{itemize}
\begin{description}
\item [TLS Enable = \lt{}yes|no\gt{}]
-Enable TLS support.
+Enable TLS support. If TLS is not enabled, none of the other TLS directives
+have any effect. In other words, even if you set {\bf TLS Require = yes}
+you need to have TLS enabled or TLS will not be used.
\item [TLS Require = \lt{}yes|no\gt{}]
-Require TLS connections.
+Require TLS connections. This directive is ignored unless {\bf TLS Enable}
+is set to {\bf yes}. If TLS is not required, and TLS is enabled, then
+Bacula will connect with other daemons either with or without TLS depending
+on what the other daemon requests. If TLS is enabled and TLS is required,
+then Bacula will refuse any connection that does not use TLS.
\item [TLS Certificate = \lt{}Directory\gt{}]
Path to a PEM encoded TLS certificate. It can be used as either a client
Note, however, that self-signed certificates will only work for the
outgoing end of connections. For example, in the case of the Director
making a connection to a File Daemon, the File Daemon may be configured to
-allow self-signed certifictes, but the certificate being sed by the
+allow self-signed certifictes, but the certificate used by the
Director must be signed by a certificate that is explicitly trusted on the
File Daemon end.
Landon has supplied us with the TLS portions of his configuration
files, which should help you setting up your own.
-
+
{\bf bacula-dir.conf}
\footnotesize
\begin{verbatim}
-1.39.21 (27 August 2006)
+1.39.21 (02 Septermber 2006)
projects / bacula / docs / commitdiff