From 7b85c8a509d5d648baf96aecca6ab6701af80ca6 Mon Sep 17 00:00:00 2001
From: Eric Bollengier <eric@baculasystems.com>
Date: Mon, 25 Feb 2013 18:16:00 +0100
Subject: [PATCH] Add note for Autochanger handling in 6.0.2

---
 docs/manuals/en/main/newbsfeatures.tex | 86 ++++++++++++++++++++++++++
 1 file changed, 86 insertions(+)

diff --git a/docs/manuals/en/main/newbsfeatures.tex b/docs/manuals/en/main/newbsfeatures.tex
index 5382ec05..96713ab4 100644
--- a/docs/manuals/en/main/newbsfeatures.tex
+++ b/docs/manuals/en/main/newbsfeatures.tex
@@ -284,6 +284,92 @@ don't need to learn about internals of Oracle backup techniques or write
 complex scripts.  The Bacula Enterprise Oracle plugin supports both dump and
 Point In Time Recovery (PITR) with RMAN backup techniques.
 
+
+\section{Bacula Enterprise 6.0.2}
+
+To make Bacula function properly with multiple Autochanger definition in the
+Director configuration, you must adapt your {\bf bacula-dir.conf} {\bf Storage}
+directives.
+
+\smallskip
+Each autochanger that you have defined in an {\bf Autochanger} 
+resource in the Storage daemon's {\bf bacula-sd.conf} file,
+must have a corresponding {\bf Autochanger} resource defined
+in the Director's {\bf bacula-dir.conf} file.  Normally you will
+already have a {\bf Storage} resource that points to the
+Storage daemon's {\bf Autochanger} resource.  Thus you need
+only to change the name of the {\bf Storage} resource to
+{\bf Autochanger}.  In addition no {\bf Autochanger = yes}
+directive is needed in the Director's {\bf Autochanger} resource.
+
+\smallskip
+In addition to the above change ({\bf Storage} to {\bf Autochanger}),
+you must modify any additional {\bf Storage} resources that correspond
+to devices that are part of the {\bf Autochanger} device.
+Instead of the previous {\bf Autochanger = yes} directive they
+should be modified to be {\bf Autochanger = xxx} where you
+replace the {\bf xxx} with the name of the Autochanger.
+
+\smallskip
+For example, in the bacula-dir.conf file:
+
+\begin{verbatim}
+Autochanger {             # New resource
+  Name = Changer-1
+  Address = cibou.company.com
+  SDPort = 9103
+  Password = "xxxxxxxxxx"
+  Device = LTO-Changer-1
+  Media Type = LTO-4
+  Maximum Concurrent Jobs = 50
+}
+
+Storage {
+  Name = Changer-1-Drive0
+  Address = cibou.company.com
+  SDPort = 9103
+  Password = "xxxxxxxxxx"
+  Device = LTO4_1_Drive0
+  Media Type = LTO-4
+  Autochanger = Changer-1  # New directive
+  Maximum Concurrent Jobs = 5
+}
+
+Storage {
+  Name = Changer-1-Drive1
+  Address = cibou.company.com
+  SDPort = 9103
+  Password = "xxxxxxxxxx"
+  Device = LTO4_1_Drive1
+  Media Type = LTO-4
+  Autochanger = Changer-1  # New directive
+  Maximum Concurrent Jobs = 5
+}
+
+...
+\end{verbatim}
+
+Note that Storage resources {\bf Changer-1-Drive0} and 
+{\bf Changer-1-Drive1} are not required since they make
+up part of an autochanger. However, by referring to those
+Storage definitions in a job, you will be sure to use only
+the indicated drive.  This is probably most used for
+reserving a drive for restores.  See the Storage daemon
+example .conf below and the use of {\bf AutoSelect = no}.
+
+So, in summary, the changes are:
+\begin{itemize}
+\item Remove the {\bf Shared Storage = yes} from the {\bf Director}
+resource.
+\item Change {\bf Storage} to {\bf Autochanger} in the LTO4 resource.
+\item Remove the {\bf Autochanger = yes} from the {\bf Autochanger}
+LTO4 resource.
+\item Change the {\bf Autochanger = yes} in each of the {\bf Storage}
+device that belong to the {\bf Autochanger} to point to the
+{\bf Autochanger} resource with for the example above the
+directive {\bf Autochanger = LTO4}.
+\end{itemize}
+
 \section{Bacula Enterprise 6.0.0}
 
 \subsection{Incomplete Jobs}
-- 
2.39.5