From: Eric Bollengier Date: Wed, 9 Apr 2008 11:37:10 +0000 (+0000) Subject: ebl update sqlite convertion doc X-Git-Tag: Release-3.0.0~1589 X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=74d47b48f4ae6583966293ead8b4f7fff342139c;p=bacula%2Fdocs ebl update sqlite convertion doc --- diff --git a/docs/manuals/en/catalog/catmaintenance.tex b/docs/manuals/en/catalog/catmaintenance.tex index f0abaa6f..07b1b6b6 100644 --- a/docs/manuals/en/catalog/catmaintenance.tex +++ b/docs/manuals/en/catalog/catmaintenance.tex @@ -524,18 +524,18 @@ Director's configuration file. Note, in the case of SQLite, it is necessary to completely delete (rm) the old database before creating a new compressed version. -\section{Migrating from SQLite to MySQL} +\section{Migrating from SQLite to MySQL or PostgreSQL} \index[general]{MySQL!Migrating from SQLite to } -\index[general]{Migrating from SQLite to MySQL } +\index[general]{Migrating from SQLite to MySQL or PostgreSQL} You may begin using Bacula with SQLite then later find that you want to switch -to MySQL for any of a number of reasons: SQLite tends to use more disk than -MySQL; when the database is corrupted it is often more catastrophic than -with MySQL or PostgreSQL. -Several users have succeeded in converting from SQLite to MySQL by -exporting the MySQL data and then processing it with Perl scripts -prior to putting it into MySQL. This is, however, not a simple -process. +to MySQL or Postgres for any of a number of reasons: SQLite tends to use more +disk than MySQL; when the database is corrupted it is often more catastrophic +than with MySQL or PostgreSQL. Several users have succeeded in converting by +exporting the SQLite data and then processing it with Perl scripts prior to +putting it into MySQL or PostgreSQL. This is, however, not a simple process. +Scripts are available on bacula source distribution under +\texttt{examples/database}. \label{BackingUpBacula} \section{Backing Up Your Bacula Database}