-2.1.8 (14 May 2007)
+2.1.8 (16 May 2007)
-2.1.8 (14 May 2007)
+2.1.8 (16 May 2007)
sent by Bacula. We furnish such a script that works with {\bf mtx} found in
the {\bf depkgs} distribution. This script works only with single drive
autochangers.
+
\item That each Volume (tape) to be used must be defined in the Catalog and
have a Slot number assigned to it so that Bacula knows where the Volume is in
the autochanger. This is generally done with the {\bf label} command. See
below for more details. You must pre-label the tapes manually before
using them.
+
\item Modifications to your Storage daemon's Device configuration resource to
identify that the device is a changer, as well as a few other parameters.
+
\item You should also modify your Storage resource definition in the
Director's configuration file so that you are automatically prompted for the
Slot when labeling a Volume.
+
\item You need to ensure that your Storage daemon (if not running as root)
has access permissions to both the tape drive and the control device.
+
\item You need to have {\bf Autochanger = yes} in your Storage resource
in your bacula-dir.conf file so that you will be prompted for the
slot number when you label Volumes.
Bacula uses its own {\bf mtx-changer} script to interface with a program
that actually does the tape changing. Thus in principle, {\bf mtx-changer}
-can be adapted to function with any autochanger program. The current
+can be adapted to function with any autochanger program, or you can
+call any other script or program. The current
version of {\bf mtx-changer} works with the {\bf mtx} program. However,
FreeBSD users have provided a script in the {\bf examples/autochangers}
directory that allows Bacula to use the {\bf chio} program.
first, {\bf /dev/sg1} for the second, ...) on the {\bf Changer Device = }
Bacula directive.
+For more detailed information on what SCSI devices you have please see
+the \ilink{Linux SCSI Tricks}{SCSITricks} section of the Tape Testing
+chapter of this manual.
+
Under FreeBSD, you can use:
\footnotesize
device.
The following tip for FreeBSD users comes from Danny Butroyd:
-n reboot bacula will NOT have permissions to
+on reboot Bacula will NOT have permission to
control the device /dev/pass0 (assuming this is your changer device).
To get around this just edit the /etc/devfs.conf file and add the
-following to the bottom of the config file:
+following to the bottom:
\footnotesize
\begin{verbatim}
own pass0 root:bacula
perm nsa0.0 0666
\end{verbatim}
\normalsize
-I have given the bacula group permission to write to the nsa0.0 device
+
+This gives the bacula group permission to write to the nsa0.0 device
too just to be on the safe side. To bring these changes into effect
just run:-
/etc/rc.d/devfs restart
-Basically this will stop you having to change permissions on these
-devices to make bacula work when operating the AutoChanger after a reboot.
+Basically this will stop you having to manually change permissions on these
+devices to make Bacula work when operating the AutoChanger after a reboot.
\label{scripts}
-
\section{Example Scripts}
\index[general]{Scripts!Example }
\index[general]{Example Scripts }
\label{mult}
\section{Multiple Devices}
-\index[general]{Devices!Multiple }
-\index[general]{Multiple Devices }
+\index[general]{Devices!Multiple}
+\index[general]{Multiple Devices}
Some autochangers have more than one read/write device (drive). The
-new
-\ilink{Autochanger resource}{AutochangerRes} introduced in version
+new \ilink{Autochanger resource}{AutochangerRes} introduced in version
1.37 permits you to group Device resources, where each device
represents a drive. The Director may still reference the Devices (drives)
directly, but doing so, bypasses the proper functioning of the
Device} (control channel) as the first drive, but a different {\bf Archive
Device}.
+As a default, Bacula jobs will prefer to write to a Volume that is
+already mounted. If you have a multiple drive autochanger and you want
+Bacula to write to more than one Volume in the same Pool at the same
+time, you will need to set \ilink{Prefer Mounted Volumes} {PreferMountedVolumes}
+in the Directors Job resource to {\bf no}. This will cause
+the Storage daemon to maximize the use of drives.
+
+
\label{ConfigRecords}
\section{Device Configuration Records}
\index[general]{Records!Device Configuration }
(thanks to Aristides Maniatis for the above graphic)
\label{ResFormat}
+\section{Character Sets}
+\index[general]{Character Sets}
+Bacula is designed to handle most character sets of the world,
+US ASCII, German, French, Chinese, ... However, it does this by
+encoding everything in UTF-8, and it expects all configuration files
+(including those read on Win32 machines) to be in UTF-8 format.
+UTF-8 is typically the default on Linux machines, but not on all
+Unix machines, nor on Windows, so you must take some care to ensure
+that your locale is set properly before starting Bacula.
+
+To ensure that Bacula configuration files can be correctly read including
+foreign characters the {bf LANG} environment variable
+must end in {\bf .UTF-8}. An full example is {\bf en\_US.UTF-8}. The
+exact syntax may vary a bit from OS to OS, and exactly how you define
+it will also vary.
+
+Bacula assumes that all filenames are in UTF-8 format on Linux and
+Unix machines. On Win32 they are in Unicode (UTF-16), and will
+be automatically converted to UTF-8 format.
+
\section{Resource Directive Format}
\index[general]{Resource Directive Format }
\index[general]{Format!Resource Directive }
the same as when the job was scheduled). Please note that if there is a
{\bf Max Wait Time} it may also be applied to the job.
+\label{PreferMountedVolumes}
\item [Prefer Mounted Volumes = \lt{}yes|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
yes), the Storage daemon is requested to select either an Autochanger or
a drive with a valid Volume already mounted in preference to a drive
- that is not ready. If no drive with a suitable Volume is available, it
- will select the first available drive.
+ that is not ready. This means that all jobs will attempt to append
+ to the same Volume (providing the Volume is appropriate -- right Pool,
+ ... for that job). If no drive with a suitable Volume is available, it
+ will select the first available drive. Note, any Volume that has
+ been requested to be mounted, will be considered valid as a mounted
+ volume by another job. This if multiple jobs start at the same time
+ and they all prefer mounted volumes, the first job will request the
+ mount, and the other jobs will use the same volume.
If the directive is set to {\bf no}, the Storage daemon will prefer
finding an unused drive, otherwise, each job started will append to the
same Volume (assuming the Pool is the same for all jobs). Setting
- Prefer Mounted Volumes to no can be useful for those sites particularly
+ Prefer Mounted Volumes to no can be useful for those sites
with multiple drive autochangers that prefer to maximize backup
- throughput at the expense of using additional drives and Volumes. As an
- optimization, when using multiple drives, you will probably want to
- start each of your jobs one after another with approximately 5 second
- intervals. This will help ensure that each night, the same drive
- (Volume) is selected for the same job, otherwise, when you do a restore,
- you may find the files spread over many more Volumes than necessary.
-
+ throughput at the expense of using additional drives and Volumes.
+ This means that the job will prefer to use an unused drive rather
+ than use a drive that is already in use.
\item [Prune Jobs = \lt{}yes|no\gt{}]
\index[dir]{Prune Jobs}
of the Include/Exclude contents). Each time a new FileSet is created,
Bacula will ensure that the next backup is always a Full save.
+\section{Character Sets}
+\index[general]{Character Sets}
+Bacula is designed to handle most character sets of the world,
+US ASCII, German, French, Chinese, ... However, it does this by
+encoding everything in UTF-8, and it expects all configuration files
+(including those read on Win32 machines) to be in UTF-8 format.
+UTF-8 is typically the default on Linux machines, but not on all
+Unix machines, nor on Windows, so you must take some care to ensure
+that your locale is set properly before starting Bacula.
+
+To ensure that Bacula configuration files can be correctly read including
+foreign characters the {bf LANG} environment variable
+must end in {\bf .UTF-8}. An full example is {\bf en\_US.UTF-8}. The
+exact syntax may vary a bit from OS to OS, and exactly how you define
+it will also vary.
+
+Bacula assumes that all filenames are in UTF-8 format on Linux and
+Unix machines. On Win32 they are in Unicode (UTF-16), and will
+be automatically converted to UTF-8 format.
+
+
\begin{description}
\item [FileSet]
For FreeBSD users, please see the notes below for doing further testing of
your tape drive.
+\label{SCSITricks}
\subsection{Linux SCSI Tricks}
\index[general]{Tricks!Linux SCSI}
\index[general]{Linux SCSI Tricks}
-2.1.8 (14 May 2007)
+2.1.8 (16 May 2007)
projects / bacula / docs / commitdiff