From: Eric Bollengier Date: Fri, 24 Oct 2008 09:14:19 +0000 (+0000) Subject: ebl update copy doc X-Git-Tag: Release-3.0.0~714 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=43ab8aadad0e75d077738a012435ed282168288b;p=bacula%2Fdocs ebl update copy doc --- diff --git a/docs/manuals/en/concepts/migration.tex b/docs/manuals/en/concepts/migration.tex index b487c0a8..80d695ed 100644 --- 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