\end{description}
\label{CompactingMySQL}
-
\subsection*{Compacting Your MySQL Database}
\index[general]{Database!Compacting Your MySQL }
\index[general]{Compacting Your MySQL Database }
\end{verbatim}
\normalsize
-Alternatively you can modify your /etc/my.conf file and in the
-[mysqld] section set:
+Alternatively you can modify your /etc/my.conf file before creating the
+Bacula tables, and in the [mysqld] section set:
\footnotesize
\begin{verbatim}
\end{verbatim}
\normalsize
-The above row and point size changes should already be the default on MySQL
-version 5.x, so these changes should only be necessary on MySQL 4.x
+The above myisam data pointer size must be made before you create your
+Bacula tables or it will have no effect.
+
+The row and pointer size changes should already be the default on MySQL
+version 5.x, so making these changes should only be necessary on MySQL 4.x
depending on the size of your catalog database.
\item You use {\bf RunBeforeJob} to create the ASCII backup file and {\bf
RunAfterJob} to clean up
- \end{itemize}
+\end{itemize}
Assuming that you start all your nightly backup jobs at 1:05 am (and that they
run one after another), you can do the catalog backup with the following
and/or using tcp wrappers ({\bf etc/hosts.allow}).
\item By default, all data that is sent across the network is unencrypted.
However, Bacula does support TLS (transport layer security) and can
- encrypt transmitted data. Please read \ilink{Data Encryption}{DataEncryption}
+ encrypt transmitted data. Please read the
+ \ilink{TLS (SSL) Communications Encryption}{CommEncryption}
section of this manual.
- built-in.
\item You should ensure that the Bacula working directories are readable and
writable only by the Bacula daemons.
\item If you are using {\bf MySQL} it is not necessary for it to run with