From 9839032c94341fdc55d8f86aa0517ce945b9722b Mon Sep 17 00:00:00 2001 From: Joerg Steffens Date: Wed, 11 Jan 2017 16:45:21 +0100 Subject: [PATCH] cleanup --- manuals/en/main/migration.tex | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/manuals/en/main/migration.tex b/manuals/en/main/migration.tex index 83aba93e169..6f1c4f2b617 100644 --- a/manuals/en/main/migration.tex +++ b/manuals/en/main/migration.tex @@ -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 @@ -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}