ebl update copy doc

diff --git a/docs/manuals/en/concepts/migration.tex b/docs/manuals/en/concepts/migration.tex
index b487c0a8b01db8f97ab666d66f00d00c643b0172..80d695ed50cfd3dcdd0c5f03d8e4bd81fb192a2b 100644 (file)
--- a/docs/manuals/en/concepts/migration.tex
+++ b/docs/manuals/en/concepts/migration.tex
@@ -79,7 +79,7 @@ a number of volumes for migration, you may have a large number of
 Jobs that start. Because each job must read the same Volume, they will
 run consecutively (not simultaneously).
 
-\section{Migration Job Resource Directives}
+\section{Migration and Copy Job Resource Directives}
 
 The following directives can appear in a Director's Job resource, and they
 are used to define a Migration job.          
@@ -101,6 +101,14 @@ are used to define a Migration job.
     an Admin job.  Migration jobs simply check to see if there is anything to
    Migrate then possibly start and control new Backup jobs to migrate the data
    from the specified Pool to another Pool.
+
+\item [Type = Copy]
+   {\bf Copy} is a new type that defines the job that is run as being a
+   Copy Job.  A Copy Job is a sort of control job and does not have
+   any Files associated with it, and in that sense they are more or less like
+    an Admin job.  Copy jobs simply check to see if there is anything to
+   Copy then possibly start and control new Backup jobs to copy the data
+   from the specified Pool to another Pool.
  
 \item [Selection Type = \lt{}Selection-type-keyword\gt{}]  
   The \lt{}Selection-type-keyword\gt{} determines how the migration job