added statistics chapter

diff --git a/docs/manuals/de/concepts/concepts.tex b/docs/manuals/de/concepts/concepts.tex
index 962f6e4e7104982811fa4dd78d5b748d1556d1a3..90f3b8206978aa4717ddc226da3d8970b58bafdc 100644 (file)
--- a/docs/manuals/de/concepts/concepts.tex
+++ b/docs/manuals/de/concepts/concepts.tex
@@ -90,6 +90,7 @@
 \include{autochangers}
 \include{supportedchangers}
 \include{spooling}
+\include{statistics}
 \include{python}
 \include{ansi-labels}
 \include{win32}

diff --git a/docs/manuals/de/concepts/statistics.tex b/docs/manuals/de/concepts/statistics.tex
new file mode 100644 (file)
index 0000000..57bca3b
--- /dev/null
+++ b/docs/manuals/de/concepts/statistics.tex
@@ -0,0 +1,61 @@
+\chapter{Using Bacula catalog to grab information}
+\label{UseBaculaCatalogToExtractInformationChapter}
+\index[general]{Statistics}
+
+Bacula catalog contains lot of information about your IT infrastructure, how
+many files, their size, the number of video or music files etc. Using Bacula
+catalog during the day to get them permit to save resources on your servers.
+
+In this chapter, you will find tips and information to measure bacula
+efficiency and report statistics.
+
+\section{Job statistics}
+If you (or probably your boss) want to have statistics on your backups to
+provide some \textit{Service Level Agreement} indicators, you could use a few
+SQL queries on the Job table to report how many:
+
+\begin{itemize}
+\item jobs have run
+\item jobs have been successful
+\item files have been backed up
+\item ...
+\end{itemize}
+
+However, these statistics are accurate only if your job retention is greater
+than your statistics period. Ie, if jobs are purged from the catalog, you won't
+be able to use them. 
+
+Now, you can use the \textbf{update stats [days=num]} console command to fill
+the JobHistory table with new Job records. If you want to be sure to take in
+account only \textbf{good jobs}, ie if one of your important job has failed but
+you have fixed the problem and restarted it on time, you probably want to
+delete the first \textit{bad} job record and keep only the successful one. For
+that simply let your staff do the job, and update JobHistory table after two or
+three days depending on your organization using the \textbf{[days=num]} option.
+
+These statistics records aren't used for restoring, but mainly for
+capacity planning, billings, etc.
+
+The Bweb interface provides a statistics module that can use this feature. You
+can also use tools like Talend or extract information by yourself.
+
+The {\textbf Statistics Retention = \lt{}time\gt{}} director directive defines
+the length of time that Bacula will keep statistics job records in the Catalog
+database after the Job End time. (In \texttt{JobHistory} table) When this time
+period expires, and if user runs \texttt{prune stats} command, Bacula will
+prune (remove) Job records that are older than the specified period.
+
+You can use the following Job resource in your nightly \textbf{BackupCatalog}
+job to maintain statistics.
+\begin{verbatim}
+Job {
+  Name = BackupCatalog
+  ...
+  RunScript {
+    Console = "update stats days=3"
+    Console = "prune stats yes"
+    RunsWhen = After
+    RunsOnClient = no
+  }
+}
+\end{verbatim}