{"id":9523,"date":"2016-12-08T20:21:09","date_gmt":"2016-12-08T19:21:09","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/"},"modified":"2023-06-08T16:15:20","modified_gmt":"2023-06-08T14:15:20","slug":"enterprisedb-backup-and-recovery-tool-bart","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/","title":{"rendered":"EnterpriseDB Backup and Recovery Tool (BART)"},"content":{"rendered":"

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

Many tools are proposed for backup and recovery operation of a PostgreSQL database. EnterpriseDB has developed a product named BART (Backup and Recovery Tool). Use of this product needs a subscription but you can download a trial version for test purpose.
\nIn this blog we are using BART with PostgreSQL 9.6.1. BART allows backing up over the net and can centralize backups of many PostgreSQL servers.
\nWe are using the following configuration:
\nBart Host<\/b>: pgserver.localdomain
\nPostgreSQL server 1<\/b>: pgserve1.localdomain
\nPostgreSQL server 2<\/b>: pgserve2.localdomain
\nWe suppose that there are clusters running on pgserver1 and pgserver2 and the archive mode is activated for both clusters
\nWhat is needed on the server hosting BART (i.e. pgserver in our case)?
\n1. We need to install rpm package using yum or rpm command
\n2. We need PostgreSQL binaries installed. Note that the version of the binaries should be at least the same than those installed on the servers to be backed up. In our case as we are using 9.6.1 for databases, binaries should be 9.6.1 or higher. Note that we don\u2019t need any cluster running on pgserver.
\nFor the package installation, we are using yum.
\n
\n[root@pgserver 96]# yum localinstall edb-bart-1.1.0-1.rhel7.x86_64.rpm
\n<\/code>
\nBy default BART is installed in \/usr\/edb-bart-1.1.
\n
\n[root@pgserver 96]# cd \/usr\/edb-bart-1.1\/
\n[root@pgserver edb-bart-1.1]# ls
\nbart_license.txt bin etc
\n[root@pgserver edb-bart-1.1]# ls -l
\ntotal 16
\n-rw-r--r--. 1 root root 15272 Jul 3 2015 bart_license.txt
\ndrwxr-xr-x. 2 root root 17 Dec 6 14:15 bin
\ndrwxr-xr-x. 2 root root 21 Dec 6 14:15 etc
\n[root@pgserver edb-bart-1.1]#
\n<\/code>
\nBefore configuring the BART configuration file, the ssh connectivity should be configured between servers for the Linux user used for backups, here we are using postgres.
\n
\n[postgres@pgserver ~]$ ssh-keygen -t rsa
\nGenerating public\/private rsa key pair.
\nEnter file in which to save the key (\/home\/postgres\/.ssh\/id_rsa):
\nEnter passphrase (empty for no passphrase):
\nEnter same passphrase again:
\nYour identification has been saved in \/home\/postgres\/.ssh\/id_rsa.
\nYour public key has been saved in \/home\/postgres\/.ssh\/id_rsa.pub.
\nThe key fingerprint is:
\nb9:fb:1a:90:c2:76:73:6e:fe:28:38:cf:42:52:7a:81 postgres@pgserver.localdomain
\nThe key's randomart image is:
\n+--[ RSA 2048]----+
\n| |
\n| |
\n| . |
\n| E.o . . |
\n| o+.= S |
\n| o.oo = . |
\n| + . = |
\n| +..o + |
\n| +o.=+o |
\n+-----------------+
\n[postgres@pgserver ~]$ ssh-copy-id -i .ssh\/id_rsa.pub pgserver1
\n\/usr\/bin\/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
\n\/usr\/bin\/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
\npostgres@pgserver1's password:
\nNumber of key(s) added: 1
\nNow try logging into the machine, with: \"ssh 'pgserver1'\"
\nand check to make sure that only the key(s) you wanted were added.
\n[postgres@pgserver ~]$ ssh-copy-id -i .ssh\/id_rsa.pub pgserver2
\n\/usr\/bin\/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
\n\/usr\/bin\/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
\npostgres@pgserver2's password:
\nNumber of key(s) added: 1
\nNow try logging into the machine, with: \"ssh 'pgserver2'\"
\nand check to make sure that only the key(s) you wanted were added.
\n[postgres@pgserver ~]$
\n<\/code>
\n
\n[postgres@pgserver ~]$ ssh pgserver1 date
\nTue Dec 6 14:24:35 CET 2016
\n[postgres@pgserver ~]$ ssh pgserver2 date
\nTue Dec 6 14:24:40 CET 2016
\n[postgres@pgserver ~]$
\n<\/code>
\nWe also need a super user created on each cluster to be backed up
\n
\npostgres=# CREATE ROLE backupuser WITH LOGIN SUPERUSER PASSWORD 'root';
\nCREATE ROLE
\npostgres=#
\n<\/code>
\nAnd we will create a .pgpass for this user to be able to connect without being asked for password
\n
\n[postgres@pgserver1 ~]$ echo \"*:5432:*:backupuser:root\" >> ~\/.pgpass
\n[postgres@pgserver1 ~]$ chmod 600 .pgpass<\/code><\/p>\n


\n<\/code><\/p>\n

[postgres@pgserver2 ~]$ echo \"*:5432:*:backupuser:root\" >> ~\/.pgpass
\n[postgres@pgserver2 ~]$ chmod 600 .pgpass
\n<\/code>
\nThe configuration file is located under $BART_INSTALL_DIRECTORY\/etc. It must contain a part for BART itself and a part for each server to be backed up. Below an example of our bart.cfg
\n
\n[root@pgserver etc]# pwd
\n\/usr\/edb-bart-1.1\/etc
\n<\/code>
\n
\n[root@pgserver etc]# cat bart.cfg | grep -v ^#
\n[BART]
\nbart-host= postgres@192.168.56.35
\nbackup_path = \/u01\/app\/backup
\npg_basebackup_path = \/u01\/app\/PostgreSQL\/9.6\/bin\/pg_basebackup
\nlogfile = \/tmp\/bart.log
\nxlog-method = fetch
\nretention_policy = 1 DAYS
\nwal_compression = enabled<\/code><\/p>\n

<\/code><\/code><\/p>\n

[PGSERVER1]
\nhost = 192.168.56.36
\nport = 5432
\nuser = backupuser
\nbackup-name = PGSERVER1_%year-%month-%dayT%hour:%minute
\nremote-host = postgres@pgserver1
\ndescription = “Postgres server1”<\/p>\n


\n<\/code><\/p>\n

[PGSERSERVER2]
\nhost = 192.168.56.37
\nport = 5432
\nuser = backupuser
\nbackup-name = PGSERVER2_%year-%month-%dayT%hour:%minute
\nremote-host = postgres@pgserver2
\ndescription = \"Postgres server2\"
\n[root@pgserver etc]#
\n<\/code>
\nThe backup_path \/u01\/app\/backup is only needed on the BART host (pgserver) as backup will be done over the net. But on both servers pgserver1 and pgserver2 the pg_hba.conf<\/span> need to be updated to allow connection from the BART host. Below two lines we add
\n
\n[postgres@pgserver1 data]$ grep 192.168.56.0 pg_hba.conf
\nhost all all 192.168.56.0\/24 md5
\nhost replication backupuser 192.168.56.0\/24 md5
\n[postgres@pgserver1 data]$
\n<\/code>
\n
\n[postgres@pgserver2 data]$ grep 192.168.56.0 pg_hba.conf
\nhost all all 192.168.56.0\/24 md5
\nhost replication backupuser 192.168.56.0\/24 md5
\n[postgres@pgserver2 data]$
\n<\/code>
\nNow we can initialize the catalog, first for pgserver1 and after for pgserver2 (note this can be done for both servers in a single command)
\n
\n[postgres@pgserver bin]$ .\/bart -d -c \/usr\/edb-bart-1.1\/etc\/bart.cfg init -s PGSERVER1 -o
\nDEBUG: Server: Global, Now: 2016-12-06 15:51:04 CET, RetentionWindow: 86400 (secs) ==> 24 hour(s)
\nINFO: setting archive_command for server 'pgserver1'
\nDEBUG: SHOW archive_command: test ! -f \/u01\/app\/archive\/%f && cp %p \/u01\/app\/archive\/%f
\nDEBUG: archive command set to: ALTER SYSTEM SET archive_command TO 'scp %p postgres@192.168.56.35:\/u01\/app\/backup\/pgserver1\/archived_wals\/%f'
\nWARNING: archive_command is set. server restart is required
\n[postgres@pgserver bin]$
\n<\/code>
\n
\n[postgres@pgserver bin]$ .\/bart -d -c \/usr\/edb-bart-1.1\/etc\/bart.cfg init -s PGSERVER2 -o
\nDEBUG: Server: Global, Now: 2016-12-06 19:01:08 CET, RetentionWindow: 86400 (secs) ==> 24 hour(s)
\nINFO: setting archive_command for server 'pgserver2'
\nDEBUG: SHOW archive_command: test ! -f \/u01\/app\/archive\/%f && cp %p \/u01\/app\/archive\/%f
\nDEBUG: archive command set to: ALTER SYSTEM SET archive_command TO 'scp %p postgres@192.168.56.35:\/u01\/app\/backup\/pgserver2\/archived_wals\/%f'
\nWARNING: archive_command is set. server restart is required
\n[postgres@pgserver bin]$
\n<\/code>
\nNow it\u2019s time to launch a backup
\n
\n[postgres@pgserver bin]$ .\/bart -c \/usr\/edb-bart-1.1\/etc\/bart.cfg BACKUP -s PGSERVER1<\/code><\/p>\n

<\/code><\/code><\/p>\n

INFO: creating backup for server ‘pgserver1’
\nINFO: backup identifier: ‘1481037296469’
\n39433\/39433 kB (100%), 1\/1 tablespace<\/p>\n

<\/code><\/code><\/p>\n

INFO: backup completed successfully
\nINFO: backup checksum: fb105a542d8856e9d5bd95410337463f of base.tar
\nINFO:
\nBACKUP DETAILS:
\nBACKUP STATUS: active
\nBACKUP IDENTIFIER: 1481037296469
\nBACKUP NAME: PGSERVER1_2016-12-06T16:14
\nBACKUP LOCATION: \/u01\/app\/backup\/pgserver1\/1481037296469
\nBACKUP SIZE: 38.51 MB
\nBACKUP FORMAT: tar
\nXLOG METHOD: fetch
\nBACKUP CHECKSUM(s): 1
\nChkSum File
\nfb105a542d8856e9d5bd95410337463f base.tar<\/p>\n

<\/code><\/code><\/p>\n

TABLESPACE(s): 0
\nSTART WAL LOCATION: 000000010000000000000008
\nBACKUP METHOD: streamed
\nBACKUP FROM: master
\nSTART TIME: 2016-12-06 16:14:56 CET
\nSTOP TIME: 2016-12-06 16:14:58 CET
\nTOTAL DURATION: 2 sec(s)<\/p>\n


\n<\/code><\/p>\n

[postgres@pgserver bin]$
\n<\/code>
\n
\npostgres@pgserver bin]$ .\/bart -c \/usr\/edb-bart-1.1\/etc\/bart.cfg BACKUP -s PGSERVER2<\/code><\/p>\n

<\/code><\/code><\/p>\n

INFO: creating backup for server ‘pgserver2’
\nINFO: backup identifier: ‘1481047475191’
\n39216\/39216 kB (100%), 1\/1 tablespace<\/p>\n

<\/code><\/code><\/p>\n

INFO: backup completed successfully
\nINFO: backup checksum: 052d82f3df1def72e9962cdef965fe8f of base.tar
\nINFO:
\nBACKUP DETAILS:
\nBACKUP STATUS: active
\nBACKUP IDENTIFIER: 1481047475191
\nBACKUP NAME: PGSERVER2_2016-12-06T19:04
\nBACKUP LOCATION: \/u01\/app\/backup\/pgserver2\/1481047475191
\nBACKUP SIZE: 38.30 MB
\nBACKUP FORMAT: tar
\nXLOG METHOD: fetch
\nBACKUP CHECKSUM(s): 1
\nChkSum File
\n052d82f3df1def72e9962cdef965fe8f base.tar<\/p>\n

<\/code><\/code><\/p>\n

TABLESPACE(s): 0
\nSTART WAL LOCATION: 000000010000000000000003
\nBACKUP METHOD: streamed
\nBACKUP FROM: master
\nSTART TIME: 2016-12-06 19:04:36 CET
\nSTOP TIME: 2016-12-06 19:04:38 CET
\nTOTAL DURATION: 2 sec(s)<\/p>\n


\n<\/code><\/p>\n

[postgres@pgserver bin]$
\n<\/code>
\nWe can list backups for pgserver2 for example
\n
\n[postgres@pgserver bin]$ .\/bart SHOW-BACKUPS -s pgserver2
\nSERVER NAME BACKUP ID BACKUP TIME BACKUP SIZE WAL(s) SIZE WAL FILES STATUS<\/code><\/p>\n

<\/code><\/code><\/p>\n

pgserver2 1481047475191 2016-12-06 19:04:38 CET 38.30 MB 26.54 kB 1 active<\/p>\n


\n<\/code><\/p>\n

[postgres@pgserver bin]$
\n<\/code><\/p>\n

It\u2019s good to have a backup, but it is better to know how to restore. And now we are going to simulate a crash of pgserver2 and then do a restore. First let\u2019s create a database and a table.
\n
\n[postgres@pgserver2 data]$ psql
\nPassword:
\npsql.bin (9.6.1)
\nType \"help\" for help.
\npostgres=# create database sales;
\nCREATE DATABASE
\npostgres=# c sales
\nYou are now connected to database \"sales\" as user \"postgres\".
\nsales=# create table article(id int);
\nCREATE TABLE
\nsales=# insert into article values (1);
\nINSERT 0 1
\nsales=# table article;
\nid
\n----
\n1
\n(1 row)
\nsales=#
\n<\/code>
\nAnd then let\u2019s do a backup
\n
\n[postgres@pgserver bin]$ .\/bart -c \/usr\/edb-bart-1.1\/etc\/bart.cfg BACKUP -s PGSERVER2
\nINFO: creating backup for server 'pgserver2'
\nINFO: backup identifier: '1481051725125'
\n46814\/46814 kB (100%), 1\/1 tablespace
\nINFO: backup completed successfully
\nINFO: backup checksum: 19069965fa53444b31459f6d984682d0 of base.tar
\nINFO:
\nBACKUP DETAILS:
\nBACKUP STATUS: active
\nBACKUP IDENTIFIER: 1481051725125
\nBACKUP NAME: PGSERVER2_2016-12-06T20:15
\nBACKUP LOCATION: \/u01\/app\/backup\/pgserver2\/1481051725125
\nBACKUP SIZE: 45.72 MB
\nBACKUP FORMAT: tar
\nXLOG METHOD: fetch
\nBACKUP CHECKSUM(s): 1
\nChkSum File
\n19069965fa53444b31459f6d984682d0 base.tar
\nTABLESPACE(s): 0
\nSTART WAL LOCATION: 000000010000000000000005
\nBACKUP METHOD: streamed
\nBACKUP FROM: master
\nSTART TIME: 2016-12-06 20:15:28 CET
\nSTOP TIME: 2016-12-06 20:15:28 CET
\nTOTAL DURATION: 0 sec(s)
\n<\/code>
\n
\n[postgres@pgserver bin]$ .\/bart SHOW-BACKUPS -s PGSERVER2
\nSERVER NAME BACKUP ID BACKUP TIME BACKUP SIZE WAL(s) SIZE WAL FILES STATUS
\npgserver2 1481051725125 2016-12-06 20:15:28 CET 45.72 MB 16.00 MB 1 active
\npgserver2 1481047475191 2016-12-06 19:04:38 CET 38.30 MB 16.03 MB 2 active
\n[postgres@pgserver bin]$
\n<\/code>
\nNow let\u2019s crash our cluster
\n
\n[root@pgserver2 9.6]# pwd
\n\/u01\/app\/PostgreSQL\/9.6
\n[root@pgserver2 9.6]# mv data\/ data_crash
\n[root@pgserver2 9.6]#
\n<\/code>
\n
\n[postgres@pgserver2 9.6]$ pg_ctl start
\npg_ctl: directory \"\/u01\/app\/PostgreSQL\/9.6\/data\" does not exist
\n[postgres@pgserver2 9.6]$
\n<\/code>
\nFor the restore, we have to provide the backup id and the path to restore. This path must exist.
\n
\n[postgres@pgserver bin]$ .\/bart RESTORE -s pgserver2 -i 1481047475191 -p \/u01\/app\/PostgreSQL\/9.6\/data
\nINFO: restoring backup '1481047475191' of server 'pgserver2'
\nINFO: restoring backup to postgres@pgserver2:\/u01\/app\/PostgreSQL\/9.6\/data
\nINFO: base backup restored
\nINFO: copying WAL file(s) to postgres@pgserver2:\/u01\/app\/PostgreSQL\/9.6\/data\/archived_wals
\nINFO: archiving is disabled
\n[postgres@pgserver bin]$
\n<\/code>
\nBefore starting cluster, let\u2019s create a recovery.conf file
\n
\n[postgres@pgserver2 data]$ cat recovery.conf
\nrestore_command='cp \/u01\/app\/PostgreSQL\/9.6\/data\/archived_wals\/%f %p'
\n[postgres@pgserver2 data]$
\n<\/code>
\nAnd then let\u2019s start the cluster
\n
\n[postgres@pgserver2 data]$ pg_ctl start
\nserver starting
\n[postgres@pgserver2 data]$ 2016-12-06 20:33:01 CET LOG: redirecting log output to logging collector process
\n2016-12-06 20:33:01 CET HINT: Future log output will appear in directory \"pg_log\".
\n<\/code>
\nAfter the restore finished, the recovery.conf is automatically renamed to recovery.done because PostgreSQL will go into recovery mode again after a restart otherwise.
\n
\n[postgres@pgserver2 data]$ cat recovery.done
\nrestore_command='cp \/u01\/app\/PostgreSQL\/9.6\/data\/archived_wals\/%f %p'
\n[postgres@pgserver2 data]$
\n<\/code>
\nWhile connecting we can verify our data
\n
\n[postgres@pgserver2 data]$ psql
\nPassword:
\npsql.bin (9.6.1)
\nType \"help\" for help.
\npostgres=# c sales
\nYou are now connected to database \"sales\" as user \"postgres\".
\nsales=# table article
\nsales-# ;
\nid
\n----
\n1
\n(1 row)
\nsales=#
\n<\/code>
\nIn this blog we have seen how to configure EDB BART, how to use it for backup and recovery.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Many tools are proposed for backup and recovery operation of a PostgreSQL database. EnterpriseDB has developed a product named BART (Backup and Recovery Tool). Use of this product needs a subscription but you can download a trial version for test purpose. In this blog we are using BART with PostgreSQL 9.6.1. BART […]<\/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":[1003,1004,713,1002],"type_dbi":[],"class_list":["post-9523","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-bart","tag-edb","tag-enterprisedb","tag-postgresql-9-6"],"acf":[],"yoast_head":"\nEnterpriseDB Backup and Recovery Tool (BART) - dbi Blog<\/title>\n<meta name=\"description\" content=\"PostgresSQL,Backup and recovery Tool, BART\" \/>\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\/enterprisedb-backup-and-recovery-tool-bart\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"EnterpriseDB Backup and Recovery Tool (BART)\" \/>\n<meta property=\"og:description\" content=\"PostgresSQL,Backup and recovery Tool, BART\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2016-12-08T19:21:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-08T14:15:20+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=\"8 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\/enterprisedb-backup-and-recovery-tool-bart\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"EnterpriseDB Backup and Recovery Tool (BART)\",\"datePublished\":\"2016-12-08T19:21:09+00:00\",\"dateModified\":\"2023-06-08T14:15:20+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/\"},\"wordCount\":750,\"commentCount\":0,\"keywords\":[\"Bart\",\"edb\",\"enterprisedb\",\"PostgreSQL 9.6\"],\"articleSection\":[\"Database Administration & Monitoring\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/\",\"name\":\"EnterpriseDB Backup and Recovery Tool (BART) - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2016-12-08T19:21:09+00:00\",\"dateModified\":\"2023-06-08T14:15:20+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"PostgresSQL,Backup and recovery Tool, BART\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"EnterpriseDB Backup and Recovery Tool (BART)\"}]},{\"@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":"EnterpriseDB Backup and Recovery Tool (BART) - dbi Blog","description":"PostgresSQL,Backup and recovery Tool, BART","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\/enterprisedb-backup-and-recovery-tool-bart\/","og_locale":"en_US","og_type":"article","og_title":"EnterpriseDB Backup and Recovery Tool (BART)","og_description":"PostgresSQL,Backup and recovery Tool, BART","og_url":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/","og_site_name":"dbi Blog","article_published_time":"2016-12-08T19:21:09+00:00","article_modified_time":"2023-06-08T14:15:20+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"EnterpriseDB Backup and Recovery Tool (BART)","datePublished":"2016-12-08T19:21:09+00:00","dateModified":"2023-06-08T14:15:20+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/"},"wordCount":750,"commentCount":0,"keywords":["Bart","edb","enterprisedb","PostgreSQL 9.6"],"articleSection":["Database Administration & Monitoring"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/","url":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/","name":"EnterpriseDB Backup and Recovery Tool (BART) - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2016-12-08T19:21:09+00:00","dateModified":"2023-06-08T14:15:20+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"PostgresSQL,Backup and recovery Tool, BART","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/enterprisedb-backup-and-recovery-tool-bart\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"EnterpriseDB Backup and Recovery Tool (BART)"}]},{"@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\/9523","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=9523"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9523\/revisions"}],"predecessor-version":[{"id":25687,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/9523\/revisions\/25687"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=9523"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=9523"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=9523"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=9523"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}