From: Eric Bollengier <eric@eb.homelinux.org>
Date: Fri, 24 Oct 2008 09:11:20 +0000 (+0000)
Subject: ebl  Add docs about Copy
X-Git-Tag: Release-3.0.0~715
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=90b0027c4fc3627e372384697703411cd41f041b;p=bacula%2Fdocs

ebl  Add docs about Copy
---

diff --git a/docs/manuals/en/concepts/migration.tex b/docs/manuals/en/concepts/migration.tex
index b0d49df2..b487c0a8 100644
--- a/docs/manuals/en/concepts/migration.tex
+++ b/docs/manuals/en/concepts/migration.tex
@@ -1,7 +1,8 @@
 
-\chapter{Migration}
+\chapter{Migration and Copy}
 \label{MigrationChapter}
 \index[general]{Migration} 
+\index[general]{Copy} 
 
 The term Migration, as used in the context of Bacula, means moving data from
 one Volume to another.  In particular it refers to a Job (similar to a backup
@@ -12,6 +13,12 @@ moves Bacula Job data from one Volume to another by reading the Job data
 from the Volume it is stored on, writing it to a different Volume in a
 different Pool, and then purging the database records for the first Job.
 
+The Copy process is essentially identical to the Migration feature
+with the exception that the Job that is copied is left unchanged.  This
+essentially creates two identical copies of the same backup.  The Copy Job runs
+without using the File daemon by copying the data from the old backup Volume to
+a different Volume in a different Pool.
+
 The section process for which Job or Jobs are migrated
 can be based on quite a number of different criteria such as:
 \begin{itemize}