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 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 If you are building PostgreSQL from source, please be sure to add
22 the {\bf \verb:--:enable-thread-safety} option when doing the ./configure
25 \section{Installing PostgreSQL}
26 \index[general]{PostgreSQL!Installing }
28 If you use the {\bf ./configure \verb:--:with-postgresql=PostgreSQL-Directory}
29 statement for configuring {\bf Bacula}, you will need PostgreSQL version 7.3
30 or later installed. NOTE! PostgreSQL versions earlier than 7.3 do not work
31 with Bacula. If PostgreSQL is installed in the standard system location, you
32 need only enter {\bf \verb:--:with-postgresql} since the configure program will
33 search all the standard locations. If you install PostgreSQL in your home
34 directory or some other non-standard directory, you will need to provide the
35 full path with the {\bf \verb:--:with-postgresql} option.
37 Installing and configuring PostgreSQL is not difficult but can be confusing
38 the first time. If you prefer, you may want to use a package provided by your
39 chosen operating system. Binary packages are available on most PostgreSQL
42 If you prefer to install from source, we recommend following the instructions
44 \elink{PostgreSQL documentation}{http://www.postgresql.org/docs/}.
46 If you are using FreeBSD,
47 \elink{this FreeBSD Diary article}{http://www.freebsddiary.org/postgresql.php}
48 will be useful. Even if you are not using FreeBSD, the article will contain
49 useful configuration and setup information.
51 If you configure the Batch Insert code in Bacula (attribute inserts are
52 10 times faster), you {\bf must} be using a PostgreSQL that was built with
53 the {\bf \verb:--:enable-thread-safety} option, otherwise you will get
54 data corruption. Most major Linux distros have thread safety turned on, but
55 it is better to check. One way is to see if the PostgreSQL library that
56 Bacula will be linked against references pthreads. This can be done
57 with a command such as:
61 nm /usr/lib/libpq.a | grep pthread_mutex_lock
65 The above command should print a line that looks like:
73 if does, then everything is OK. If it prints nothing, do not enable batch
74 inserts when building Bacula.
76 After installing PostgreSQL, you should return to completing the installation
77 of {\bf Bacula}. Later, after Bacula is installed, come back to this chapter
78 to complete the installation. Please note, the installation files used in the
79 second phase of the PostgreSQL installation are created during the Bacula
80 Installation. You must still come back to complete the second phase of the
81 PostgreSQL installation even if you installed binaries (e.g. rpm, deb,
85 \label{PostgreSQL_configure}
86 \section{Configuring PostgreSQL}
87 \index[general]{PostgreSQL!Configuring PostgreSQL -- }
89 At this point, you should have built and installed PostgreSQL, or already have
90 a running PostgreSQL, and you should have configured, built and installed {\bf
91 Bacula}. If not, please complete these items before proceeding.
93 Please note that the {\bf ./configure} used to build {\bf Bacula} will need to
94 include {\bf \verb:--:with-postgresql=PostgreSQL-directory}, where {\bf
95 PostgreSQL-directory} is the directory name that you specified on the
96 ./configure command for configuring PostgreSQL (if you didn't specify a
97 directory or PostgreSQL is installed in a default location, you do not need to
98 specify the directory). This is needed so that Bacula can find the necessary
99 include headers and library files for interfacing to PostgreSQL.
101 {\bf Bacula} will install scripts for manipulating the database (create,
102 delete, make tables etc) into the main installation directory. These files
103 will be of the form *\_bacula\_* (e.g. create\_bacula\_database). These files
104 are also available in the \lt{}bacula-src\gt{}/src/cats directory after
105 running ./configure. If you inspect create\_bacula\_database, you will see
106 that it calls create\_postgresql\_database. The *\_bacula\_* files are
107 provided for convenience. It doesn't matter what database you have chosen;
108 create\_bacula\_database will always create your database.
110 Now you will create the Bacula PostgreSQL database and the tables that Bacula
111 uses. These instructions assume that you already have PostgreSQL running. You
112 will need to perform these steps as a user that is able to create new
113 databases. This can be the PostgreSQL user (on most systems, this is the pgsql
117 \item cd \lt{}install-directory\gt{}
119 This directory contains the Bacula catalog interface routines.
121 \item ./create\_bacula\_database
123 This script creates the PostgreSQL {\bf bacula} database.
124 Before running this command, you should carefully think about
125 what encoding sequence you want for the text fields (paths, files, ...).
126 Ideally, the encoding should be set to UTF8. However, many Unix systems
127 have filenames that are not encoded in UTF8, either because you have
128 not set UTF8 as your default character set or because you have imported
129 files from elsewhere (e.g. MacOS X). For this reason, Bacula uses
130 SQL\_ASCII as the default encoding. If you want to change this,
131 please modify the script before running it.
133 If running the script fails, it is probably because the database is
134 owned by a user other than yourself. On many systems, the database
135 owner is {\bf pgsql} and on others such as Red Hat and Fedora it is {\bf
136 postgres}. You can find out which it is by examining your /etc/passwd
137 file. To create a new user under either your name or with say the name
138 {\bf bacula}, you can do the following:
142 (enter root password)
143 su pgsql (or postgres)
144 createuser kern (or perhaps bacula)
145 Shall the new user be allowed to create databases? (y/n) y
146 Shall the new user be allowed to create more new users? (y/n) (choose
151 At this point, you should be able to execute the
152 ./create\_bacula\_database command.
154 \item ./make\_bacula\_tables
156 This script creates the PostgreSQL tables used by {\bf Bacula}.
157 \item ./grant\_bacula\_privileges
159 This script creates the database user {\bf bacula} with restricted access
160 rights. You may want to modify it to suit your situation. Please note that
161 this database is not password protected.
165 Each of the three scripts (create\_bacula\_database, make\_bacula\_tables, and
166 grant\_bacula\_privileges) allows the addition of a command line argument.
167 This can be useful for specifying the user name. For example, you might need
168 to add {\bf -h hostname} to the command line to specify a remote database
171 To take a closer look at the access privileges that you have setup with the
176 PostgreSQL-directory/bin/psql --command \\dp bacula
180 Also, I had an authorization problem with the password. In the end,
181 I had to modify my {\bf pg\_hba.conf} file (in /var/lib/pgsql/data on my machine)
186 local all all ident sameuser
188 local all all trust sameuser
192 This solved the problem for me, but it is not always a good thing
193 to do from a security standpoint. However, it allowed me to run
194 my regression scripts without having a password.
196 A more secure way to perform database authentication is with md5
197 password hashes. Begin by editing the {\bf pg\_hba.conf} file, and
198 just prior the the existing ``local'' and ``host'' lines, add the line:
202 local bacula bacula md5
206 and restart the Postgres database server (frequently, this can be done
207 using "/etc/init.d/postgresql restart" or "service postgresql restart") to
208 put this new authentication rule into effect.
210 Next, become the Postgres administrator, postgres, either by logging
211 on as the postgres user, or by using su to become root and then using
212 su - postgres to become postgres. Add a password to the bacula
213 database for the bacula user using:
218 bacula=# alter user bacula with password 'secret';
224 You'll have to add this password to two locations in the
225 bacula-dir.conf file: once to the Catalog resource and once to the
226 RunBeforeJob entry in the BackupCatalog Job resource. With the
227 password in place, these two lines should look something like:
231 dbname = bacula; user = bacula; password = "secret"
233 RunBeforeJob = "/etc/make_catalog_backup bacula bacula secret"
237 Naturally, you should choose your own significantly more random
238 password, and ensure that the bacula-dir.conf file containing this
239 password is readable only by the root.
241 Even with the files containing the database password properly
242 restricted, there is still a security problem with this approach: on
243 some platforms, the environment variable that is used to supply the
244 password to Postgres is available to all users of the
245 local system. To eliminate this problem, the Postgres team have
246 deprecated the use of the environment variable password-passing
247 mechanism and recommend the use of a .pgpass file instead. To use
248 this mechanism, create a file named .pgpass containing the single
253 localhost:5432:bacula:bacula:secret
257 This file should be copied into the home directory of all accounts
258 that will need to gain access to the database: typically, root,
259 bacula, and any users who will make use of any of the console
260 programs. The files must then have the owner and group set to match
261 the user (so root:root for the copy in ~root, and so on), and the mode
262 set to 600, limiting access to the owner of the file.
264 \section{Re-initializing the Catalog Database}
265 \index[general]{Database!Re-initializing the Catalog }
266 \index[general]{Re-initializing the Catalog Database }
268 After you have done some initial testing with {\bf Bacula}, you will probably
269 want to re-initialize the catalog database and throw away all the test Jobs
270 that you ran. To do so, you can do the following:
274 cd <install-directory>
277 ./grant_bacula_privileges
281 Please note that all information in the database will be lost and you will be
282 starting from scratch. If you have written on any Volumes, you must write an
283 end of file mark on the volume so that Bacula can reuse it. Do so with:
287 (stop Bacula or unmount the drive)
288 mt -f /dev/nst0 rewind
293 Where you should replace {\bf /dev/nst0} with the appropriate tape drive
294 device name for your machine.
296 \section{Installing PostgreSQL from RPMs}
297 \index[general]{PostgreSQL!Installing from RPMs}
298 \index[general]{Installing PostgreSQL from RPMs}
299 If you are installing PostgreSQL from RPMs, you will need to install
300 both the PostgreSQL binaries and the client libraries. The client
301 libraries are usually found in a devel package, so you must
313 These will be similar with most other package managers too. After
314 installing from rpms, you will still need to run the scripts that set up
315 the database and create the tables as described above.
318 \section{Converting from MySQL to PostgreSQL}
319 \index[general]{PostgreSQL!Converting from MySQL to }
320 \index[general]{Converting from MySQL to PostgreSQL }
322 The conversion procedure presented here was worked out by Norm Dressler
323 \lt{}ndressler at dinmar dot com\gt{}
325 This process was tested using the following software versions:
328 \item Linux Mandrake 10/Kernel 2.4.22-10 SMP
329 \item Mysql Ver 12.21 Distrib 4.0.15, for mandrake-linux-gnu (i586)
330 \item PostgreSQL 7.3.4
334 WARNING: Always as a precaution, take a complete backup of your databases
335 before proceeding with this process!
338 \item Shutdown bacula (cd /etc/bacula;./bacula stop)
339 \item Run the following command to dump your Mysql database:
343 mysqldump -f -t -n >bacula-backup.dmp
348 \item Make a backup of your /etc/bacula directory (but leave the original in
350 \item Go to your Bacula source directory and rebuild it to include PostgreSQL
351 support rather then Mysql support. Check the config.log file for your
352 original configure command and replace enable-mysql with enable-postgresql.
353 \item Recompile Bacula with a make and if everything compiles completely,
354 perform a make install.
355 \item Shutdown Mysql.
356 \item Start PostgreSQL on your system.
357 \item Create a bacula user in Postgres with the createuser command. Depending on
358 your Postgres install, you may have to SU to the user who has privileges to
360 \item Verify your pg\_hba.conf file contains sufficient permissions to allow
361 bacula to access the server. Mine has the following since it's on a secure
368 host all all 127.0.0.1 255.255.255.255 trust
370 NOTE: you should restart your postgres server if you
376 \item Change into the /etc/bacula directory and prepare the database and
377 tables with the following commands:
381 ./create_postgresql_database
383 ./make_postgresql_tables
385 ./grant_postgresql_privileges
390 \item Verify you have access to the database:
400 You should not get any errors.
401 \item Load your database from the Mysql database dump with:
405 psql -Ubacula bacula <bacula-backup.dmp>
410 \item Resequence your tables with the following commands:
416 SELECT SETVAL('basefiles_baseid_seq', (SELECT
417 MAX(baseid) FROM basefiles));
418 SELECT SETVAL('client_clientid_seq', (SELECT
419 MAX(clientid) FROM client));
420 SELECT SETVAL('file_fileid_seq', (SELECT MAX(fileid)
422 SELECT SETVAL('filename_filenameid_seq', (SELECT
423 MAX(filenameid) FROM filename));
425 SELECT SETVAL('fileset_filesetid_seq', (SELECT
426 MAX(filesetid) FROM fileset));
428 SELECT SETVAL('job_jobid_seq', (SELECT MAX(jobid) FROM job));
429 SELECT SETVAL('jobmedia_jobmediaid_seq', (SELECT
430 MAX(jobmediaid) FROM jobmedia));
431 SELECT SETVAL('media_mediaid_seq', (SELECT MAX(mediaid) FROM media));
432 SELECT SETVAL('path_pathid_seq', (SELECT MAX(pathid) FROM path));
434 SELECT SETVAL('pool_poolid_seq', (SELECT MAX(poolid) FROM pool));
439 \item At this point, start up Bacula, verify your volume library and perform
440 a test backup to make sure everything is working properly.
443 \section{Upgrading PostgreSQL}
444 \index[general]{Upgrading PostgreSQL }
445 \index[general]{Upgrading!PostgreSQL }
446 \index[general]{Upgrading}
447 If you upgrade PostgreSQL, you must reconfigure, rebuild, and re-install
448 Bacula otherwise you are likely to get bizarre failures. If you
449 to modify the bacula.spec file to account for the new PostgreSQL version.
450 You can do so by rebuilding from the source rpm. To do so, you may need
451 install from rpms and you upgrade PostgreSQL, you must also rebuild Bacula.
455 \index[general]{Credits }
456 Many thanks to Dan Langille for writing the PostgreSQL driver. This will
457 surely become the most popular database that Bacula supports.