StorageDaemon.
The normal way to handle this situation is to use a canonical name such as
-``storage-server'' that will be resolved on the Director side as the WAN address
-and on the Client side as the LAN address. This is now possible to configure
-this parameter using the new \texttt{FDStorageAddress} Storage
-% or Client
-directive.
+``storage-server'' that will be resolved on the Director side as the WAN
+address and on the Client side as the LAN address. This is now possible to
+configure this parameter using the new directive \texttt{FDStorageAddress} in
+the Storage or Client resource.
+
\bsysimageH{BackupOverWan1}{Backup Over WAN}{figbs6:fdstorageaddress}
% \label{fig:fdstorageaddress}
Name = storage1
Address = 65.1.1.1
FD Storage Address = 10.0.0.1
- SD Port 9103
+ SD Port = 9103
...
}
\end{lstlisting}
% # or in the Client resouce
%
-% Client {
-% Name = client1
-% Address = 65.1.1.2
-% FD Storage Address = 10.0.0.1
-% FD Port 9103
-% ...
-% }
-% \end{lstlisting}
-%
-% Note that using the Client \texttt{FDStorageAddress} directive will not allow
-% to use multiple Storage Daemon, all Backup or Restore requests will be sent to
-% the specified \texttt{FDStorageAddress}.
+
+\begin{lstlisting}
+ Client {
+ Name = client1
+ Address = 65.1.1.2
+ FD Storage Address = 10.0.0.1
+ FD Port = 9102
+ ...
+ }
+\end{lstlisting}
+
+Note that using the Client \texttt{FDStorageAddress} directive will not allow
+to use multiple Storage Daemon, all Backup or Restore requests will be sent to
+the specified \texttt{FDStorageAddress}.
\subsection{Maximum Concurrent Read Jobs}
This is a new directive that can be used in the {\bf bacula-dir.conf} file