release notes and some cleanups

manuals/en/main/catmaintenance.tex

@@ -728,16 +728,6 @@ \subsubsection{Job statistics}
 
 \section{PostgreSQL}
 
-\label{RepairingPSQL}
-\subsection{Repairing Your PostgreSQL Database}
-\index[general]{Database!Repairing Your PostgreSQL}
-\index[general]{Repairing Your PostgreSQL Database}
-
-The same considerations apply that are indicated above for MySQL. That is,
-consult the PostgreSQL documents for how to repair the database, and also
-consider using \command{bareos-dbcheck} program if the conditions are reasonable for
-using (see above).
-
 \subsection{Compacting Your PostgreSQL Database}
 \index[general]{Database!Compacting Your PostgreSQL}
 \index[general]{Compacting Your PostgreSQL Database}
@@ -771,13 +761,11 @@ \subsection{Compacting Your PostgreSQL Database}
 For a {\bf PostgreSQL} database, you could write the Bareos database as an
 ASCII file (\texttt{bareos.sql}) then reload it by doing the following:
 
-\footnotesize
-\begin{verbatim}
+\begin{commands}{}
 pg_dump -c bareos > bareos.sql
 cat bareos.sql | psql bareos
 rm -f bareos.sql
-\end{verbatim}
-\normalsize
+\end{commands}
 
 Depending on the size of your database, this will take more or less time and a
 fair amount of disk space. For example, you can {\bf cd} to the location of
@@ -799,6 +787,7 @@ \subsection{Compacting Your PostgreSQL Database}
 for the current PostgreSQL version.
 
 \subsubsection{What To Do When The Database Keeps Growing}
+\label{PostgresSize}
 Especially when a high number of files are beeing backed up or when working with
 high retention periods, it is probable that autovacuuming will not work.
 When starting to use Bareos with an empty Database, it is normal that the file
@@ -937,11 +926,27 @@ \subsubsection{What To Do When The Database Keeps Growing}
 \end{enumerate}
 
 
+\subsection{Repairing Your PostgreSQL Database}
+\label{RepairingPSQL}
+\index[general]{Database!Repairing Your PostgreSQL}
+\index[general]{Repairing Your PostgreSQL Database}
+
+The same considerations apply as for \nameref{RepairingMySQL}.
+Consult the PostgreSQL documents for how to repair the database.
+
+For Bareos specific problems, 
+consider using \nameref{bareos-dbcheck} program .
+
+
+
+
 \section{MySQL}
-\label{CompactingMySQL}
+
+
 \subsection{Compacting Your MySQL Database}
 \index[general]{Database!Compacting Your MySQL}
 \index[general]{Compacting Your MySQL Database}
+\label{CompactingMySQL}
 
 Over time, as noted above, your database will tend to grow.
 Even though Bareos regularly prunes files, {\bf MySQL} does not automatically
@@ -977,11 +982,10 @@ \subsection{Compacting Your MySQL Database}
 Depending on the size of your database, this will take more or less time and a
 fair amount of disk space.
 
-\label{DatabaseRepair}
-\label{RepairingMySQL}
 \subsection{Repairing Your MySQL Database}
 \index[general]{Database!Repairing Your MySQL}
 \index[general]{Repairing Your MySQL Database}
+\label{RepairingMySQL}
 
 If you find that you are getting errors writing to your MySQL database, or
 Bareos hangs each time it tries to access the database, you should consider
@@ -1003,6 +1007,7 @@ \subsection{Repairing Your MySQL Database}
 such a case, you will need to create additional space on the partition.
 
 
+
 \subsection{MySQL Table is Full}
 \index[general]{Database!MySQL Table is Full}
 \index[general]{MySQL Table is Full}
@@ -1132,7 +1137,7 @@ \section{Performance Issues Indexes}
 \index[general]{Database Performance Issues Indexes}
 \index[general]{Performance!Database}
 
-\TODO{Is chapter needs verification/updating (by Stephan).}
+\TODO{This chapter needs verification/updating.}
 
 One of the most important considerations for improving performance on
 the Bareos database is to ensure that it has all the appropriate indexes.

manuals/en/main/releasenotes.tex

@@ -17,11 +17,19 @@ \section*{Bareos-14.2}
 It is known, that \command{drop_database} scripts will not longer work on PostgreSQL $<$ 8.4. However, as \command{drop_database} scripts are very seldom needed, package dependencies do not yet enforce PostgreSQL $>=$ 8.4.
 We plan to ensure this in future version of Bareos.
 
+\releasenote{14.2.3}{
+
+\begin{tabular}{p{0.2\textwidth} p{0.8\textwidth}}
+Code Release      & 2015-02-02 \\
+Database Version: & 2003 (unchanged)\\
+\end{tabular}
+}
+
 \releasenote{14.2.2}{
 
 \begin{tabular}{p{0.2\textwidth} p{0.8\textwidth}}
 Code Release      & 2014-12-12 \\
-Database Version: & 2003\\
+Database Version: & 2003 (unchanged)\\
                   & Database update required if updating from version $<$ 14.2.\\
                   & See the \nameref{bareos-update} section for details.\\
 \end{tabular}
@@ -42,6 +50,14 @@ \section*{Bareos-14.2}
 
 \section*{Bareos-13.2}
 
+\releasenote{13.2.4}{
+
+\begin{tabular}{p{0.2\textwidth} p{0.8\textwidth}}
+Code Release & 2014-11-05 \\
+Database Version: & 2002 (unchanged)\\
+\end{tabular}
+}
+
 \releasenote{13.2.3}{
 
 \begin{tabular}{p{0.2\textwidth} p{0.8\textwidth}}

manuals/en/main/troubleshooting.tex

@@ -454,8 +454,8 @@ \subsection{Restoring When Things Go Wrong}
 \item[Solution]
    For SQLite, use the vacuum command to try to fix the database. For either
    MySQL or PostgreSQL, see the vendor's documentation. They have specific tools
-   that check and repair databases, see the \ilink{database
-   repair}{DatabaseRepair} sections of this manual for links to vendor
+   that check and repair databases, see the \nameref{CatMaintenanceChapter} sections 
+   of this manual for links to vendor
    information.
 
    Assuming the above does not resolve the problem, you will need to restore