ebl Add info about copies

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index af036b088f4b59091aa566c45b2b7a201dcf4985..9362b1b4814fb70388b6dc127d39a6e278722ca8 100644 (file)
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -47,6 +47,29 @@ copy jobs and allows selection of copies by using \texttt{jobid=}
 option. If the keyword {\bf copies} is present on the command line, Bacula will
 display the list of all copies for selected jobs.
 
+\begin{verbatim}
+* restore copies
+[...]
+These JobIds have copies as follows:
++-------+------------------------------------+-----------+------------------+
+| JobId | Job                                | CopyJobId | MediaType        |
++-------+------------------------------------+-----------+------------------+
+| 2     | CopyJobSave.2009-02-17_16.31.00.11 | 7         | DiskChangerMedia |
++-------+------------------------------------+-----------+------------------+
++-------+-------+----------+----------+---------------------+------------------+
+| JobId | Level | JobFiles | JobBytes | StartTime           | VolumeName       |
++-------+-------+----------+----------+---------------------+------------------+
+| 19    | F     | 6274     | 76565018 | 2009-02-17 16:30:45 | ChangerVolume002 |
+| 2     | I     | 1        | 5        | 2009-02-17 16:30:51 | FileVolume001    |
++-------+-------+----------+----------+---------------------+------------------+
+You have selected the following JobIds: 19,2
+
+Building directory tree for JobId(s) 19,2 ...  ++++++++++++++++++++++++++++++++++++++++++++
+5,611 files inserted into the tree.
+...
+\end{verbatim}
+
+
 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. See the Migration
 documentation for additional details. For copy Jobs there is a new selection
@@ -416,7 +439,7 @@ fail with an error.
 \section{Catalog format}
 Bacula 3.0 comes with some changes on the catalog format. The upgrade operation
 will convert an essential field of the File table that permits to handle more
-than 4 billions objects over the time, and this operation will take TIME and
+than 4 billion objects over the time, and this operation will take TIME and
 will DOUBLE THE SIZE of your catalog temporarily. Depending on your catalog
 backend, you won't be able to run jobs during this period. For example, a 3
 million files catalog will take 2mins to upgrade on a normal machine. Don't