Several network backup topologies of Bacula
The previous article introduced the Bacula has 5 components, in the actual application, does not need to place 5 parts on the different server, some parts of them can be merged, the common Bacula deployment structure has the following several kinds:
1 Director and SD and console on a machine, while the client FD on another machine, of course, client FD can have one or more platforms.
2 Director and console on a machine, SD on a machine, client FD on one or more platforms.
3 Director and Client FD, SD and console end on a machine, that is, the server itself back up their own, the data saved in this machine.
Second, compile and install Bacula
Here is an introduction to the first Bacula deployment structure in the previous section. The environment is shown in table 4-1.
Table 11 Environment for a BACULA deployment structure
Host name IP address operating system application role
Baculaserver 192.168.12.188 CentOS Release 5.4 Director, SD, Console
Baculaclient 192.168.12.189 CentOS Release 5.4 FD
The entire topology is shown in Figure 1.
Fig. 1 The topological structure of the Bacula instance
1. Install Bacula on Bacula server side
First in the http://www.bacula.org download the corresponding source code, here to download the bacula-5.0.1.tar.gz, and then compile the installation process as follows:
[Root@baculaserver opt]# tar zxvf bacula-5.0.1.tar.gz
[root@baculaserveropt]# CD bacula-5.0.1
[Root@baculaserver bacula-5.0.1]#./configure--prefix=/opt/bacula--with-mysql=/opt/mysql
[Root@baculaserver bacula-5.0.1] #make
[Root@baculaserver bacula-5.0.1] #make Install
Bacula requires database support, where MySQL database is used, and assumes MySQL has been installed on the Bacula server side, and the MySQL installation path is/opt/mysql (Bacula at compile time through "--with-mysql" option specifies the installation path for the MySQL database.
After the Bacula installation is complete, all the profiles are placed by default in the/opt/bacula/etc/directory.