{"id":10834,"date":"2018-02-15T15:41:26","date_gmt":"2018-02-15T14:41:26","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/"},"modified":"2023-06-09T16:53:48","modified_gmt":"2023-06-09T14:53:48","slug":"backup-and-restore-postgresql-with-pgbackrest-ii","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/","title":{"rendered":"Backup and Restore PostgreSQL with PgBackRest II"},"content":{"rendered":"

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

In a precedent blog<\/a> I shown a basic utilization of PgBackRest<\/a> which is a tool to backup and restore PostgreSQL databases. In this blog I am going to talk some useful features of this tool. In practical examples we will see some tasks we can do with this tool. Of course the official documentation remains the best source of knowledges.<\/p>\n

Encryption<\/u>
\nNowadays encryption of backups is very critical and is mandatory for many companies. PgBackRest allows us to encrypt the repository where backups are stored. A passphrase is used to encrypt\/decrypt files of the repository. As you may already know, it is recommended to use a strong passphrase. In the following demonstration we use the openssl to generate a passphrase.
\n
\n[postgres@pgserver ~]$ openssl rand -base64 48
\nFhXg7oW2pZb9UICZ4iYZPn3X4I6fF0ni7IL6QjaB1IL8qz4LIrP+GW+XqCZqIi3w
\n[postgres@pgserver ~]$
\n<\/code>
\nOnce the passphrase generated, we can update the PgBackRest configuration file with
\n2 options: repo-cipher-pass and repo-cipher-type
\n
\n[postgres@pgserver clustpgserver]$ cat \/etc\/pgbackrest.conf
\n[global]
\nrepo-path=\/var\/lib\/pgbackrest
\nrepo-cipher-pass=FhXg7oW2pZb9UICZ4iYZPn3X4I6fF0ni7IL6QjaB1IL8qz4LIrP+GW+XqCZqIi3w<\/strong>
\nrepo-cipher-type=aes-256-cbc<\/strong>
\n[clustpgserver]
\ndb-path=\/var\/lib\/pgsql\/10\/data
\nretention-full=2
\n<\/code>
\nThe next step is to create the stanza
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 stanza-create
\n2018-02-13 13:54:50.447 P00 INFO: stanza-create command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --stanza=clustpgserver
\n2018-02-13 13:55:04.520 P00 INFO: stanza-create command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nAs we can see the system automatically detect that the repository is encrypted and then will rewrite the command including the –repo-cipher-pass and the –repo-cipher-type options. After the creation of the stanza we can check the status of our stanza
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 check
\n2018-02-13 13:56:08.999 P00 INFO: check command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --stanza=clustpgserver
\n2018-02-13 13:57:08.026 P00 INFO: WAL segment 00000002000000000000004C successfully stored in the archive at '\/var\/lib\/pgbackrest\/archive\/clustpgserver\/10-1\/0000000200000000\/00000002000000000000004C-f5ced60cd351d74a91c9ce2e913b761144165e28.gz'
\n2018-02-13 13:57:08.030 P00 INFO: check command end: completed successfully
\n<\/code>
\nEverything seems fine, so let’s run a backup. Note that outputs are truncated
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 backup
\n2018-02-13 14:01:40.012 P00 INFO: backup command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --retention-full=2 --stanza=clustpgserver
\nWARN: no prior backup exists, incr backup has been changed to full
\n2018-02-13 14:01:54.118 P00 INFO: execute non-exclusive pg_start_backup() with label \"pgBackRest backup started at 2018-02-13 14:01:52\": backup begins after the next regular checkpoint completes
\n...
\ntype=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --retention-archive=2 --retention-full=2 --stanza=clustpgserver
\n2018-02-13 14:35:08.281 P00 INFO: full backup total < 2 - using oldest full backup for 10-1 archive retention
\n2018-02-13 14:35:08.801 P00 INFO: expire command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nIn a non-encrypted repository, file backup.info can be read. Now with encryption the if we try to read the file backup.info in the repository, we cannot.
\n
\n[postgres@pgserver clustpgserver]$ less \/var\/lib\/pgbackrest\/backup\/clustpgserver\/backup.info
\n\"\/var\/lib\/pgbackrest\/backup\/clustpgserver\/backup.info\" may be a binary file. See it anyway?
\n<\/code>
\nAnd using the command strings, we can see that the file is encrypted.
\n
\n[postgres@pgserver clustpgserver]$ strings \/var\/lib\/pgbackrest\/backup\/clustpgserver\/backup.info
\nSalted__Fx
\n.;Ru
\ncz4@
\ndo:t
\npi3\"E
\nVUSO
\n}a.R*
\nWx5M
\n,?,W
\n3CXWB
\n[postgres@pgserver clustpgserver]$
\n<\/code>
\nFrom now, backups cannot be used unless the password is provided.<\/p>\n

Restore in another location<\/u>
\nPgBackRest allows to restore to another location. This can be useful if we want to duplicate our cluster on the same server or to another server. In the following demonstration, let\u2019s duplicate on the same server.
\nThe data directory of the source cluster is \/var\/lib\/pgsql\/10\/data
\n
\npostgres=# show data_directory;
\ndata_directory
\n------------------------
\n\/var\/lib\/pgsql\/10\/data
\n(1 row)
\npostgres=#
\n<\/code>
\nTo duplicate to a new data directory \/u01\/devdata for example, the option –db-path is used
\n
\n[postgres@pgserver log]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-path=\/u01\/devdata restore
\n\u2026
\n\u2026
\n2018-02-14 09:40:05.755 P01 INFO: restore file \/u01\/devdata\/base\/1\/13657 (0B, 100%)
\n2018-02-14 09:40:05.773 P01 INFO: restore file \/u01\/devdata\/base\/1\/13652 (0B, 100%)
\n2018-02-14 09:40:05.811 P01 INFO: restore file \/u01\/devdata\/base\/1\/13647 (0B, 100%)
\n2018-02-14 09:40:05.983 P01 INFO: restore file \/u01\/devdata\/base\/1\/13642 (0B, 100%)
\n2018-02-14 09:40:06.067 P00 INFO: write \/u01\/devdata\/recovery.conf
\n2018-02-14 09:40:14.403 P00 INFO: restore global\/pg_control (performed last to ensure aborted restores cannot be started)
\n2018-02-14 09:40:30.187 P00 INFO: restore command end: completed successfully
\n<\/code>
\nAfter the duplicate don\u2019t forget to change the port (as we are in the same server) and then start your new cluster
\n
\npostgres=# show data_directory ;
\ndata_directory
\n----------------
\n\/u01\/devdata
\n(1 row)
\npostgres=#
\n<\/code><\/p>\n

Restore specific databases<\/u>
\nWith PgBackRest, we can restore specific user databases. Note that built-in databases (template0, template1 and postgres) are always restored.
\nLet\u2019s show an example. In our source cluster we actually have two databases test and sandbox.
\n
\nsandbox=# l
\nList of databases
\nName | Owner | Encoding | Collate | Ctype | Access privileges
\n-----------+----------+----------+-------------+-------------+-----------------------
\npostgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
\nsandbox | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
\ntemplate0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c\/postgres +
\n| | | | | postgres=CTc\/postgres
\ntemplate1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c\/postgres +
\n| | | | | postgres=CTc\/postgres
\ntest | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
\n(5 rows)
\n<\/code>
\nIn sandbox we have a table mytab with 2 rows
\n
\nsandbox=# c sandbox
\nYou are now connected to database \"sandbox\" as user \"postgres\".
\nsandbox=# table mytab;
\nid
\n----
\n1
\n2
\n(2 rows)
\n<\/code>
\nNow let\u2019s restore the cluster but only with test database, the option –db-include will be used.
\n
\n[postgres@pgserver log]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-path=\/u01\/devdata --db-include=test restore
\n2018-02-14 10:11:00.948 P00 INFO: restore command begin 1.28: --db-include=test=1 --db1-path=\/u01\/devdata --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --stanza=clustpgserver
\n2018-02-14 10:11:05.137 P00 INFO: restore backup set 20180214-095439F_20180214-100446I
\n2018-02-14 10:11:25.110 P00 INFO: remap $PGDATA directory to \/u01\/devdata
\n...
\n<\/code>
\nAfter the restore completed, let\u2019s start the new cluster and let\u2019s verify present databases.
\n
\n[postgres@pgserver devdata]$ psql -p 5436
\npsql (10.1)
\nType \"help\" for help.
\npostgres=# l
\nList of databases
\nName | Owner | Encoding | Collate | Ctype | Access privileges
\n-----------+----------+----------+-------------+-------------+-----------------------
\npostgres | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
\nsandbox | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
\ntemplate0 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c\/postgres +
\n| | | | | postgres=CTc\/postgres
\ntemplate1 | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 | =c\/postgres +
\n| | | | | postgres=CTc\/postgres
\ntest | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
\n(5 rows)
\n<\/code>
\nWhat!! the sandbox is still present despite the use of option –include-db=test. But if we try to connect to sandbox database. We get an error.
\n
\npostgres=# c sandbox
\nFATAL: relation mapping file \"base\/24581\/pg_filenode.map\" contains invalid data
\nPrevious connection kept
\npostgres=#
\n<\/code>
\nAnd if we compare at OS level the size of files of the database at the source cluster and at the target
\n
\n[postgres@pgserver log]$ du -sh \/var\/lib\/pgsql\/10\/data\/base\/24581
\n7.8M \/var\/lib\/pgsql\/10\/data\/base\/24581
\n[postgres@pgserver log]$ du -sh \/u01\/devdata\/base\/24581
\n16K \/u01\/devdata\/base\/24581
\n[postgres@pgserver log]$
\n<\/code>
\nWe can see that at the target cluster, sandbox uses less disk space during the selective restore than it would have if the entire database had been restored. To finish the selective restore, we have to manually drop the sandbox database. Indeed PgBackRest cannot automatically drop the database because the cluster is not accessible until the recovery process finishes.
\n
\npostgres=# drop database sandbox;
\nDROP DATABASE
\npostgres=#
\n<\/code><\/p>\n

Automatic cleanup of expired backups<\/u>
\nAnother nice feature of PgBackRest is that expired backups are automatically removed.
\nIf we check our pgbackrest.conf file, we see that the retention-full is set to 2. This means that 2 full backups will be maintained. So if we do a third full backup, the first full backup and all corresponding incremental and differential backups will be expired and removed
\n
\n[postgres@pgserver log]$ cat \/etc\/pgbackrest.conf
\n[global]
\nrepo-path=\/var\/lib\/pgbackrest
\nrepo-cipher-pass=FhXg7oW2pZb9UICZ4iYZPn3X4I6fF0ni7IL6QjaB1IL8qz4LIrP+GW+XqCZqIi3w
\nrepo-cipher-type=aes-256-cbc
\n[clustpgserver]
\ndb-path=\/var\/lib\/pgsql\/10\/data
\nretention-full=2
\n[postgres@pgserver log]$
\n<\/code>
\nLet\u2019s do a quick demonstration. Actually we have 2 full backups
\n
\n[postgres@pgserver log]$ pgbackrest --stanza=clustpgserver info
\nstanza: clustpgserver
\nstatus: ok
\ndb (current)
\nwal archive min\/max (10-1): 00000002000000000000004E \/ 000000020000000000000056
\nfull backup: 20180213-140152F
\ntimestamp start\/stop: 2018-02-13 14:01:52 \/ 2018-02-13 14:32:00
\nwal start\/stop: 00000002000000000000004E \/ 00000002000000000000004E
\ndatabase size: 577MB, backup size: 577MB
\nrepository size: 28.8MB, repository backup size: 28.8MB
\nincr backup: 20180213-140152F_20180213-152509I
\ntimestamp start\/stop: 2018-02-14 09:31:03 \/ 2018-02-14 09:33:17
\nwal start\/stop: 000000020000000000000052 \/ 000000020000000000000052
\ndatabase size: 30.7MB, backup size: 285.3KB
\nrepository size: 3.6MB, repository backup size: 24.3KB
\nbackup reference list: 20180213-140152F
\nfull backup: 20180214-095439F
\ntimestamp start\/stop: 2018-02-14 09:54:39 \/ 2018-02-14 09:58:53
\nwal start\/stop: 000000020000000000000054 \/ 000000020000000000000054
\ndatabase size: 30.7MB, backup size: 30.7MB
\nrepository size: 3.6MB, repository backup size: 3.6MB
\nincr backup: 20180214-095439F_20180214-100446I
\ntimestamp start\/stop: 2018-02-14 10:04:46 \/ 2018-02-14 10:07:43
\nwal start\/stop: 000000020000000000000056 \/ 000000020000000000000056
\ndatabase size: 38.3MB, backup size: 7.6MB
\nrepository size: 4.5MB, repository backup size: 928.5KB
\nbackup reference list: 20180214-095439F
\n[postgres@pgserver log]$
\n<\/code>
\nAnd we can confirm by executing a simple ls in the repository where backups are stored
\n
\n[postgres@pgserver clustpgserver]$ ls -ld *
\ndrwxr-x---. 3 postgres postgres 69 Feb 13 14:32 20180213-140152F
\ndrwxr-x---. 3 postgres postgres 69 Feb 14 09:33 20180213-140152F_20180213-152509I
\ndrwxr-x---. 3 postgres postgres 69 Feb 14 09:59 20180214-095439F
\ndrwxr-x---. 3 postgres postgres 69 Feb 14 10:07 20180214-095439F_20180214-100446I
\ndrwxr-x---. 3 postgres postgres 17 Feb 13 14:33 backup.history
\n-rw-r-----. 1 postgres postgres 2992 Feb 14 10:08 backup.info
\n-rw-r-----. 1 postgres postgres 2992 Feb 14 10:08 backup.info.copy
\nlrwxrwxrwx. 1 postgres postgres 33 Feb 14 10:08 latest -> 20180214-095439F_20180214-100446I
\n[postgres@pgserver clustpgserver]$ ls -ld
\ndrwxr-x---. 7 postgres postgres 4096 Feb 14 10:08 .
\n[postgres@pgserver clustpgserver]$ ls -ld *
\n<\/code>
\nNow let\u2019s do a third full backup
\n
\n[postgres@pgserver clustpgserver]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 --type=full backup
\n2018-02-14 10:55:52.250 P00 INFO: backup command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --retention-full=2 --stanza=clustpgserver --type=full
\n\u2026
\n2018-02-14 11:19:02.001 P00 INFO: backup command end: completed successfully
\n2018-02-14 11:19:02.107 P00 INFO: expire command begin 1.28: --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --retention-archive=2 --retention-full=2 --stanza=clustpgserver
\n2018-02-14 11:19:02.928 P00 INFO: expire full backup set: 20180213-140152F, 20180213-140152F_20180213-152509I
\n2018-02-14 11:22:08.759 P00 INFO: remove expired backup 20180213-140152F_20180213-152509I
\n2018-02-14 11:22:09.000 P00 INFO: remove expired backup 20180213-140152F<\/strong>
\n2018-02-14 11:22:49.387 P00 INFO: expire command end: completed successfully
\n[postgres@pgserver clustpgserver]$
\n<\/code>
\nWe can see that at the end of backups, some old backups are expired and removed. We can also confirm this by listing files in the repository
\n
\n[postgres@pgserver clustpgserver]$ ls -ld *
\ndrwxr-x---. 3 postgres postgres 69 Feb 14 09:59 20180214-095439F
\ndrwxr-x---. 3 postgres postgres 69 Feb 14 10:07 20180214-095439F_20180214-100446I
\ndrwxr-x---. 3 postgres postgres 69 Feb 14 11:13 20180214-105603F
\ndrwxr-x---. 3 postgres postgres 17 Feb 13 14:33 backup.history
\n-rw-r-----. 1 postgres postgres 2320 Feb 14 11:19 backup.info
\n-rw-r-----. 1 postgres postgres 2320 Feb 14 11:20 backup.info.copy
\nlrwxrwxrwx. 1 postgres postgres 16 Feb 14 11:14 latest -> 20180214-105603F
\n[postgres@pgserver clustpgserver]$
\n<\/code><\/p>\n

Point-in-Time Recovery<\/u>
\nPgBackRest can also do a point-in-time recovery. Let\u2019s drop table article in the database test
\n
\ntest=# table article;
\nnom
\n---------
\nprinter
\n(1 row)
\n.
\ntest=# select now();
\nnow
\n-------------------------------
\n2018-02-14 11:39:28.024378+01
\n(1 row)
\n.
\ntest=# drop table article;
\nDROP TABLE
\n.
\ntest=# table article;
\nERROR: relation \"article\" does not exist
\nLINE 1: table article;
\n^
\ntest=#
\n<\/code>
\nAnd now let\u2019s restore until just before we drop the table let\u2019s say 2018-02-14 11:39:28.
\nBut as we have many backup sets we have to restore from a backup done before the table was dropped.
\nIf we check our backups, we have to restore from the full backup: 20180214-105603F
\nwhich was taken before table article was dropped.
\n
\n[postgres@pgserver devdata]$ pgbackrest --stanza=clustpgserver --log-level-console=info info
\nstanza: clustpgserver
\nstatus: ok
\ndb (current)
\nwal archive min\/max (10-1): 000000020000000000000054 \/ 00000002000000000000005A
\nfull backup: 20180214-095439F
\ntimestamp start\/stop: 2018-02-14 09:54:39 \/ 2018-02-14 09:58:53
\nwal start\/stop: 000000020000000000000054 \/ 000000020000000000000054
\ndatabase size: 30.7MB, backup size: 30.7MB
\nrepository size: 3.6MB, repository backup size: 3.6MB
\nincr backup: 20180214-095439F_20180214-100446I
\ntimestamp start\/stop: 2018-02-14 10:04:46 \/ 2018-02-14 10:07:43
\nwal start\/stop: 000000020000000000000056 \/ 000000020000000000000056
\ndatabase size: 38.3MB, backup size: 7.6MB
\nrepository size: 4.5MB, repository backup size: 928.5KB
\nbackup reference list: 20180214-095439F
\n full backup: 20180214-105603F
\ntimestamp start\/stop: 2018-02-14 10:56:03 \/ 2018-02-14 11:12:26<\/strong>
\nwal start\/stop: 000000020000000000000058 \/ 000000020000000000000058
\ndatabase size: 38.3MB, backup size: 38.3MB
\nrepository size: 4.5MB, repository backup size: 4.5MB
\nincr backup: 20180214-105603F_20180214-121044I
\ntimestamp start\/stop: 2018-02-14 12:10:44 \/ 2018-02-14 12:15:14
\nwal start\/stop: 00000002000000000000005A \/ 00000002000000000000005A
\ndatabase size: 38.3MB, backup size: 1.1MB
\nrepository size: 4.5MB, repository backup size: 140.8KB
\nbackup reference list: 20180214-105603F
\n[postgres@pgserver devdata]$
\n<\/code>
\nFor the restore we use the option –set which allows us to specify the backup set we want to use for the restore. Note also the use of –type=time and –target
\n
\n[postgres@pgserver log]$ pgbackrest --stanza=clustpgserver --log-level-console=info --type=time \"--target=2018-02-14 11:39:28.024378+01\" --db-path=\/u01\/devdata --set=20180214-105603F restore
\n2018-02-14 13:36:50.848 P00 INFO: restore command begin 1.28: --db1-path=\/u01\/devdata --log-level-console=info --repo-cipher-pass= --repo-cipher-type=aes-256-cbc --repo-path=\/var\/lib\/pgbackrest --set=20180214-105603F --stanza=clustpgserver \"--target=2018-02-14 11:39:28.024378+01\" --type=time
\n2018-02-14 13:37:03.406 P00 INFO: restore backup set 20180214-105603F
\n...
\n<\/code>
\nAt the end of the restore let\u2019s see the contents of the recovery.done file
\n
\n[postgres@pgserver devdata]$ cat recovery.conf
\nrestore_command = '\/usr\/bin\/pgbackrest --db1-path=\/u01\/devdata --log-level-console=info --stanza=clustpgserver archive-get %f \"%p\"'
\nrecovery_target_time = '2018-02-14 11:39
\n<\/code>
\nIf we start our new cluster, we can see in log files that PITR is starting
\n2018-02-14 13:54:23.824 CET [10049] LOG: starting point-in-time recovery to 2018-02-14 11:39:28.024378+01<\/code>
\nAnd once the recovery finished, we can verify that the table article is present
\n
\npostgres=# c test
\nYou are now connected to database \"test\" as user \"postgres\".
\ntest=# d article
\nTable \"public.article\"
\nColumn | Type | Collation | Nullable | Default
\n--------+-----------------------+-----------+----------+---------
\nnom | character varying(50) | | |
\n.
\ntest=# table article;
\nnom
\n---------
\nprinter
\n(1 row)
\ntest=#
\n<\/code>
\nConclusion: <\/strong>
\nIn this blog I talked about some features about PgBackRest. But as already specified, there are many, many other options with this wonderful tool. The official documentation can give more information. In future blogs we will explore more with advanced configuration.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw In a precedent blog I shown a basic utilization of PgBackRest which is a tool to backup and restore PostgreSQL databases. In this blog I am going to talk some useful features of this tool. In practical examples we will see some tasks we can do with this tool. Of course the […]<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[229],"tags":[1293,77],"type_dbi":[],"class_list":["post-10834","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-pgbackrest","tag-postgresql"],"acf":[],"yoast_head":"\nBackup and Restore PostgreSQL with PgBackRest II - dbi Blog<\/title>\n<meta name=\"description\" content=\"PostgreSQL, Backup and restore, PgBackRest\" \/>\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\/backup-and-restore-postgresql-with-pgbackrest-ii\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Backup and Restore PostgreSQL with PgBackRest II\" \/>\n<meta property=\"og:description\" content=\"PostgreSQL, Backup and restore, PgBackRest\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-02-15T14:41:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-09T14:53:48+00:00\" \/>\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\/backup-and-restore-postgresql-with-pgbackrest-ii\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Backup and Restore PostgreSQL with PgBackRest II\",\"datePublished\":\"2018-02-15T14:41:26+00:00\",\"dateModified\":\"2023-06-09T14:53:48+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/\"},\"wordCount\":865,\"commentCount\":0,\"keywords\":[\"pgbackrest\",\"PostgreSQL\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/\",\"name\":\"Backup and Restore PostgreSQL with PgBackRest II - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2018-02-15T14:41:26+00:00\",\"dateModified\":\"2023-06-09T14:53:48+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"PostgreSQL, Backup and restore, PgBackRest\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Backup and Restore PostgreSQL with PgBackRest II\"}]},{\"@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":"Backup and Restore PostgreSQL with PgBackRest II - dbi Blog","description":"PostgreSQL, Backup and restore, PgBackRest","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\/backup-and-restore-postgresql-with-pgbackrest-ii\/","og_locale":"en_US","og_type":"article","og_title":"Backup and Restore PostgreSQL with PgBackRest II","og_description":"PostgreSQL, Backup and restore, PgBackRest","og_url":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/","og_site_name":"dbi Blog","article_published_time":"2018-02-15T14:41:26+00:00","article_modified_time":"2023-06-09T14:53:48+00:00","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\/backup-and-restore-postgresql-with-pgbackrest-ii\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Backup and Restore PostgreSQL with PgBackRest II","datePublished":"2018-02-15T14:41:26+00:00","dateModified":"2023-06-09T14:53:48+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/"},"wordCount":865,"commentCount":0,"keywords":["pgbackrest","PostgreSQL"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/","url":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/","name":"Backup and Restore PostgreSQL with PgBackRest II - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-02-15T14:41:26+00:00","dateModified":"2023-06-09T14:53:48+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"PostgreSQL, Backup and restore, PgBackRest","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-ii\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Backup and Restore PostgreSQL with PgBackRest II"}]},{"@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\/10834","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=10834"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10834\/revisions"}],"predecessor-version":[{"id":25763,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10834\/revisions\/25763"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=10834"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=10834"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=10834"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=10834"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}