Installing and Configuring SQLite

Bacula 1.34 User's Guide |
Installing and Configuring PostgreSQL | Index | Internal Bacula Database
# Installing and Configuring SQLite ## Installing and Configuring SQLite -- Phase I If you use the ./configure --with-sqlite statement for configuring Bacula, you will need SQLite version 2.2.3 or later installed. Our standard location (for the moment) for SQLite is in the dependency package depkgs/sqlite-2.2.3. Please note that the version will be updated as new versions are available and tested. Installing and Configuring is quite easy. Download the Bacula dependency packages Detar it with something like: tar xvfz depkgs.tar.gz Note, the above command requires GNU tar. If you do not have GNU tar, a command such as: zcat depkgs.tar.gz | tar xvf - will probably accomplish the same thing. cd depkgs make sqlite At this point, you should return to completing the installation of Bacula. Please note that the ./configure used to build Bacula will need to include --with-sqlite. ## Installing and Configuring SQLite -- Phase II This phase is done after you have run the ./configure command to configure Bacula. Bacula will install scripts for manipulating the database (create, delete, make tables etc) into the main installation directory. These files will be of the form *_bacula_* (e.g. create_bacula_database). These files are also available in the <bacula-src>/src/cats directory after running ./configure. If you inspect create_bacula_database, you will see that it calls create_sqlite_database. The *_bacula_* files are provided for convenience. It doesn't matter what database you have chosen; create_bacula_database will always create your database. At this point, you can create the SQLite database and tables: cd <install-directory> This directory contains the Bacula catalog interface routines. ./make_sqlite_tables This script creates the SQLite database as well as the tables used by Bacula. This script will be automatically setup by the ./configure program to create a database named bacula.db in Bacula's working directory. ## Linking Bacula with SQLite If you have followed the above steps, this will all happen automatically and the SQLite libraries will be linked into Bacula. ## Testing SQLite As of this date (20 March 2002), we have much less "production" experience using SQLite than using MySQL. That said, we should note that SQLite has performed flawlessly for us in all our testing. ## Re-initializing the Catalog Database After you have done some initial testing with Bacula, you will probably want to re-initialize the catalog database and throw away all the test Jobs that you ran. To do so, you can do the following:
      cd <install-directory>
      ./drop_sqlite_tables
      ./make_sqlite_tables
Please note that all information in the database will be lost and you will be starting from scratch. If you have written on any Volumes, you must write and end of file mark on the volume so that Bacula can reuse it. Do so with:
       (stop Bacula or unmount the drive)
       mt -f /dev/nst0 rewind
       mt -f /dev/nst0 weof
Where you should replace /dev/nst0 with the appropriate tape drive device name for your machine.
Installing and Configuring PostgreSQL | Index | Internal Bacula Database
Bacula 1.34 User's Guide The Network Backup Solution | Copyright © 2000-2004 Kern Sibbald and John Walker