Skip to content
This repository has been archived by the owner on Mar 19, 2021. It is now read-only.

Commit

Permalink
cleanup
Browse files Browse the repository at this point in the history
  • Loading branch information
joergsteffens committed Jan 11, 2017
1 parent ce21dbf commit 9839032
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions manuals/en/main/migration.tex
Expand Up @@ -116,25 +116,22 @@ \section{Important Migration Considerations}
read and write the same Volume from two jobs at the same time.

\item Migration works only if the Job resource of the original Job is
still defined in the current director configuration. Otherwise
still defined in the current Director configuration. Otherwise
you'll get a fatal error.

\item Setting the Migration High Bytes watermark is not sufficient
\item Setting the \linkResourceDirective{Dir}{Pool}{Migration High Bytes} watermark is not sufficient
for migration to take place. In addition, you must define
and schedule a migration job which looks for jobs that can
be migrated.

\item To figure out which jobs are going to be migrated by a given
configuration, choose a debug level of 100 or more. This
activates information about the migration selection process.

\item Bareos 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 Bareos may block waiting to reserve a drive that it
will never find. In general, ensure that all your migration
will never find.
A way to prevent problems is that all your migration
pools contain only one \linkResourceDirective{Dir}{Storage}{Media Type},
and that you always
migrate to pools with different Media Types.
migrate to a pool with a different Media Type.

\item The \linkResourceDirective{Dir}{Pool}{Next Pool} = ... directive must be defined in the Pool
referenced in the Migration Job to define the Pool into which the
Expand All @@ -144,6 +141,10 @@ \section{Important Migration Considerations}
selection types. All other selection types (time, occupancy,
smallest, oldest, ...) are experimental features.

\item To figure out which jobs are going to be migrated by a given
configuration, choose a debug level of 100 or more. This
activates information about the migration selection process.

\end{itemize}

\section{Configure Copy or Migration Jobs}
Expand Down

0 comments on commit 9839032

Please sign in to comment.