From: Eric Bollengier <eric@eb.homelinux.org>
Date: Fri, 3 Oct 2008 08:52:26 +0000 (+0000)
Subject: ebl  Update doc about statistics
X-Git-Tag: Release-3.0.0~895
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=f821ec12bf83395fc8e5d234b92c2d88f2fdee7e;p=bacula%2Fdocs

ebl  Update doc about statistics
---

diff --git a/docs/manuals/en/concepts/newfeatures.tex b/docs/manuals/en/concepts/newfeatures.tex
index 9b067533..f8e1d7ef 100644
--- a/docs/manuals/en/concepts/newfeatures.tex
+++ b/docs/manuals/en/concepts/newfeatures.tex
@@ -626,17 +626,19 @@ when the job was scheduled. This can be useful to prevent jobs from running
 during working hours. We can see it like \texttt{Max Start Delay + Max Run
   Time}.
 
-\item [Max Wait Time]
+\item [Max Wait Time] 
+
 Previous \textbf{MaxWaitTime} directives aren't working as expected, instead
 of checking the maximum allowed time that a job may block for a resource,
-those directives worked like \textbf{MaxRunTime}. Some users are reporting to use
-\textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of their job
-depending on the level. Now, they have to use \textbf{Incr/Diff/Full Max Run Time}.
-\textbf{Incr/Diff/Full Max Wait Time} directives are now deprecated.
+those directives worked like \textbf{MaxRunTime}. Some users are reporting to
+use \textbf{Incr/Diff/Full Max Wait Time} to control the maximum run time of
+their job depending on the level. Now, they have to use
+\textbf{Incr/Diff/Full Max Run Time}.  \textbf{Incr/Diff/Full Max Wait Time}
+directives are now deprecated.
 
 \item [Incremental|Differential Max Wait Time = \lt{}time\gt{}] 
-Theses directives have been deprecated in favor of \texttt{Incremental|Differential
-Max Run Time}.
+Theses directives have been deprecated in favor of
+\texttt{Incremental|Differential Max Run Time}.
 
 \item [Max Run Time directives]
 Using \textbf{Full/Diff/Incr Max Run Time}, it's now possible to specify the
@@ -646,8 +648,11 @@ maximum allowed time that a job can run depending on the level.
 \includegraphics{\idir different_time.eps}
 
 \item [Statistics Enhancements]
-If you (or your boss) want to have statistics on your backups, you could use
-a few SQL queries on the Job table to report how many:
+
+If you (or probably your boss) want to have statistics on your backups to
+provide some sort of \textit{Servce Level Agreement} indicators, you could use
+few SQL queries on the Job table to report how many:
+
 \begin{itemize}
 \item jobs have run
 \item jobs have been successful
@@ -655,12 +660,23 @@ a few SQL queries on the Job table to report how many:
 \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.
+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 JobStat table with new Job records. If you want to be sure to take in
+account only \textbi{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 JobStat table after two or
+three days depending on your organization using the \textbf{[days=num]} option.
+
+These statistics records aren't used for restore purpose, but mainly for
+capacity planning, billings, etc.
 
-Now, you can use the \textbf{update stats [days=num]} console command to fill the
-JobStat table with new Job records.
+The Bweb interface provide 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
@@ -668,9 +684,6 @@ database after the Job End time. (In \texttt{JobStat} 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.
 
-These statistics records aren't used for restore purpose, but mainly for
-capacity planning, billings, etc.
-
 You can use the following Job resource in your nightly \textbf{BackupCatalog}
 job to maintain statistics.
 \begin{verbatim}