Skip to content

Commit

Permalink
migration: mark resources by latex commands
Browse files Browse the repository at this point in the history
  • Loading branch information
joergsteffens committed Dec 9, 2015
1 parent adf2e82 commit 0f6ebd5
Show file tree
Hide file tree
Showing 2 changed files with 22 additions and 16 deletions.
2 changes: 2 additions & 0 deletions manuals/en/main/bareos.sty
Expand Up @@ -143,6 +143,7 @@
\newcommand{\command}[1]{\path|#1|}
% to also link to a directive, use \linkResourceDirective}{Dir|Sd|Fd}{Resource}{Directive Name}
\newcommand{\configdirective}[1]{\textbf{#1}}
\newcommand{\configresource}[1]{\path|#1|}
\newcommand{\configline}[1]{\path|#1|}
\newcommand{\directory}[1]{\path|#1|}
\newcommand{\email}[1]{\url{#1}}
Expand All @@ -159,6 +160,7 @@
\newcommand{\pluginevent}[1]{\path|#1|}
\newcommand{\pool}[1]{\path|#1|}
\newcommand{\argument}[1]{\textit{#1}}
\newcommand{\resourcename}[1]{\path|#1|}
\newcommand{\registrykey}[1]{\path|#1|}
\newcommand{\variable}[1]{\path|#1|}
\newcommand{\volume}[1]{\path|#1|}
Expand Down
36 changes: 20 additions & 16 deletions manuals/en/main/migration.tex
Expand Up @@ -237,15 +237,17 @@ \subsection{Example Migration Jobs}
}
\end{bconfig}

Note that the backup job writes to the {\tt Default} pool, which
corresponds to {\tt File} storage. There is no {\tt Storage} directive
in the Job resource while the two {\tt Pool} resources contain
different {\tt Storage} directives. Moreover, the {\tt Default}
pool contains a {\tt Next Pool} directive that refers to the {\tt
Tape} pool.

In order to migrate jobs from the Default pool to the Tape pool we
add the following Job resource:
Note that the backup job writes to the \pool{Default} pool, which
corresponds to \resourcename{File} storage. There is no
\linkResourceDirective{Dir}{Pool}{Storage} directive
in the Job resource while the two \configresource{Pool} resources contain
different \linkResourceDirective{Dir}{Pool}{Storage} directives.
Moreover, the \pool{Default}
pool contains a \linkResourceDirective{Dir}{Pool}{Next Pool} directive
that refers to the \pool{Tape} pool.

In order to migrate jobs from the \pool{Default} pool to the \pool{Tape} pool
we add the following Job resource:

\begin{bconfig}{migrate all volumes of a pool}
Job {
Expand All @@ -258,12 +260,14 @@ \subsection{Example Migration Jobs}
}
\end{bconfig}

The {\bf Selection Type} and {\bf Selection pattern} directives
instruct Bareos to select all volumes of the given pool ({\bf Default})
whose volume names match the given regular expression ({\bf "."}),
The \linkResourceDirective{Dir}{Job}{Selection Type} and
\linkResourceDirective{Dir}{Job}{Selection Pattern} directives
instruct Bareos to select all volumes of the given pool (\pool{Default})
whose volume names match the given regular expression (\argument{"."}),
i.e., all volumes. Hence those jobs which were backed up to any volume
in the {\bf Default} pool will be migrated. Because of the {\bf Next
Pool} directive of the {\bf Default} pool resource, the jobs will be
in the \pool{Default} pool will be migrated. Because of the
\linkResourceDirective{Dir}{Pool}{Next Pool} directive
of the \pool{Default} pool resource, the jobs will be
migrated to tape storage.

Another way to accomplish the same is the following Job resource:
Expand All @@ -279,8 +283,8 @@ \subsection{Example Migration Jobs}
}
\end{bconfig}

This migrates all jobs ending with {\bf Save} from the {\bf Default}
pool to the {\bf Tape} pool, i.e., from File storage to Tape storage.
This migrates all jobs ending with \argument{Save} from the \pool{Default}
pool to the \pool{Tape} pool, i.e., from File storage to Tape storage.

\subsubsection{Multiple Storage Daemons}
\label{sec:CopyMigrationJobsMultipleStorageDaemons}
Expand Down

0 comments on commit 0f6ebd5

Please sign in to comment.