From d759b5a930a9c60726b60949349cb18617b15fcd Mon Sep 17 00:00:00 2001
From: Kern Sibbald <kern@sibbald.com>
Date: Tue, 26 Feb 2013 18:19:38 +0100
Subject: [PATCH] Tweak changes to the Autochanger resource

---
 docs/manuals/en/main/newbsfeatures.tex | 29 ++++++++++++++------------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/docs/manuals/en/main/newbsfeatures.tex b/docs/manuals/en/main/newbsfeatures.tex
index 96713ab4..9520fe0c 100644
--- a/docs/manuals/en/main/newbsfeatures.tex
+++ b/docs/manuals/en/main/newbsfeatures.tex
@@ -287,9 +287,9 @@ 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.
+To make Bacula function properly with multiple Autochanger definitions, in
+the Director's configuration, you must adapt your {\bf bacula-dir.conf}
+{\bf Storage} directives.
 
 \smallskip
 Each autochanger that you have defined in an {\bf Autochanger} 
@@ -299,8 +299,10 @@ 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.
+{\bf Autochanger}.  In addition the {\bf Autochanger = yes}
+directive is not needed in the Director's {\bf Autochanger}
+resource, since the resource name is {\bf Autochanger}, the
+Director already knows that it represents an autochanger.
 
 \smallskip
 In addition to the above change ({\bf Storage} to {\bf Autochanger}),
@@ -331,8 +333,8 @@ Storage {
   Password = "xxxxxxxxxx"
   Device = LTO4_1_Drive0
   Media Type = LTO-4
-  Autochanger = Changer-1  # New directive
   Maximum Concurrent Jobs = 5
+  Autochanger = Changer-1  # New directive
 }
 
 Storage {
@@ -342,8 +344,8 @@ Storage {
   Password = "xxxxxxxxxx"
   Device = LTO4_1_Drive1
   Media Type = LTO-4
-  Autochanger = Changer-1  # New directive
   Maximum Concurrent Jobs = 5
+  Autochanger = Changer-1  # New directive
 }
 
 ...
@@ -351,16 +353,17 @@ Storage {
 
 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
+up part of an autochanger, and normally, Jobs refer only
+to the Autochanger resource.
+However, by referring to those
+Storage definitions in a Job, you will use only
+the indicated drive.  This is not normally what
+you want to do, but it is very useful and often 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.
-- 
2.39.5