From: Kern Sibbald <kern@sibbald.com>
Date: Thu, 22 Feb 2007 15:33:15 +0000 (+0000)
Subject: Updates
X-Git-Tag: Release-2.2.0~996
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=2d3dfa206ce81704d98b6322b9d2ed47b42ba98c;p=bacula%2Fdocs

Updates
---

diff --git a/docs/developers/version.tex b/docs/developers/version.tex
index e7695043..3b9cc19e 100644
--- a/docs/developers/version.tex
+++ b/docs/developers/version.tex
@@ -1 +1 @@
-2.0.3 (06 February 2007)
+2.0.3 (15 February 2007)
diff --git a/docs/manual-de/update_version b/docs/manual-de/update_version
index ecf019c0..ad1a3bd5 100755
--- a/docs/manual-de/update_version
+++ b/docs/manual-de/update_version
@@ -3,8 +3,8 @@
 # Script file to update the Bacula version
 #
 out=/tmp/$$
-VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' /home/kern/bacula/branch-2.0/src/version.h`
-DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' /home/kern/bacula/branch-2.0/src/version.h`
+VERSION=`sed -n -e 's/^.*VERSION.*"\(.*\)"$/\1/p' /home/kern/bacula/branch-2.0/bacula/src/version.h`
+DATE=`sed -n -e 's/^.*[ \t]*BDATE.*"\(.*\)"$/\1/p' /home/kern/bacula/branch-2.0/bacula/src/version.h`
 . ./do_echo
 sed -f ${out} version.tex.in >version.tex
 rm -f ${out}
diff --git a/docs/manual-de/version.tex b/docs/manual-de/version.tex
index e7695043..3b9cc19e 100644
--- a/docs/manual-de/version.tex
+++ b/docs/manual-de/version.tex
@@ -1 +1 @@
-2.0.3 (06 February 2007)
+2.0.3 (15 February 2007)
diff --git a/docs/manual/tapetesting.tex b/docs/manual/tapetesting.tex
index 1c859b9b..d5d817eb 100644
--- a/docs/manual/tapetesting.tex
+++ b/docs/manual/tapetesting.tex
@@ -20,6 +20,10 @@ Do not proceed to the next item until you have succeeded with the previous
 one. 
 
 \begin{enumerate}
+\item Make sure that Bacula (the Storage daemon) is not running
+  or that you have {\bf unmount}ed the drive you will use 
+  for testing.
+
 \item Use tar to write to, then read from your drive:  
 
    \footnotesize
@@ -98,6 +102,22 @@ on each system type.
 Adjust your autochanger as necessary to ensure that it works  correctly. See
 the Autochanger chapter of this manual  for a complete discussion of testing
 your autochanger.  
+
+\item We strongly recommend that you use a dedicated SCSI
+controller for your tape drives. Scanners are known to induce
+serious problems with the SCSI bus, causing it to reset. If the
+SCSI bus is reset while Bacula has the tape drive open, it will
+most likely be fatal to your tape since the drive will rewind.
+These kinds of problems show up in the system log. For example,
+the following was most likely caused by a scanner:
+
+\footnotesize
+\begin{verbatim}
+Feb 14 17:29:55 epohost kernel: (scsi0:A:2:0): No or incomplete CDB sent to device.
+Feb 14 17:29:55 epohost kernel: scsi0: Issued Channel A Bus Reset. 1 SCBs aborted
+\end{verbatim}
+\normalsize
+
 \end{enumerate}
 
 If you have reached this point, you stand a good chance of having everything
@@ -107,6 +127,7 @@ bacula-users} email list, but specify which of the steps you have successfully
 completed. In particular, you may want to look at the 
 \ilink{ Tips for Resolving Problems}{problems1} section below. 
 
+
 \label{NoTapeInDrive}
 \subsection{Problems When no Tape in Drive}
 \index[general]{Problems When no Tape in Drive}
diff --git a/docs/manual/tips.tex b/docs/manual/tips.tex
index 9ab15c68..d0767710 100644
--- a/docs/manual/tips.tex
+++ b/docs/manual/tips.tex
@@ -916,9 +916,9 @@ and must change tapes manually.!!!!!
 
 Bacula supports a variety of tape changers through the use of mtx-changer
 scripts/programs. This highly flexible approach allowed me to create 
-\ilink{this shell script}{mtx-changer.txt} which does the following:
-% TODO: This link doesn't work; also need to include this in book appendix
-% TODO: and point to it.
+\elink{this shell script}{http://www.bacula.org/rel-manual/mtx-changer.txt} which does the following:
+% TODO: We need to include this in book appendix and point to it.
+% TODO:
 Whenever a new tape is required it sends a mail to the operator to insert the
 new tape. Then it waits until a tape has been inserted, sends a mail again to
 say thank you and let's bacula continue its backup.
diff --git a/docs/manual/version.tex b/docs/manual/version.tex
index e7695043..7fed0f7f 100644
--- a/docs/manual/version.tex
+++ b/docs/manual/version.tex
@@ -1 +1 @@
-2.0.3 (06 February 2007)
+2.0.3 (16 February 2007)
diff --git a/docs/manual/win32.tex b/docs/manual/win32.tex
index 9c0a570d..9e146292 100644
--- a/docs/manual/win32.tex
+++ b/docs/manual/win32.tex
@@ -186,6 +186,11 @@ get a different (better) antivirus program or use something like
 RunClientJobBefore/After to turn off the antivirus program while
 the backup is running.
 
+If turning off anti-virus software does not resolve your VSS
+problems, you might have to turn on VSS debugging.  The following
+link describes how to do this:
+\elink{http://support.microsoft.com/kb/887013/en-us}{http://support.microsoft.com/kb/887013/en-us}.
+
 The most likely source of problems is authentication when the Director
 attempts to connect to the File daemon that you installed. This can occur if
 the names and the passwords defined in the File daemon's configuration file