Backup with Open Source Solution - Bareos

Having a current backup at hand is an extremely important point, because no one is immune from unpleasant incidents associated with the failure of the media, loss of information, accidental deletion, etc. In such situations, the backup will save not only nerves, but also save you from possible financial problems that may arise due to data loss.



Bareos - was selected as a backup system for the following reasons:

')

• is open source;
• actively developing;
• has many useful features;
• can extend its functionality with plugins.

Task Description

Suppose we have 3 cars. Servers: Bareos, BitrixVm, Windows Server 2012 R2. For example, all this will be within the same network, but Bareos itself, of course, allows you to perform backups if the machine is located outside of it.

Bareos - 172.16.10.10

BitrixVM - 172.16.10.11

Windows Server - 172.16.10.12

Add a repository:

# wget http://download.bareos.org/bareos/release/latest/CentOS_7/bareos.repo -O /etc/yum.repos.d/bareos.repo 

For the server with Bareos, we will use CentOS 7. The usual installation occurs:

 # yum install -y bareos-client bareos-database-tools bareos-filedaemon bareos-database-postgresql bareos bareos-bconsole bareos-database-common bareos-storage bareos-director bareos-common 

PostgreSQL will be used as the database. Installation is also easy:

 # yum install -y postgresql-server postgresql-contrib 

When installing Bareos in / etc / bareos, we have the following list of files and folders, with the exception of the “ssl” directory, we move on to it a little later:

 /bareos-dir.d /bareos-sd.d /ssl bareos-dir.conf bareos-fd.conf bareos-sd.conf bconsole.conf .rndpwd 

After installation, the scripts for working with Bareos will appear in the / usr / lib / bareos / scripts / directory. Thanks to them, we can pre-configure the database (we will create a database, tables, and rights):

 su postgres -c /usr/lib/bareos/scripts/create_bareos_database su postgres -c /usr/lib/bareos/scripts/make_bareos_tables su postgres -c /usr/lib/bareos/scripts/grant_bareos_privileges 

The important point is that the names of our machines must be resolved, if not, we add the appropriate lines in / etc / hosts

 172.16.10.10 bareos-server 172.16.10.10 bareos-fd 172.16.10.11 bitrixvm 172.16.10.12 win-fd 

bareos-server - the server itself, bareos-fd - we will also make a backup of the server itself, i.e. at the same time, it will act as a client, then it will be seen in the configuration, bitrixvm - the client name speaks for itself, win-fd is a client with Windows Server 2012 R2.



The configuration of the server part for BareOS, namely the director, must be performed in the bareos-dir.conf file. The director is responsible for all operations performed.



Of the main guidelines:

Director - description of the director himself,

Storage - the device on which we write backups,

Catalog - contains information on completed jobs, saved files, clients, statuses,

Messages - which messages will be collected and how to deliver them,

Console - configure the console to manage the director,

Client - description of the client from which backup copies will be taken,

Pool - allows you to manage so-called. Volume where data will be written for different types of backups (Full, Incremental, Differential), limit storage periods. Volume, sizes,

FileSet - what backup and additional attributes,

Schedule - schedule

Job - description of the backup task.

From the official documentation, the scheme of interaction between the services:









# Add the two remaining clients as separate configuration files.

 @/etc/bareos/bareos-dir.d/win.conf @/etc/bareos/bareos-dir.d/bitrixvm.conf 

It is important that there is a correspondence between the configurations:







After all the basic settings you need to restart the bareos services:

 systemctl restart bareos-dir systemctl restart bareos-sd systemctl restart bareos-fd 

In case of errors, we look at the state with the command:

 systemctl status bareos-dir.service -l 

Let's proceed to the installation of the bareos client plugin for Windows. You can download here .



Installing the plugin is also easy. From the list of proposed components, we select only two indicated in the screenshot: then we set the name for the client, indicate the parameters of the already existing director:







We prescribe the following data:

Client Name - win-fd

Director Name - bareos-server

Password - zcx @ # $ BGj

Networks Address - bareos-server

The entered settings can always be corrected, the default configuration file is in “C: \ Program Data \ Bareos \ bareos-fd.conf”.



In the hosts file we also specify the IP for the BareOS server so that the name is resolved. On the server side (bareos-server), the config for the client (win-fd) looks like this and is located along the /etc/bareos/bareos-dir.d/win.conf path:





From the FileSet directive we see that for the Job-win-Full task we copy the users folder “C: \ Users” and in the Job-win-Full-restore task we restore it to the folder if necessary “C: \ tmp”.



There is one more client (bitrixvm) for which you need to copy the root directory and copy the mysql database in a separate task.



Let’s go to the bitrixvm machine and install the client:

yum install -y bareos-client bareos-common



Moving to the / etc / bareos directory

 /bareos-dir.d /bareos-fd.d /bconsole.conf /ssl .rndpwd tray-monitor.d 

To configure the client go to the directory /bareos-fd.d

 /client /director /messages 

By default, after installation, the configuration is scattered into the three directories shown above, so for further convenience we will commit partial configurations in the directories and messages directories, and perform all the settings in /client/myself.conf



We enter the parameters and restart the service:

 /etc/init.d/bareos-fd restart 

Register in the hosts address for the bareos-server



On the server side (bareos-server), the configuration for the client (bitrixvm) is as follows: /etc/bareos/bareos-dir.d/bitrixvm.conf:





In the RunScript section of the Command parameter, we run the mysqldump command, passing all the necessary "mysqldump -uroot -ppassword --opt --all-databases> /tmp/dump.sql" parameters.



The saved dump.sql file will be backed up as specified for the FileSet called "bareos-fileset-bitrixvm-mysql".



Bareos uses the TLS protocol to encrypt data transfers. For each client and director we must have a CA certificate, certificate and key. We will use self-signed certificates, all this can be done through openssl.



Let's follow the path of the openssl configuration file /etc/pki/tls/openssl.cnf



We generate CA certificate:

 #openssl req -config openssl.cnf -new -x509 -extensions v3_ca -keyout private/myca.key -out certs/myca.crt 

After entering the password and other data, we get two files:

 /etc/pki/CA/private/myca.key /etc/pki/CA/certs/myca.crt 

We will correct / check the settings file openssl.cnf so that the paths to the certificates are correct, bold highlights what needs to be changed.



You also need to create the index.txt and serial files in the / etc / pki / CA folder:

 touch /etc/pki/CA/index.txt 

In the serial file we immediately enter the value “01”, the file will contain the following number for the following certificates:

 echo '01' > /etc/pki/CA/serial 

We generate a key for the server, you will need to enter a password.

 openssl genrsa -aes256 -out bareos-server.key.pem 4096 

We generate a certificate request. The important point is that in this section, when generating the certificate, you must correctly specify the Common Name (CN) so that it matches the name of the machine, otherwise errors will occur when attempting to perform any task. In this example, CN = bareos-server

openssl req -config openssl.cnf -key bareos-server.key.pem -new -sha256 -out bareos-server.csr.pem



We sign CSR through CA, we get the certificate itself

 openssl ca -config openssl.cnf -in bareos-server.csr.pem -out bareos-server.cert.pem 

We remove the password for the key, because bareos need him password free

 openssl rsa -in bareos-server.key.pem -out bareos-server.nopass.key.pem 

We will convert the CA key and certificate into one file with the PEM extension.

 cat /etc/pki/CA/private/myca.key /etc/pki/CA/certs/myca.cert > ca-chain.cert.pem 

Generating DH key

 openssl dhparam -out dh1024.pem -5 1024 

Copy the bareos-server.cert.pem certificates bareos-server.nopass.key.pem ca-chain.cert.pem dh1024.pem to the / etc / bareos / ssl folder that you first need to create and install the bareos group



For each certificate, change the group to bareos

 chgrp bareos * 

Similar actions need to be done for each client (bitrixvm, win-fd):

 openssl genrsa -aes256 -out bitrixvm.key.pem 4096 openssl req -config openssl.cnf -key bitrixvm.key.pem -new -sha256 -out bitrixvm.csr.pem openssl ca -config openssl.cnf -in bitrixvm.csr.pem -out bitrixvm.cert.pem openssl rsa -in bitrixvm.key.pem -out bitrixvm.nopass.key.pem 

Using SCP, copy 4 files bitrixvm.cert.pem bitrixvm.nopass.key.pem ca-chain.cert.pem dh1024.pem to a remote bitrixvm machine in the / etc / bareos / ssl folder, which you must first create and install the bareos group for folder so for certificates.



The bitrixvm client configuration (/etc/bareos/bareos-fd.d/client/myself.conf) in the Director {} section requires that client certificates, but not the director, be registered. In the configuration on the server side (/etc/bareos/bareos-dir.d/bitrixvm.conf), in the Client {} section, director certificates are specified. After making configuration changes, restart the services.



Creating certificates for a win-fd machine is identical.



You also need to register certificates for bconsole, a utility that allows you to manage the director in the /etc/bareos/bconsole.conf file:





The backup or restore procedure is as follows. Let's use the bconsole utility, as a greeting we will see *

run Shows all possible jobs:





The result of the command can be viewed either through the message command and in response we get something like this:





Or through the status dir command





Where in the status column, you can view the status of the backup. Job number 75 was successful.



The restore is done by the restore command

 *restore 

Then a list of all possible options will be offered.

To select the JobIds, you have the following choices:



1: List last 20 Jobs run

2: List Jobs where a given File is saved

3: Enter list of comma separated JobIds to select

4: Enter SQL list command

5: Select the most recent backup for a client

6: Select backup for a client

7: Enter a list of files to restore

8: Enter a list of files

9: Find the JobIds of the most recent backup for a client

10: Find the job

11: Enter a list of directories to restore for found JobIds

12: Select full restore to a specified job date

13: Cancel

We will show the list of the last 20 tasks:







Click 3 and specify JobID number, for example 75. After that, we automatically get to the console to select the files that we want to restore.

 cwd is: / $ 

A list of all available commands can be viewed via the help command. We check which files are available in this backup, mark the necessary files with the mark command by specifying the files or via *, thus selecting everything. Upon completion, we execute the done command, after which the dialogue with the system will start

 $ ls tmp/ $ cd tmp/ cwd is: /tmp/ $ ls dump.sql $ mark * 1 file marked. $ done 

The job will require the following

Volume (s) Storage (s) SD Device (s)

================================================= =========================



bitrixvm-bareos-client-Full-0011 bareos-server-sd bareos-sd



Volumes marked with "*" are online.



1 file selected to be restored.



Select the recovery task we need (point 2)



The defined Restore Job resources are:

1: Job-Full-restore

2: Job-bitrixvm-mysql-restore

3: Job-bitrixvm-Full-restore

Select Restore Job (1-3): 2



Set the client for which we perform the recovery (2)



Defined Clients:

1: bareos-fd

2: bitrixvm

3: win-fd

Select the Client (1-3): 2



Using Catalog "bareos-server"

Run Restore job

JobName: Job-bitrixvm-mysql-restore

Bootstrap: /var/lib/bareos/bareos-server.restore.1.bsr

Where: /tmp

Replace: Always

FileSet: bareos-fileset-bitrixvm-mysql

Backup Client: bitrixvm

Restore Client: bitrixvm

Format: Native

Storage: bareos-server-sd

When: 2016-10-16 11:26:54

Catalog: bareos-server

Priority: 10

Plugin Options: *None*

OK to run? (yes/mod/no): yes



yes, mod , . JobId.

 Job queued. JobId=76 

status dir . . , /tmp dump.sql.

 76 1 1.100 M OK 16-Oct-16 11:27 Job-bitrixvm-mysql-restore 

, Bareos , , , , ( MS SQL, Ceph, Gluster, LDAP).

---

SIM-CLOUD - Fail-safe cloud in Germany



Dedicated servers in reliable data centers in Germany!

Any configuration, quick build and free installation