{"id":12263,"date":"2019-02-16T12:16:37","date_gmt":"2019-02-16T11:16:37","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/"},"modified":"2023-06-15T16:33:00","modified_gmt":"2023-06-15T14:33:00","slug":"postgresql-barman-rsync-method-vs-streaming-method","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/","title":{"rendered":"PostgreSQL : barman rsync method vs streaming method"},"content":{"rendered":"

By Mouhamadou Diaw<\/strong><\/p>\n

Barman is a tool to perform backup and recovery for PostgreSQL databases. It can do backup using two methods:
\n-rsync\/ssh
\n-streaming
\nIn this blog I am going to explain how to use these two methods to backup a PostgreSQL database. Generally it is a good practice to dedicate a server for barman instead of installing it on the database server. My environment is described below
\npostgreSQL server<\/strong>: dbi-pg-essentials 192.168.22.101 Centos 7
\nbarman server<\/strong>: pgservertools 192.168.22.104 Oracle Linux 7
\npostgreSQL version<\/strong>: 11.1
\nbarman version<\/strong>: 2.6
\nThe first step is to install barman on the barman server pgservertools<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n<\/td>\n
\n
\n
[root@pgservertools network-scripts]<\/code># yum install\u00a0 barman.noarch barman-cli.noarch<\/code><\/div>\n
Loaded plugins: langpacks, ulninfo<\/code><\/div>\n
Resolving Dependencies<\/code><\/div>\n
--> Running transaction check<\/code><\/div>\n
---> Package barman.noarch 0:2.6-1.rhel7 will be installed<\/code><\/div>\n
---> Package barman-cli.noarch 0:1.3-1.rhel7.1 will be installed<\/code><\/div>\n
--> Finished Dependency Resolution<\/code><\/div>\n
<\/div>\n
Dependencies Resolved<\/code><\/div>\n
<\/div>\n
================================================================================<\/code><\/div>\n
\u00a0<\/code>Package\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Arch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Version\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Repository\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Size<\/code><\/div>\n
================================================================================<\/code><\/div>\n
Installing:<\/code><\/div>\n
\u00a0<\/code>barman\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 noarch\u00a0\u00a0\u00a0\u00a0 2.6-1.rhel7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 pgdg10-updates-testing\u00a0\u00a0\u00a0\u00a0 300 k<\/code><\/div>\n
\u00a0<\/code>barman-cli\u00a0\u00a0\u00a0\u00a0 noarch\u00a0\u00a0\u00a0\u00a0 1.3-1.rhel7.1\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 pgdg10-updates-testing\u00a0\u00a0\u00a0\u00a0\u00a0 14 k<\/code><\/div>\n
<\/div>\n
Transaction Summary<\/code><\/div>\n
================================================================================<\/code><\/div>\n
...<\/code><\/div>\n
...<\/code><\/div>\n
Installed:<\/code><\/div>\n
\u00a0\u00a0<\/code>barman.noarch 0:2.6-1.rhel7\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 barman-cli.noarch 0:1.3-1.rhel7.1<\/code><\/div>\n
<\/div>\n
Complete!<\/code><\/div>\n
[root@pgservertools network-scripts]<\/code>#<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The installation will create a linux user named barman.
\nAs the rsync method need connections without passwords between two servers for the barman user, we have to configure ssh keys
\nOn the server pgservertools (barman server) let\u2019s create keys with the user barman and then copy the public key to the database server dbi-pg-essentials for the user postgres<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n
25<\/div>\n
26<\/div>\n
27<\/div>\n
28<\/div>\n
29<\/div>\n
30<\/div>\n
31<\/div>\n
32<\/div>\n
33<\/div>\n
34<\/div>\n
35<\/div>\n
36<\/div>\n
37<\/div>\n
38<\/div>\n
39<\/div>\n
40<\/div>\n
41<\/div>\n
42<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ <\/code>ssh<\/code>-keygen<\/code><\/div>\n
Generating public<\/code>\/private<\/code> rsa key pair.<\/code><\/div>\n
Enter <\/code>file<\/code> in<\/code> which<\/code> to save the key (<\/code>\/var\/lib\/barman\/<\/code>.<\/code>ssh<\/code>\/id_rsa<\/code>):<\/code><\/div>\n
Created directory <\/code>'\/var\/lib\/barman\/.ssh'<\/code>.<\/code><\/div>\n
Enter passphrase (empty <\/code>for<\/code> no passphrase):<\/code><\/div>\n
Enter same passphrase again:<\/code><\/div>\n
Your identification has been saved <\/code>in<\/code> \/var\/lib\/barman\/<\/code>.<\/code>ssh<\/code>\/id_rsa<\/code>.<\/code><\/div>\n
Your public key has been saved <\/code>in<\/code> \/var\/lib\/barman\/<\/code>.<\/code>ssh<\/code>\/id_rsa<\/code>.pub.<\/code><\/div>\n
The key fingerprint is:<\/code><\/div>\n
f4:b7:6b:6e:38:25:ae:be:7f:9a:34:03:a1:1c:a0:ac barman@pgservertools<\/code><\/div>\n
The key's randomart image is:<\/code><\/div>\n
+--[ RSA 2048]----+<\/code><\/div>\n
|\u00a0\u00a0\u00a0 .\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
| . . .\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
|\u00a0 o\u00a0\u00a0 . o\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
| .\u00a0\u00a0 . + o\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 |<\/code><\/div>\n
|E\u00a0\u00a0\u00a0\u00a0 o S . .\u00a0\u00a0\u00a0 |<\/code><\/div>\n
|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 .....\u00a0\u00a0 |<\/code><\/div>\n
|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 .++.\u00a0\u00a0\u00a0 |<\/code><\/div>\n
|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 .+++.\u00a0\u00a0 |<\/code><\/div>\n
|\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 .+++Bo\u00a0\u00a0\u00a0 |<\/code><\/div>\n
+-----------------+<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$ <\/code><\/div>\n
<\/div>\n
<\/div>\n
-<\/code>bash<\/code>-4.2$ <\/code>cd<\/code> .<\/code>ssh<\/code>\/<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$ <\/code>ls<\/code><\/div>\n
id_rsa\u00a0 id_rsa.pub<\/code><\/div>\n
<\/div>\n
<\/div>\n
-<\/code>bash<\/code>-4.2$ <\/code>ssh<\/code>-copy-<\/code>id<\/code> postgres@dbi-pg-essentials<\/code><\/div>\n
The authenticity of host <\/code>'dbi-pg-essentials (192.168.22.101)'<\/code> can't be established.<\/code><\/div>\n
ECDSA key fingerprint is 33:65:38:f4:eb:5b:f4:10:d3:36:7b:ea:5a:70:33:18.<\/code><\/div>\n
Are you sure you want to <\/code>continue<\/code> connecting (<\/code>yes<\/code>\/no<\/code>)? <\/code>yes<\/code><\/div>\n
\/bin\/ssh-copy-id<\/code>: INFO: attempting to log <\/code>in<\/code> with the new key(s), to filter out any that are already installed<\/code><\/div>\n
\/bin\/ssh-copy-id<\/code>: INFO: 1 key(s) remain to be installed -- <\/code>if<\/code> you are prompted now it is to <\/code>install<\/code> the new keys<\/code><\/div>\n
postgres@dbi-pg-essentials's password:<\/code><\/div>\n
<\/div>\n
Number of key(s) added: 1<\/code><\/div>\n
<\/div>\n
Now try logging into the machine, with:\u00a0\u00a0 <\/code>\"ssh 'postgres@dbi-pg-essentials'\"<\/code><\/div>\n
and check to <\/code>make<\/code> sure that only the key(s) you wanted were added.<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

If everything is fine, barman should be able to connect to database server as postgres linux user without password<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ <\/code>hostname<\/code><\/div>\n
pgservertools.localdomain<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$ <\/code>id<\/code><\/div>\n
uid=994(barman) gid=992(barman) <\/code>groups<\/code>=992(barman) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$ <\/code>ssh<\/code> postgres@dbi-pg-essentials <\/code>hostname<\/code><\/div>\n
dbi-pg-essentials<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

On the database server I also have installed the package barman-cli.noarch which will allow us to use the command barman-wal-archive. We will talk about this later.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n<\/td>\n
\n
\n
[root@dbi-pg-essentials ~]<\/code># yum install barman-cli.noarch<\/code><\/div>\n
Loaded plugins: fastestmirror<\/code><\/div>\n
dbipgessentials\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 3.6 kB\u00a0\u00a0\u00a0\u00a0 00:00<\/code><\/div>\n
edb-repos\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 | 2.4 kB\u00a0\u00a0\u00a0\u00a0 00:00<\/code><\/div>\n
\u2026<\/code><\/div>\n
\u2026<\/code><\/div>\n
Running transaction check<\/code><\/div>\n
Running transaction <\/code>test<\/code><\/div>\n
Transaction <\/code>test<\/code> succeeded<\/code><\/div>\n
Running transaction<\/code><\/div>\n
\u00a0\u00a0<\/code>Installing : barman-cli-1.3-1.rhel7.1.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1<\/code>\/1<\/code><\/div>\n
\u00a0\u00a0<\/code>Verifying\u00a0 : barman-cli-1.3-1.rhel7.1.noarch\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 1<\/code>\/1<\/code><\/div>\n
<\/div>\n
Installed:<\/code><\/div>\n
\u00a0\u00a0<\/code>barman-cli.noarch 0:1.3-1.rhel7.1<\/code><\/div>\n
<\/div>\n
Complete!<\/code><\/div>\n
[root@dbi-pg-essentials ~]<\/code># <\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

rsync backup<\/h3>\n

As specified earlier in this case the backup is done using rsync. But we have many ways to ship WAL to the barman server. So before talking about barman configuration let\u2019s take a moment to see the WAL shipping
\n1- With WAL archiving<\/strong>
\nTo better understand I put this picture I got from the barman documentation <\/a>. As we see backup is done via rsync and the WAL are sent via the barman-wal-archive. This utility comes with barman 2.6.
\nBefore barman 2.6 the rsync command was used to send WAL to barman.
\nIn the documentation we can find that using barman-wal-archive instead of rsync\/SSH reduces the risk of data corruption of the shipped WAL file on the Barman server.
\n\"rsync_1\"<\/a>
\nThe use of barman_wal_archive is done via the postgresql.conf file on the database server. It appears on the value of the parameter archive_command. Below values in my postgresql.conf file.<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials PG1]$ <\/code>grep<\/code> -E\u00a0 <\/code>\"archive_mode|wal_level|archive_command\"<\/code> postgresql.conf<\/code><\/div>\n
wal_level = replica\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code># minimal, replica, or logical<\/code><\/div>\n
archive_mode = on\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code># enables archiving; off, on, or always<\/code><\/div>\n
archive_command = <\/code>'barman-wal-archive 192.168.22.104 pgserver11 %p'<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 # command to use to archive a logfile segment<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Before barman 2.6 we would use following for archive_command to send WAL to barman server<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n<\/td>\n
\n
\n
archive_command = <\/code>'rsync -a\u00a0 %p\u00a0 barman@pgservertools:\/var\/lib\/barman\/pgserver11\/incoming\/%f'<\/code> # command to use to archive a logfile segment<\/code><\/div>\n
[postgres@dbi-pg-essentials PG1]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

2- With WAL archiving and WAL streaming<\/strong>
\nThis picture from barman documentation will help to better understand
\n\"rsync_2\"<\/a>
\nTo use WAL streaming to the barman server, we need pg_receivewal (pg_receivexlog up to PostgreSQL 10) to be installed on the barman server. Be careful of the version of pg_receivewal. In my case I installed the version 11.1 as my PostgreSQL is 11.1<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
[postgres@pgservertools bin]$ <\/code>\/usr\/pgsql-11\/bin\/pg_receivewal<\/code> -V<\/code><\/div>\n
pg_receivewal (PostgreSQL) 11.1<\/code><\/div>\n
[postgres@pgservertools bin]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

A streaming connection also should be configured and the parameter streaming_archiver should be set to on.
\nNow to resume let\u2019s say that I want to configure barman with
\n-rsync method
\n-using barman_wal_archive and WAL streaming
\nThe barman file configuration \/etc\/barman.conf should be like<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n<\/td>\n
\n
\n
[postgres@pgservertools bin]$ <\/code>cat<\/code> \/etc\/barman<\/code>.conf | <\/code>grep<\/code> -<\/code>v<\/code>\u00a0 ^\\;<\/code><\/div>\n
<\/div>\n
[barman]<\/code><\/div>\n
barman_user = barman<\/code><\/div>\n
configuration_files_directory = <\/code>\/etc\/barman<\/code>.d<\/code><\/div>\n
barman_home = <\/code>\/var\/lib\/barman<\/code><\/div>\n
log_file = <\/code>\/var\/log\/barman\/barman<\/code>.log<\/code><\/div>\n
log_level = INFO<\/code><\/div>\n
compression = <\/code>gzip<\/code><\/div>\n
retention_policy = REDUNDANCY 2<\/code><\/div>\n
<\/div>\n
[pgserver11]<\/code><\/div>\n
description = <\/code>\"Main DB Server\"<\/code><\/div>\n
ssh_command = <\/code>ssh<\/code> postgres@dbi-pg-essentials<\/code><\/div>\n
streaming_conninfo=host=192.168.22.101 user=postgres<\/code><\/div>\n
conninfo=host=192.168.22.101 user=postgres<\/code><\/div>\n
backup_method = <\/code>rsync<\/code><\/div>\n
streaming_archiver = on<\/code><\/div>\n
archiver = on<\/code><\/div>\n
path_prefix=<\/code>\/usr\/pgsql-11\/bin\/<\/code><\/div>\n
[postgres@pgservertools bin]$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And the postgresql.conf should contain following entries<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials PG1]$ <\/code>grep<\/code> -E\u00a0 <\/code>\"archive_mode|wal_level|archive_command\"<\/code> postgresql.conf<\/code><\/div>\n
wal_level = replica\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code># minimal, replica, or logical<\/code><\/div>\n
archive_mode = on\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code># enables archiving; off, on, or always<\/code><\/div>\n
archive_command = <\/code>'barman-wal-archive 192.168.22.104 pgserver11 %p'<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 # command to use to archive a logfile segment<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

The first thing is to test that the barman configuration is fine for the PostgreSQL database. The check command should not return any errors. On the barman server with the user barman<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman check pgserver11<\/code><\/div>\n
Server pgserver11:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>PostgreSQL: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>is_superuser: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>PostgreSQL streaming: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>wal_level: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>directories: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>retention policy settings: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>backup maximum age: OK (no last_backup_maximum_age provided)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>compression settings: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>failed backups: OK (there are 0 failed backups)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>minimum redundancy requirements: OK (have 0 backups, expected at least 0)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>ssh<\/code>: OK (PostgreSQL server)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>not <\/code>in<\/code> recovery: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>archive_mode: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>archive_command: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>continuous archiving: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_receivexlog: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_receivexlog compatible: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>receive-wal running: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>archiver errors: OK<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Now we can launch a backup using the backup command on the barman server with the user barman<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman backup pgserver11<\/code><\/div>\n
Starting backup using <\/code>rsync<\/code>-exclusive method <\/code>for<\/code> server pgserver11 <\/code>in<\/code> \/var\/lib\/barman\/pgserver11\/base\/20190215T153350<\/code><\/div>\n
Backup start at LSN: 0<\/code>\/2E000060<\/code> (00000005000000000000002E, 00000060)<\/code><\/div>\n
This is the first backup <\/code>for<\/code> server pgserver11<\/code><\/div>\n
Starting backup copy via <\/code>rsync<\/code>\/SSH<\/code> for<\/code> 20190215T153350<\/code><\/div>\n
Copy <\/code>done<\/code> (<\/code>time<\/code>: 12 seconds)<\/code><\/div>\n
This is the first backup <\/code>for<\/code> server pgserver11<\/code><\/div>\n
WAL segments preceding the current backup have been found:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>00000005000000000000002D from server pgserver11 has been removed<\/code><\/div>\n
Asking PostgreSQL server to finalize the backup.<\/code><\/div>\n
Backup size: 74.1 MiB<\/code><\/div>\n
Backup end at LSN: 0<\/code>\/2E000168<\/code> (00000005000000000000002E, 00000168)<\/code><\/div>\n
Backup completed (start <\/code>time<\/code>: 2019-02-15 15:33:52.392144, elapsed <\/code>time<\/code>: 15 seconds)<\/code><\/div>\n
Processing xlog segments from <\/code>file<\/code> archival <\/code>for<\/code> pgserver11<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>00000005000000000000002E<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>00000005000000000000002E.00000060.backup<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

We can list the existing backup. On the barman server with the barman user<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman list-backup pgserver11<\/code><\/div>\n
pgserver11 20190215T153350 - Fri Feb 15 15:34:08 2019 - Size: 74.1 MiB - WAL Size: 0 B<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Streaming backup<\/h3>\n

Since the version 2.0, barman supports streaming replication for backup. This method uses the native pg_basebackup
\n1- Streaming-only backup<\/strong>
\nThis picture is from the barman documentation may help
\n\"stream_1\"<\/a>
\nAs we can see, In this case backup are done via streaming. WAL are also using streaming protocol.
\n2- WAL archiving and WAL streaming<\/strong>
\nOnce again following picture may help
\n\"stream_2\"<\/a>
\nIn this case we configure standard archiving as well to implement a more robust architecture<\/p>\n

For example to implement a barman configuration with streaming backup WAL streaming and WAL archiving, the \/etc\/barman.conf should be like<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n<\/td>\n
\n
\n
[postgres@pgservertools bin]$ <\/code>cat<\/code> \/etc\/barman<\/code>.conf | <\/code>grep<\/code> -<\/code>v<\/code>\u00a0 ^\\;<\/code><\/div>\n
<\/div>\n
[barman]<\/code><\/div>\n
barman_user = barman<\/code><\/div>\n
configuration_files_directory = <\/code>\/etc\/barman<\/code>.d<\/code><\/div>\n
barman_home = <\/code>\/var\/lib\/barman<\/code><\/div>\n
log_file = <\/code>\/var\/log\/barman\/barman<\/code>.log<\/code><\/div>\n
log_level = INFO<\/code><\/div>\n
compression = <\/code>gzip<\/code><\/div>\n
retention_policy = REDUNDANCY 2<\/code><\/div>\n
<\/div>\n
[pgserver11]<\/code><\/div>\n
description = <\/code>\"Main DB Server\"<\/code><\/div>\n
ssh_command = <\/code>ssh<\/code> postgres@dbi-pg-essentials<\/code><\/div>\n
streaming_conninfo=host=192.168.22.101 user=postgres<\/code><\/div>\n
conninfo=host=192.168.22.101 user=postgres<\/code><\/div>\n
backup_method = postgres<\/code><\/div>\n
streaming_archiver = on<\/code><\/div>\n
archiver = on<\/code><\/div>\n
slot_name=barman<\/code><\/div>\n
path_prefix=<\/code>\/usr\/pgsql-11\/bin\/<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

and the postgressql.conf<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n<\/td>\n
\n
\n
[postgres@dbi-pg-essentials PG1]$ <\/code>grep<\/code> -E\u00a0 <\/code>\"archive_mode|wal_level|archive_command\"<\/code> postgresql.conf<\/code><\/div>\n
wal_level = replica\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code># minimal, replica, or logical<\/code><\/div>\n
archive_mode = on\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/code># enables archiving; off, on, or always<\/code><\/div>\n
archive_command = <\/code>'barman-wal-archive 192.168.22.104 pgserver11 %p'<\/code>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 # command to use to archive a logfile segment<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

So the check should not return any errors<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n
16<\/div>\n
17<\/div>\n
18<\/div>\n
19<\/div>\n
20<\/div>\n
21<\/div>\n
22<\/div>\n
23<\/div>\n
24<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman check pgserver11<\/code><\/div>\n
Server pgserver11:<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>PostgreSQL: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>is_superuser: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>PostgreSQL streaming: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>wal_level: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>replication slot: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>directories: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>retention policy settings: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>backup maximum age: OK (no last_backup_maximum_age provided)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>compression settings: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>failed backups: OK (there are 0 failed backups)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>minimum redundancy requirements: OK (have 1 backups, expected at least 0)<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_basebackup: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_basebackup compatible: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_basebackup supports tablespaces mapping: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>archive_mode: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>archive_command: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>continuous archiving: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_receivexlog: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>pg_receivexlog compatible: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>receive-wal running: OK<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>archiver errors: OK<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

And we launch a backup, we can see that barman is using pg_basebackup<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n
4<\/div>\n
5<\/div>\n
6<\/div>\n
7<\/div>\n
8<\/div>\n
9<\/div>\n
10<\/div>\n
11<\/div>\n
12<\/div>\n
13<\/div>\n
14<\/div>\n
15<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman backup pgserver11<\/code><\/div>\n
Starting backup using postgres method <\/code>for<\/code> server pgserver11 <\/code>in<\/code> \/var\/lib\/barman\/pgserver11\/base\/20190215T160757<\/code><\/div>\n
Backup start at LSN: 0<\/code>\/2F0001A8<\/code> (00000005000000000000002F, 000001A8)<\/code><\/div>\n
Starting backup copy via pg_basebackup <\/code>for<\/code> 20190215T160757<\/code><\/div>\n
Copy <\/code>done<\/code> (<\/code>time<\/code>: 11 seconds)<\/code><\/div>\n
Finalising the backup.<\/code><\/div>\n
Backup size: 73.9 MiB<\/code><\/div>\n
Backup end at LSN: 0<\/code>\/31000060<\/code> (000000050000000000000031, 00000060)<\/code><\/div>\n
Backup completed (start <\/code>time<\/code>: 2019-02-15 16:07:57.919595, elapsed <\/code>time<\/code>: 11 seconds)<\/code><\/div>\n
Processing xlog segments from <\/code>file<\/code> archival <\/code>for<\/code> pgserver11<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>000000050000000000000030<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>000000050000000000000031<\/code><\/div>\n
Processing xlog segments from streaming <\/code>for<\/code> pgserver11<\/code><\/div>\n
\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/code>000000050000000000000030<\/code><\/div>\n
-<\/code>bash<\/code>-4.2$<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Available backups are now<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n
2<\/div>\n
3<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman list-backup pgserver11<\/code><\/div>\n
pgserver11 20190215T160757 - Fri Feb 15 16:08:09 2019 - Size: 73.9 MiB - WAL Size: 0 B<\/code><\/div>\n
pgserver11 20190215T153350 - Fri Feb 15 15:34:08 2019 - Size: 74.1 MiB - WAL Size: 48.3 KiB<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

To restore with barman, we use the command recover. For example the following command will restore the backup 20190215T160757 on server dbi-pg-essentials_3 in the directory \/u02\/pgdata\/PGRESTORE<\/p>\n

\n
\n\n\n\n
\n
1<\/div>\n<\/td>\n
\n
\n
-<\/code>bash<\/code>-4.2$ barman recover --remote-<\/code>ssh<\/code>-<\/code>command<\/code> \"ssh postgres@dbi-pg-essentials_3\"<\/code> pgserver11 20190215T160757 <\/code>\/u02\/pgdata\/PGRESTORE<\/code><\/div>\n<\/div>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<\/div>\n

Conclusion<\/h3>\n

In this blog I have tried to explain different scenarios for using barman. We talked about rsync method and streaming methods for backups. Before starting the setup a choice must be done. One can check documentation for more information<\/p>\n

Ref: http:\/\/docs.pgbarman.org\/<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Barman is a tool to perform backup and recovery for PostgreSQL databases. It can do backup using two methods: -rsync\/ssh -streaming In this blog I am going to explain how to use these two methods to backup a PostgreSQL database. Generally it is a good practice to dedicate a server for barman […]<\/p>\n","protected":false},"author":27,"featured_media":12264,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229,83],"tags":[329,1577,1323,1578,1579,1105],"type_dbi":[],"class_list":["post-12263","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-database-administration-monitoring","category-postgresql","tag-barman","tag-barman-wal-archive","tag-postgresql-11","tag-postgresql-backup-and-recovery","tag-rsync","tag-streaming"],"acf":[],"yoast_head":"\nPostgreSQL : barman rsync method vs streaming method - dbi Blog<\/title>\n<meta name=\"description\" content=\"barman,postgresql 11, barman-wal-archive,streaming,rsync\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL : barman rsync method vs streaming method\" \/>\n<meta property=\"og:description\" content=\"barman,postgresql 11, barman-wal-archive,streaming,rsync\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2019-02-16T11:16:37+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-15T14:33:00+00:00\" \/>\n<meta property=\"og:image\" content=\"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png\" \/>\n\t<meta property=\"og:image:width\" content=\"629\" \/>\n\t<meta property=\"og:image:height\" content=\"297\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Oracle Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Oracle Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"PostgreSQL : barman rsync method vs streaming method\",\"datePublished\":\"2019-02-16T11:16:37+00:00\",\"dateModified\":\"2023-06-15T14:33:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\"},\"wordCount\":756,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png\",\"keywords\":[\"Barman\",\"barman-wal-archive\",\"PostgreSQL 11\",\"postgresql backup and recovery\",\"rsync\",\"streaming\"],\"articleSection\":[\"Database Administration & Monitoring\",\"PostgreSQL\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\",\"name\":\"PostgreSQL : barman rsync method vs streaming method - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png\",\"datePublished\":\"2019-02-16T11:16:37+00:00\",\"dateModified\":\"2023-06-15T14:33:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"barman,postgresql 11, barman-wal-archive,streaming,rsync\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png\",\"width\":629,\"height\":297},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL : barman rsync method vs streaming method\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\",\"name\":\"Oracle Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g\",\"caption\":\"Oracle Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"PostgreSQL : barman rsync method vs streaming method - dbi Blog","description":"barman,postgresql 11, barman-wal-archive,streaming,rsync","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/","og_locale":"en_US","og_type":"article","og_title":"PostgreSQL : barman rsync method vs streaming method","og_description":"barman,postgresql 11, barman-wal-archive,streaming,rsync","og_url":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/","og_site_name":"dbi Blog","article_published_time":"2019-02-16T11:16:37+00:00","article_modified_time":"2023-06-15T14:33:00+00:00","og_image":[{"width":629,"height":297,"url":"http:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png","type":"image\/png"}],"author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"PostgreSQL : barman rsync method vs streaming method","datePublished":"2019-02-16T11:16:37+00:00","dateModified":"2023-06-15T14:33:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/"},"wordCount":756,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png","keywords":["Barman","barman-wal-archive","PostgreSQL 11","postgresql backup and recovery","rsync","streaming"],"articleSection":["Database Administration & Monitoring","PostgreSQL"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/","url":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/","name":"PostgreSQL : barman rsync method vs streaming method - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png","datePublished":"2019-02-16T11:16:37+00:00","dateModified":"2023-06-15T14:33:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"barman,postgresql 11, barman-wal-archive,streaming,rsync","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/rsync_1.png","width":629,"height":297},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/postgresql-barman-rsync-method-vs-streaming-method\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL : barman rsync method vs streaming method"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee","name":"Oracle Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/f711f7cd2c9b09bf2627133755b569fb5be0694810cfd33033bdd095fedba86d?s=96&d=mm&r=g","caption":"Oracle Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/oracle-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12263","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=12263"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12263\/revisions"}],"predecessor-version":[{"id":25937,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/12263\/revisions\/25937"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/12264"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=12263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=12263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=12263"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=12263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}