Installing bacula

That directory will be our Archive Device. Next, we'll configure our Archive Device within the default Bacula configuration file. Open that file with the command:. In that file, locate the Device and Autochanger sections and comment them completely out by adding a character before each line. Next, we'll add a new Device section:. Before you save and close the file, scroll back to the top and copy the password string in the line from the Director section :.

With the Bacula server up and running, we now have to configure the Director which supervises all backup, restore, verify and archive operations. Open the Director configuration file with the command:. If the server configuration includes:. We can confirm that with the command:. Select the LocalBackup option and then type yes to queue the job. A Bacula job is used to perform backup and restore actions. Job resources define the details of what a particular job will do, including the name of the Client, the FileSet to back up or restore, among other things.

It should look like this:. A Bacula FileSet defines a set of files or directories to include or exclude files from a backup selection, and are used by jobs. With the comments removed, it should look like this:. First, we enabled gzip compression when creating a backup archive.

For example, a FileSet that only includes your customized configuration files and databases might be sufficient for your needs, if you have a clear recovery plan that details installing required software packages and placing the restored files in the proper locations, while only using a fraction of the disk space for backup archives.

In the Bacula Director configuration file, the Storage resource defines the Storage Daemon that the Director should connect to.

It should look like this substitute the highlighted word :. This is necessary because we are going to configure the Storage Daemon to listen on the private network interface, so remote clients can connect to it. In the Bacula Director configuration file, the Catalog resource defines where the Database that the Director should use and connect to. A Pool resource defines the set of storage used by Bacula to write backups. We will use files as our storage volumes, and we will simply update the label so our local backups get labeled properly.

Our Bacula server is almost set up, but we still need to configure the Storage Daemon, so Bacula knows where to store backups. Find the Storage resource. This defines where the SD process will listen for connections. Each Bacula component, such as the Director, SD, and FD, have passwords that are used for inter-component authentication—you probably noticed placeholders while going through the configuration files.

These commands generate and set the Director password. The bconsole connects to the Director, so it needs the password too:. These commands generate and set the Storage Daemon password. The Director connects to the SD, so it needs the password too:.

These commands generate and set the local File Daemon the Bacula client software password. The Director connects to this FD, so it needs the password too:. We will use the Bacula Console to run our first backup job. If it runs without any issues, we will know that Bacula is configured properly. Then select the pool that the backup should use. It will teach you a lot about Bacula and as an example can be installed into a single directory for easy removal and run as non-root.

If you have any problems or when you want to do a real installation, come back to this chapter and read the details presented below. The following command line options are available for configure to customize your installation. However, we find this a somewhat vague concept, and so we have not implemented this option other than to use any explicit prefix that you may define. If you do not explicitly specify a prefix, Bacula's configure routine will not use the default value that.

As a consequence, we suggest that you avoid it. We have provided options that allow you to explicitly specify the directories for each of the major categories of installation files.

If you wish the man page to be installed in a different location, use this option to specify the path. If it is not available on your system, you can download the depkgs-qt package from the Bacula Source Forge download area and build it. In particular to use the Qt4 built by depkgs-qt you must source the file qt4-paths. To verify that your PostgreSQL is thread safe, you can try this change the path to point to your particular installed libpq.

The above example shows a libpq that contains the required function PQputCopyData and is thread enabled i. If you do not see the mutex entries, then thread support has not been enabled. Running with Batch Insert turned on is recommended because it can significantly improve attribute insertion times. However, it does put a significantly larger part of the work on your SQL engine, so you may need to pay more attention to tuning it.

For MySQL, the location is set in my. You may also want to increase the memory available to your SQL engine to further improve performance during Batch Inserts. When linking a static binary, the linker needs the static versions of all the libraries that are used, so frequently users will experience linking errors when this option is used.

The first thing to do is to make sure you have the static glibc library installed on your system. The second thing to do is the make sure you do not specify -openssl or -with-python on your.

You may be able to enable those options, but you will need to load additional static libraries. Note, for Bacula to be configured properly, you must specify one of the four database options supported.

That is: -with-sqlite, -with-sqlite3, -with-mysql, or -with-postgresql, otherwise the. If you get errors linking, you need to load the development libraries, or you need to disable SSL by setting without-openssl. On SuSE, the libwrappers libraries needed to link Bacula are contained in the tcpd-devel package. This option is designed primarily for use in regression testing.

Most users can safely ignore this option. Note, many other options are presented when you do a. If you want to install Bacula in an installation directory rather than run it out of the build directory as developers will do most of the time , you should also include the -- sbindir and -- sysconfdir options with appropriate paths.

Neither are necessary if you do not use "make install" as is the case for most development work. The install process will create the sbindir and sysconfdir if they do not exist, but it will not automatically create the pid-dir, subsys-dir, or working-dir, so you must ensure that they exist before running Bacula for the first time. To build Bacula from source, you will need the following installed on your system they are not by default : libiconv, gcc 3.

Probably the simplest way to do so is to run:. It is also possible to use the crle program to set the library search path. However, this should be used with caution.

In addition, users of FreeBSD prior to 4. Mixing the two will probably not work. The following script could be used if you want to put everything in a single directory except for the working directory :.

Before setting up your configuration files, you will want to install Bacula in its final location. Simply enter:.

If you have previously installed Bacula, the old binaries will be overwritten, but the old configuration files will remain unchanged, and the "new" configuration files will be appended with a.

Generally if you have previously installed and run Bacula you will want to discard or ignore the configuration files with the appended.

If you run the Director and the Storage daemon on one machine and you wish to back up another machine, you must have a copy of the File daemon for that machine. If the machine and the Operating System are identical, you can simply copy the Bacula File daemon binary file bacula-fd as well as its configuration file bacula-fd.

Be sure to make corresponding additions to the Director's configuration file bacula-dir. If the architecture or the OS level are different, you will need to build a File daemon on the Client machine. To do so, you can use the same.

Since the File daemon does not access the Catalog database, you can remove the -- with-mysql or -- with-sqlite options, then add -- enable-client-only. This will compile only the necessary libraries and the client programs and thus avoids the necessity of installing one or another of those database programs to build the File daemon.

It contains several references to other sections, and we will look at those sections further down. The FileSet in this example is very straight forward. Email Address. Excellent article. I was going through this article with fedora and ubuntu. I was having difficulties connecting to the client running on fedora.

The issue was the version difference between the client and the server. I had to downgrade the bacula-fd client on fedora to the lowest version 9. Additional menu. Pages: Page 1 Page 2 Page 3. Get notified when new articles are posted Enter your email address to subscribe and receive notifications of new posts by email. Next Post: Adding a Windows host to our Bacula setup. Comments Bonjour, Ca marche. Meilleurs salutations. Hello, Excellent article.