4 \chapter{Installing and Configuring PostgreSQL}
5 \label{PostgreSqlChapter}
6 \index[general]{PostgreSQL!Installing and Configuring }
7 \index[general]{Installing and Configuring PostgreSQL }
8 \index[general]{Upgrading}
10 Warning!!! If you are considering using PostreSQL, you should be aware
11 of their philosophy of upgrades, which could be
12 destabilizing for a production shop. Basically at every major version
13 upgrade, you are required to dump your database in an ASCII format,
14 do the upgrade, and then reload your database (or databases). This is
15 because they frequently update the "data format" from version to
16 version, and they supply no tools to automatically do the conversion.
17 If you forget to do the ASCII dump, your database may become totally
18 useless because none of the new tools can access it due to the format
19 change, and the PostgreSQL server will not be able to start.
21 \section{Installing PostgreSQL}
22 \index[general]{PostgreSQL!Installing }
24 If you use the {\bf ./configure \verb:--:with-postgresql=PostgreSQL-Directory}
25 statement for configuring {\bf Bacula}, you will need PostgreSQL version 7.3
26 or later installed. NOTE! PostgreSQL versions earlier than 7.3 do not work
27 with Bacula. If PostgreSQL is installed in the standard system location, you
28 need only enter {\bf \verb:--:with-postgresql} since the configure program will
29 search all the standard locations. If you install PostgreSQL in your home
30 directory or some other non-standard directory, you will need to provide the
31 full path with the {\bf \verb:--:with-postgresql} option.
33 Installing and configuring PostgreSQL is not difficult but can be confusing
34 the first time. If you prefer, you may want to use a package provided by your
35 chosen operating system. Binary packages are available on most PostgreSQL
38 If you prefer to install from source, we recommend following the instructions
40 \elink{PostgreSQL documentation}{http://www.postgresql.org/docs/}.
42 If you are using FreeBSD,
43 \elink{this FreeBSD Diary article}{http://www.freebsddiary.org/postgresql.php}
44 will be useful. Even if you are not using FreeBSD, the article will contain
45 useful configuration and setup information.
47 After installing PostgreSQL, you should return to completing the installation
48 of {\bf Bacula}. Later, after Bacula is installed, come back to this chapter
49 to complete the installation. Please note, the installation files used in the
50 second phase of the PostgreSQL installation are created during the Bacula
51 Installation. You must still come back to complete the second phase of the
52 PostgreSQL installation even if you installed binaries (e.g. rpm, deb,
56 \label{PostgreSQL_configure}
57 \section{Configuring PostgreSQL}
58 \index[general]{PostgreSQL!Configuring PostgreSQL -- }
60 At this point, you should have built and installed PostgreSQL, or already have
61 a running PostgreSQL, and you should have configured, built and installed {\bf
62 Bacula}. If not, please complete these items before proceeding.
64 Please note that the {\bf ./configure} used to build {\bf Bacula} will need to
65 include {\bf \verb:--:with-postgresql=PostgreSQL-directory}, where {\bf
66 PostgreSQL-directory} is the directory name that you specified on the
67 ./configure command for configuring PostgreSQL (if you didn't specify a
68 directory or PostgreSQL is installed in a default location, you do not need to
69 specify the directory). This is needed so that Bacula can find the necessary
70 include headers and library files for interfacing to PostgreSQL.
72 {\bf Bacula} will install scripts for manipulating the database (create,
73 delete, make tables etc) into the main installation directory. These files
74 will be of the form *\_bacula\_* (e.g. create\_bacula\_database). These files
75 are also available in the \lt{}bacula-src\gt{}/src/cats directory after
76 running ./configure. If you inspect create\_bacula\_database, you will see
77 that it calls create\_postgresql\_database. The *\_bacula\_* files are
78 provided for convenience. It doesn't matter what database you have chosen;
79 create\_bacula\_database will always create your database.
81 Now you will create the Bacula PostgreSQL database and the tables that Bacula
82 uses. These instructions assume that you already have PostgreSQL running. You
83 will need to perform these steps as a user that is able to create new
84 databases. This can be the PostgreSQL user (on most systems, this is the pgsql
88 \item cd \lt{}install-directory\gt{}
90 This directory contains the Bacula catalog interface routines.
92 \item ./create\_bacula\_database
94 This script creates the PostgreSQL {\bf bacula} database.
95 Before running this command, you should carefully think about
96 what encoding sequence you want for the text fields (paths, files, ...).
97 Ideally, the encoding should be set to UTF8. However, many Unix systems
98 have filenames that are not encoded in UTF8, either because you have
99 not set UTF8 as your default character set or because you have imported
100 files from elsewhere (e.g. MacOS X). For this reason, Bacula uses
101 SQL\_ASCII as the default encoding. If you want to change this,
102 please modify the script before running it.
104 If running the script fails, it is probably because the database is
105 owned by a user other than yourself. On many systems, the database
106 owner is {\bf pgsql} and on others such as Red Hat and Fedora it is {\bf
107 postgres}. You can find out which it is by examining your /etc/passwd
108 file. To create a new user under either your name or with say the name
109 {\bf bacula}, you can do the following:
113 (enter root password)
114 su pgsql (or postgres)
115 createuser kern (or perhaps bacula)
116 Shall the new user be allowed to create databases? (y/n) y
117 Shall the new user be allowed to create more new users? (y/n) (choose
122 At this point, you should be able to execute the
123 ./create\_bacula\_database command.
125 \item ./make\_bacula\_tables
127 This script creates the PostgreSQL tables used by {\bf Bacula}.
128 \item ./grant\_bacula\_privileges
130 This script creates the database user {\bf bacula} with restricted access
131 rights. You may want to modify it to suit your situation. Please note that
132 this database is not password protected.
136 Each of the three scripts (create\_bacula\_database, make\_bacula\_tables, and
137 grant\_bacula\_privileges) allows the addition of a command line argument.
138 This can be useful for specifying the user name. For example, you might need
139 to add {\bf -h hostname} to the command line to specify a remote database
142 To take a closer look at the access privileges that you have setup with the
147 PostgreSQL-directory/bin/psql --command \\dp bacula
151 Also, I had an authorization problem with the password. In the end,
152 I had to modify my {\bf pg\_hba.conf} file (in /var/lib/pgsql/data on my machine)
157 local all all ident sameuser
159 local all all trust sameuser
163 This solved the problem for me, but it is not always a good thing
164 to do from a security standpoint. However, it allowed me to run
165 my regression scripts without having a password.
167 A more secure way to perform database authentication is with md5
168 password hashes. Begin by editing the {\bf pg\_hba.conf} file, and
169 just prior the the existing ``local'' and ``host'' lines, add the line:
173 local bacula bacula md5
177 and restart the Postgres database server (frequently, this can be done
178 using "/etc/init.d/postgresql restart") to put this new authentication
181 Next, become the Postgres administrator, postgres, either by logging
182 on as the postgres user, or by using su to become root and then using
183 su - postgres to become postgres. Add a password to the bacula
184 database for the bacula user using:
189 bacula=# alter user bacula with password 'secret';
195 Next, you'll have to add this password to two locations in the
196 bacula-dir.conf file: once to the Catalog resource and once to the
197 RunBeforeJob entry in the BackupCatalog Job resource. With the
198 password in place, these two lines should look something like:
202 dbname = bacula; user = bacula; password = "secret"
204 RunBeforeJob = "/etc/make_catalog_backup bacula bacula secret"
208 Naturally, you should choose your own significantly more random
209 password, and ensure that the bacula-dir.conf file containing this
210 password is readable only by the root.
212 Even with the files containing the database password properly
213 restricted, there is still a security problem with this approach: on
214 some platforms, the environment variable that is used to supply the
215 password to Postgres is available to all users of the
216 local system. To eliminate this problem, the Postgres team have
217 deprecated the use of the environment variable password-passing
218 mechanism and recommend the use of a .pgpass file instead. To use
219 this mechanism, create a file named .pgpass containing the single
224 localhost:5432:bacula:bacula:secret
228 This file should be copied into the home directory of all accounts
229 that will need to gain access to the database: typically, root,
230 bacula, and any users who will make use of any of the console
231 programs. The files must then have the owner and group set to match
232 the user (so root:root for the copy in ~root, and so on), and the mode
233 set to 600, limiting access to the owner of the file.
235 \section{Re-initializing the Catalog Database}
236 \index[general]{Database!Re-initializing the Catalog }
237 \index[general]{Re-initializing the Catalog Database }
239 After you have done some initial testing with {\bf Bacula}, you will probably
240 want to re-initialize the catalog database and throw away all the test Jobs
241 that you ran. To do so, you can do the following:
245 cd <install-directory>
248 ./grant_bacula_privileges
252 Please note that all information in the database will be lost and you will be
253 starting from scratch. If you have written on any Volumes, you must write an
254 end of file mark on the volume so that Bacula can reuse it. Do so with:
258 (stop Bacula or unmount the drive)
259 mt -f /dev/nst0 rewind
264 Where you should replace {\bf /dev/nst0} with the appropriate tape drive
265 device name for your machine.
267 \section{Installing PostgreSQL from RPMs}
268 \index[general]{PostgreSQL!Installing from RPMs}
269 \index[general]{Installing PostgreSQL from RPMs}
270 If you are installing PostgreSQL from RPMs, you will need to install
271 both the PostgreSQL binaries and the client libraries. The client
272 libraries are usually found in a devel package, so you must
282 This will be the same with most other package managers too. After
283 installing from rpms, you will still need to run the scripts that set up
284 the database and create the tables as described above.
287 \section{Converting from MySQL to PostgreSQL}
288 \index[general]{PostgreSQL!Converting from MySQL to }
289 \index[general]{Converting from MySQL to PostgreSQL }
291 The conversion procedure presented here was worked out by Norm Dressler
292 \lt{}ndressler at dinmar dot com\gt{}
294 This process was tested using the following software versions:
297 \item Linux Mandrake 10/Kernel 2.4.22-10 SMP
298 \item Mysql Ver 12.21 Distrib 4.0.15, for mandrake-linux-gnu (i586)
299 \item PostgreSQL 7.3.4
303 WARNING: Always as a precaution, take a complete backup of your databases
304 before proceeding with this process!
307 \item Shutdown bacula (cd /etc/bacula;./bacula stop)
308 \item Run the following command to dump your Mysql database:
312 mysqldump -f -t -n >bacula-backup.dmp
317 \item Make a backup of your /etc/bacula directory (but leave the original in
319 \item Go to your Bacula source directory and rebuild it to include PostgreSQL
320 support rather then Mysql support. Check the config.log file for your
321 original configure command and replace enable-mysql with enable-postgresql.
322 \item Recompile Bacula with a make and if everything compiles completely,
323 perform a make install.
324 \item Shutdown Mysql.
325 \item Start PostgreSQL on your system.
326 \item Create a bacula user in Postgres with the createuser command. Depending on
327 your Postgres install, you may have to SU to the user who has privileges to
329 \item Verify your pg\_hba.conf file contains sufficient permissions to allow
330 bacula to access the server. Mine has the following since it's on a secure
337 host all all 127.0.0.1 255.255.255.255 trust
339 NOTE: you should restart your postgres server if you
345 \item Change into the /etc/bacula directory and prepare the database and
346 tables with the following commands:
350 ./create_postgresql_database
352 ./make_postgresql_tables
354 ./grant_postgresql_privileges
359 \item Verify you have access to the database:
369 You should not get any errors.
370 \item Load your database from the Mysql database dump with:
374 psql -Ubacula bacula <bacula-backup.dmp>
379 \item Resequence your tables with the following commands:
385 SELECT SETVAL('basefiles_baseid_seq', (SELECT
386 MAX(baseid) FROM basefiles));
387 SELECT SETVAL('client_clientid_seq', (SELECT
388 MAX(clientid) FROM client));
389 SELECT SETVAL('file_fileid_seq', (SELECT MAX(fileid)
391 SELECT SETVAL('filename_filenameid_seq', (SELECT
392 MAX(filenameid) FROM filename));
394 SELECT SETVAL('fileset_filesetid_seq', (SELECT
395 MAX(filesetid) FROM fileset));
397 SELECT SETVAL('job_jobid_seq', (SELECT MAX(jobid) FROM job));
398 SELECT SETVAL('jobmedia_jobmediaid_seq', (SELECT
399 MAX(jobmediaid) FROM jobmedia));
400 SELECT SETVAL('media_mediaid_seq', (SELECT MAX(mediaid) FROM media));
401 SELECT SETVAL('path_pathid_seq', (SELECT MAX(pathid) FROM path));
403 SELECT SETVAL('pool_poolid_seq', (SELECT MAX(poolid) FROM pool));
408 \item At this point, start up Bacula, verify your volume library and perform
409 a test backup to make sure everything is working properly.
412 \section{Upgrading PostgreSQL}
413 \index[general]{Upgrading PostgreSQL }
414 \index[general]{Upgrading!PostgreSQL }
415 \index[general]{Upgrading}
416 If you upgrade PostgreSQL, you must reconfigure, rebuild, and re-install
417 Bacula otherwise you are likely to get bizarre failures. If you
418 to modify the bacula.spec file to account for the new PostgreSQL version.
419 You can do so by rebuilding from the source rpm. To do so, you may need
420 install from rpms and you upgrade PostgreSQL, you must also rebuild Bacula.
424 \index[general]{Credits }
425 Many thanks to Dan Langille for writing the PostgreSQL driver. This will
426 surely become the most popular database that Bacula supports.