From: Kern Sibbald Date: Wed, 16 May 2007 10:30:22 +0000 (+0000) Subject: Update X-Git-Tag: Release-2.2.0~485 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=9098a0323456b5890441c10162167b93eb5b63cd;p=bacula%2Fdocs Update --- diff --git a/docs/developers/version.tex b/docs/developers/version.tex index d13586ce..91d27104 100644 --- a/docs/developers/version.tex +++ b/docs/developers/version.tex @@ -1 +1 @@ -2.1.8 (14 May 2007) +2.1.8 (16 May 2007) diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex index d13586ce..91d27104 100644 --- a/docs/manual-de/version.tex +++ b/docs/manual-de/version.tex @@ -1 +1 @@ -2.1.8 (14 May 2007) +2.1.8 (16 May 2007) diff --git a/docs/manual/autochangers.tex b/docs/manual/autochangers.tex index 27718e3e..47944144 100644 --- a/docs/manual/autochangers.tex +++ b/docs/manual/autochangers.tex @@ -15,18 +15,23 @@ which is explained in more detail after this list: 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. @@ -39,7 +44,8 @@ you must use this new resource. 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. @@ -99,6 +105,10 @@ to find out how to specify their control address ({\bf /dev/sg0} for the 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 @@ -114,10 +124,10 @@ Please check that your Storage daemon has permission to access this 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 @@ -126,17 +136,17 @@ own nsa0.0 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 } @@ -180,12 +190,11 @@ in the Console program. \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 @@ -204,6 +213,14 @@ that device. In general, the second device will have the same {\bf Changer 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 } diff --git a/docs/manual/configure.tex b/docs/manual/configure.tex index 318bc67f..f6f8192b 100644 --- a/docs/manual/configure.tex +++ b/docs/manual/configure.tex @@ -32,6 +32,26 @@ your system. An overall view of the resources can be seen in the following: (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 } diff --git a/docs/manual/dirdconf.tex b/docs/manual/dirdconf.tex index bcfbfe27..7f739e55 100644 --- a/docs/manual/dirdconf.tex +++ b/docs/manual/dirdconf.tex @@ -868,27 +868,30 @@ JobDefs { 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} diff --git a/docs/manual/fileset.tex b/docs/manual/fileset.tex index 5fb0cb13..ad48feef 100644 --- a/docs/manual/fileset.tex +++ b/docs/manual/fileset.tex @@ -18,6 +18,27 @@ automatically create a new FileSet (defined by the name and an MD5 checksum 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] diff --git a/docs/manual/tapetesting.tex b/docs/manual/tapetesting.tex index b645e511..7281f34e 100644 --- a/docs/manual/tapetesting.tex +++ b/docs/manual/tapetesting.tex @@ -353,6 +353,7 @@ See the section above on setting your {\bf Archive device} correctly. 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} diff --git a/docs/manual/version.tex b/docs/manual/version.tex index d13586ce..91d27104 100644 --- a/docs/manual/version.tex +++ b/docs/manual/version.tex @@ -1 +1 @@ -2.1.8 (14 May 2007) +2.1.8 (16 May 2007)