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

Commit

Permalink
NDMP_NATIVE
Browse files Browse the repository at this point in the history
  • Loading branch information
joergsteffens committed Sep 1, 2017
1 parent 2e08762 commit 96c2c88
Show file tree
Hide file tree
Showing 7 changed files with 1,102 additions and 115 deletions.
2 changes: 1 addition & 1 deletion manuals/en/main/always-incremental.tex
Expand Up @@ -131,7 +131,7 @@ \subsection{Consolidate Job}
\warning{All Bareos job resources have some required directives, e.g. \linkResourceDirective{Dir}{Job}{Client}.
Even so, none other than the mentioned directives are evaluated by a \resourceDirectiveValue{Dir}{Job}{Type}{Consolidate},
they still have to be defined.
Normally all required directives are already set in \resourceDirectiveValue{Dir}{Job}{JobDefs}{DefaultJob}.
Normally all required directives are already set in \resourceDirectiveValue{Dir}{Job}{Job Defs}{DefaultJob}.
If not, you have to add them. You can use arbitrary, but valid values.}


Expand Down
12 changes: 12 additions & 0 deletions manuals/en/main/bareos.sty
Expand Up @@ -23,6 +23,8 @@
% therefore use \textasciicircum instead.
% However, ^ works inside verbatim and lst environments.

\newcommand{\subsubsubsection}[1]{\paragraph{#1}}

\newcommand{\bareosFd}{Bareos File Daemon\xspace}
\newcommand{\bareosSd}{Bareos Storage Daemon\xspace}
\newcommand{\bareosDir}{Bareos Director\xspace}
Expand Down Expand Up @@ -76,6 +78,7 @@
\csdef{dtPath}{\ilink{path}{DataTypePath}}
% use csdef instead of newcommand, because command contains numbers
\csdef{dtPint32}{\dtUInt}
\csdef{dtProtocolType}{\ilink{job protocol}{DataTypeJobProtocol}}
\csdef{dtRes}{\ilink{resource-name}{DataTypeRes}}
\csdef{dtPort}{\dtNetPort}
\csdef{dtScheduleRunCommand}{{job-overrides{\gt} {\lt}date-time-specification}}
Expand Down Expand Up @@ -258,6 +261,15 @@
\newcommand{\vmware}{VMware\registered}
\newcommand{\vSphere}{VMware vSphere\registered}

% NDMP
\newcommand{\DataManagementAgent}{Data Management Agent\xspace}
\newcommand{\DataAgent}{Data Agent\xspace}
\newcommand{\TapeAgent}{Tape Agent\xspace}
\newcommand{\RobotAgent}{Robot Agent\xspace}

\newcommand{\NdmpBareos}{NDMP\_BAREOS}
\newcommand{\NdmpNative}{NDMP\_NATIVE}

% Bareos quote
\newcommand{\bquote}[1]{``#1''}
%%
Expand Down
14 changes: 14 additions & 0 deletions manuals/en/main/configure.tex
Expand Up @@ -593,6 +593,20 @@ \subsubsection{Data Types}
Don't use quotes around the number, see \nameref{sec:Quotes}.
\item [job protocol]
\index[general]{Data Type!job protocol}
\label{DataTypeJobProtocol}
The protocol to run a the job.
Following protocols are available:
\begin{description}
\item[Native] Native Bareos job protocol.
\item[NDMP] Deprecated. Alias for \NdmpBareos.
\item[NDMP\_BAREOS] Since Bareos \sinceVersion{dir}{NDMP BAREOS}{17.2.3}. See \nameref{sec:NdmpBareos}.
\item[NDMP\_NATIVE] Since Bareos \sinceVersion{dir}{NDMP NATIVE}{17.2.3}. See \nameref{sec:NdmpNative}.
\end{description}
\item [name]
\index[general]{Data Type!name}
Expand Down
7 changes: 1 addition & 6 deletions manuals/en/main/director-resource-job-definitions.tex
Expand Up @@ -775,12 +775,7 @@
}

\defDirective{Dir}{Job}{Protocol}{}{}{%
The backup protocol to use to run the Job. If not set it will default
to {\bf Native} currently the director understand the following protocols:
\begin{enumerate}
\item Native - The native Bareos protocol
\item NDMP - The NDMP protocol
\end{enumerate}
The backup protocol to use to run the Job. See \dtProtocolType.
}

\defDirective{Dir}{Job}{Prune Files}{}{}{%
Expand Down
14 changes: 9 additions & 5 deletions manuals/en/main/director-resource-storage-definitions.tex
Expand Up @@ -45,19 +45,23 @@
}

\defDirective{Dir}{Storage}{Device}{}{}{%
This directive refers to a \linkResourceDirective{Sd}{Device}{Name}
or \linkResourceDirective{Sd}{Autochanger}{Name}.

If \linkResourceDirective{Dir}{Job}{Protocol} is not \parameter{NDMP_NATIVE} (default is \linkResourceDirectiveValue{Dir}{Job}{Protocol}{Native}), this directive refers to one or multiple \linkResourceDirective{Sd}{Device}{Name}
or a single \linkResourceDirective{Sd}{Autochanger}{Name}.

If an Autochanger should be used, it had to refer to a configured \linkResourceDirective{Sd}{Autochanger}{Name}.
In this case, also set \linkResourceDirectiveValue{Dir}{Storage}{Auto Changer}{yes}.

In all other cases, refer to a configured \linkResourceDirective{Sd}{Device}{Name}.
Otherwise it refers to one or more configured \linkResourceDirective{Sd}{Device}{Name}, see \nameref{sec:MultipleStorageDevices}.

This
name is not the physical device name, but the logical device name as
This name is not the physical device name, but the logical device name as
defined in the \bareosSd resource.

If \resourceDirectiveValue{Dir}{Job}{Protocol}{NDMP_NATIVE}, it refers to tape devices on the NDMP \TapeAgent, see \nameref{sec:NdmpNative}.
}



\defDirective{Dir}{Storage}{Enabled}{}{}{%
}

Expand Down
4 changes: 4 additions & 0 deletions manuals/en/main/disk.tex
Expand Up @@ -455,6 +455,10 @@ \subsection{Example for two clients, separate devices and recycling}
\subsection{Using Multiple Storage Devices}
\label{sec:MultipleStorageDevices}
\index[general]{Multiple Storage Devices}
\index[general]{Storage Device!Multiple}
Bareos treats disk volumes similar to tape volumes as much as it can.
This means that you can only have a single Volume mounted at one time on a disk as defined in your \resourcetype{Sd}{Device} resource.
Expand Down

0 comments on commit 96c2c88

Please sign in to comment.