\date{\vspace{1.0in}\today \\
This manual documents Bacula version \input{version} \\
~\vspace{0.2in}\\
- Copyright \copyright 1999-2006, Kern Sibbald \\
+ Copyright \copyright 1999-2006, Free Software Foundation Europe e.V.
+ \\
~\vspace{0.2in}\\
Permission is granted to copy, distribute and/or modify this document under the terms of the \\
GNU Free Documentation License, Version 1.2 published by the Free Software Foundation; \\
+++ /dev/null
-\vspace*{6cm}
-\begin{center}
- \copyright\ Copyright 2000-2005 --\pubyear\ \company
-\end{center}
-
-\begin{center}
- All Rights Reserved
-\end{center}
-
-This publication, or parts thereof, may not be reproduced in any form, by any
-method, for any purpose.
-
-\company\ makes no warranty, either express or implied, including but not
-limited to any implied warranties of merchantability and fitness for a
-particular purpose, regarding these materials and makes such materials
-available solely on an "as-is" basis.
-
-In no event shall \company\ be liable to anyone for special, collateral,
-incidental, or consequential damages in connection with or arising out of
-purchase or use of these materials. The sole and exclusive liability to
-\company\ regardless of the form of action, shall not exceed the purchase
-price of the materials described herein.
-
-For condition of use and permission to use these materials for publication in
-other than the English language, contact \company
-
-\company\ reserves the right to revise and improve its products as it sees
-fit. This publication describes the state of this product as of the time of
-its publication, and may not reflect the product at all times in the future.
-
-This manual was prepared and published in \pubmonth of \pubyear, and is based
-on Release \levelno of \prog.
-
-MS-DOS and Windows are a registered trademarks of Microsoft.
-\clearpage
-\tableofcontents
case), use:
{\bf UseVolumeOnce = yes}.
+
\item To write nnn Jobs to each Volume, use:
{\bf Maximum Volume Jobs = nnn}.
+
\item To limit the maximum size of each Volume, use:
{\bf Maximum Volume Bytes = mmmm}.
+
+ Note, if you use disk volumes, with all versions up to and including
+ 1.39.28, you should probably limit the Volume size to some reasonable
+ value such as say 5GB. This is because during a restore, Bacula is
+ currently unable to seek to the proper place in a disk volume to restore
+ a file, which means that it must read all records up to where the
+ restore begins. If your Volumes are 50GB, reading half or more of the
+ volume could take quite a bit of time. Also, if you ever have a partial
+ hard disk failure, you are more likely to be able to recover more data
+ if they are in smaller Volumes.
+
\item To limit the use time (i.e. write the Volume for a maximum of 5 days),
use:
details and governing text are in the file LICENSE in the main source
directory.
-Most of this code is copyrighted: Copyright \copyright 2000-2004 Kern Sibbald and
-John Walker or Copyright \copyright 2000-2006 Kern Sibbald.
+Most of this code is copyrighted: Copyright \copyright 2000-2006
+Free Software Foundation Europe e.V.
Portions may be copyrighted by other people (ATT, the Free Software
Foundation, ...). Generally these portions are released under a
\addcontentsline{toc}{subsection}{Trademark}
Bacula\raisebox{.6ex}{\textsuperscript{\textregistered}}is a registered
-trademark of Kern Sibbald and John Walker.
+trademark of John Walker.
We have trademarked the Bacula name to ensure that any program using the
name Bacula will be exactly compatible with the program that we have
job) that reads data that was previously backed up to a Volume and writes
it to another Volume. As part of this process, the File catalog records
associated with the first backup job are purged. In other words, Migration
-moves Bacula Job data from one Volume to another. Although we mention
-Volumes to simplify the subject, in reality, Migration reads the data
-from one Volume and writes it to different Volume in a different pool,
-which is equivalent to moving individual Jobs from one Pool to another.
+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.
-Migrations can be based on quite a number of different criteria such as:
+The section process for which Job or Jobs are migrated
+can be based on quite a number of different criteria such as:
\begin{itemize}
\item a single previous Job
\item a Volume
be migrated, with one exception noted below. Also, Bacula permits pools
to contain Volumes with different Media Types. However, when doing
migration, this is a very undesirable condition. For migration to work
-properly, you {\bf must} use pools containing only Volumes of the same
+properly, you should use pools containing only Volumes of the same
Media Type for all migration jobs.
The migration job normally is either manually started or starts
migration:
\begin{itemize}
-\item The currently running Migration control Job
-\item The previous Backup Job (already run)
+\item The currently running Migration control Job. This is only
+ a control job for starting the migration child jobs.
+\item The previous Backup Job (already run). The File records
+ for this Job are purged if the Migration job successfully
+ terminates. The original data remains on the Volume until
+ it is recycled and rewritten.
\item A new Migration Backup Job that moves the data from the
- previous Backup job to the new Volume.
+ previous Backup job to the new Volume. If you subsequently
+ do a restore, the data will be read from this Job.
\end{itemize}
If the Migration control job finds a number of JobIds to migrate (e.g.
it is asked to migrate one or more Volumes), it will start one new
-migration backup job for each JobId found.
+migration backup job for each JobId found on the specified Volumes.
\subsection*{Migration Job Resource Directives}
\addcontentsline{toc}{section}{Migration Job Resource Directives}
on the new medium in the new Pool, but for the most part,
aside from having a new JobId, it will appear with all the
same characteristics of the original job (start, end time, ...).
- The column RealEndTime in the Job table will contain the
+ The column RealEndTime in the catalog Job table will contain the
time and date that the Migration terminated, and by comparing
it with the EndTime column you can tell whether or not the
job was migrated. The original job is purged of its File
a limited amount of debug information about the migration selection
process.
-\item Bacula does not currently do any Storage conflict resolution, so you
+\item Bacula currently does only minimal Storage conflict resolution, so you
must take care to ensure that you don't try to read and write to the
- same device or Bacula will block waiting to reserve a drive that it
+ same device or Bacula may block waiting to reserve a drive that it
will never find. In general, ensure that all your migration
pools contain only one Media Type, and that you always
migrate to pools with different Media Types.
Open Source Software Project (www.ossp.org). It has been adapted and extended
for use in Bacula. This code is now deprecated.
-For all those who I have left out, please send me a reminder, and in any case,
-thanks for your contribution.
+There have been numerous people over the years who have contributed ideas,
+code, and help to the Bacula project. The file AUTHORS in the main source
+release file contains a list of contributors. For all those who I have
+left out, please send me a reminder, and in any case, thanks for your
+contribution.
\subsection*{Copyrights and Trademarks}
\index[general]{Trademarks!Copyrights and }
projects / bacula / docs / commitdiff