\footnotesize
\begin{verbatim}
-sqlite <path>bacula.db
+sqlite <path>/bacula.db
select * from sqlite_master where type='index' and tbl_name='File';
\end{verbatim}
\normalsize
\footnotesize
\begin{verbatim}
-mysql bacula
+sqlite <path>/bacula.db
CREATE INDEX file_jobid_idx on File (JobId);
CREATE INDEX file_jfp_idx on File (JobId, FilenameId, PathId);
\end{verbatim}
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}