Update

[bacula/docs] / docs / manual / dirdconf.tex

diff --git a/docs/manual/dirdconf.tex b/docs/manual/dirdconf.tex
index 50cef84693643db023a68c515533c527a1cce8c6..eb038e2103b3e68a78af50af25e51212994fd90e 100644 (file)
--- a/docs/manual/dirdconf.tex
+++ b/docs/manual/dirdconf.tex
@@ -1515,12 +1515,9 @@ RunScript {
    run = "Nightly-backup level=%l since=\"%s\" storage=DDS-4"
 \end{verbatim}
 
-
    A cloned job will not start additional clones, so it is not
    possible to recurse.
 
-   
-
 \label{Priority}
 \item [Priority = \lt{}number\gt{}]
    \index[dir]{Priority}
@@ -2604,9 +2601,21 @@ The Pool Resource defined in the Director's configuration file
 \item [RecyclePool = \lt{}pool-resource-name\gt{}]
    \index[dir]{RecyclePool}
    \index[dir]{Directive!RecyclePool}
-
-   On versions 2.1.4 or greater, Bacula can recycle media in the pool of your
-   choice. The most useful setup is to use \ilink{Scratch}{TheScratchPool}.
+   On versions 2.1.4 or greater, this directive defines to which pool
+   the Volume will be placed (moved) when it is recycled. Without
+   this directive, a Volume will remain in the same pool when it is
+   recycled. With this directive, it can be moved automatically to any
+   existing pool during a recycle. This directive is probably most
+   useful when defined in the Scratch pool, so that volumes will
+   be recycled back into the Scratch pool. For more on the see the   
+   \ilink{Scratch Pool}{TheScratchPool} section of this manual.
+
+   Although this directive is called RecyclePool, the Volume in
+   question is actually moved from its current pool to the one
+   you specify on this directive when Bacula prunes the Volume and
+   discovers that there are no records left in the catalog and hence
+   marks it as {\bf Purged}.
+        
    
 \label{PoolRecycle}
 \item [Recycle = \lt{}yes|no\gt{}]