{"id":10809,"date":"2018-02-14T15:58:57","date_gmt":"2018-02-14T14:58:57","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/"},"modified":"2023-06-09T16:53:18","modified_gmt":"2023-06-09T14:53:18","slug":"backup-and-restore-postgresql-with-pgbackrest-i","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/","title":{"rendered":"Backup and Restore PostgreSQL with PgBackRest I"},"content":{"rendered":"

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

Many tools can be used to backup PostgreSQL databases. In this blog I will talk about PgBackRest<\/a> which is a simple tool that can be used to backup and restore a PostgreSQL database. Full, differential, and incremental backups are supported.
\nIn this first blog I will present a basic configuration of pgbackprest. Our configuration is composed of only one cluster and pgbackrest is installed on the server hosting the database. The goal is to explain a first use of PgBackRest.
\nBelow our configuration
\nServer with Oracle Linux 7
\nPostgreSQL 10.1
\nPgBackRest 1.28
\nWe supposed that the linux box and PostgreSQL 10.1 are already installed. So let\u2019s install PgBackRest.
\n
\nroot@pgserver ~]# yum search pgbackrest
\nLoaded plugins: langpacks, ulninfo
\n=========================== N\/S matched: pgbackrest ============================
\npgbackrest.noarch : Reliable PostgreSQL Backup & Restore
\npgbackrest.x86_64 : Reliable PostgreSQL Backup & Restore
\nName and summary matches only, use \"search all\" for everything
\n<\/code>
\nAnd then we can install PgBackRest
\n[root@pgserver ~]# yum install pgbackrest.x86_64<\/code>
\nAfter we can check the installation using pgbackrest command
\n
\n[postgres@pgserver ~]$ \/usr\/bin\/pgbackrest
\npgBackRest 1.28 - General help
\nUsage:
\npgbackrest [options] [command]
\nCommands:
\narchive-get Get a WAL segment from the archive.
\narchive-push Push a WAL segment to the archive.
\nbackup Backup a database cluster.
\ncheck Check the configuration.
\nexpire Expire backups that exceed retention.
\nhelp Get help.
\ninfo Retrieve information about backups.
\nrestore Restore a database cluster.
\nstanza-create Create the required stanza data.
\nstanza-delete Delete a stanza.
\nstanza-upgrade Upgrade a stanza.
\nstart Allow pgBackRest processes to run.
\nstop Stop pgBackRest processes from running.
\nversion Get version.
\nUse 'pgbackrest help [command]' for more information.
\n<\/code>
\nThe configuration of PgBackRest is very easy, it consists of a configuration pgbackrest.conf<\/strong> file that must be edited. In my case the file is located in \/etc. As specified, we will use a very basic configuration file.
\nBelow the contents of my configuration file
\n
\n[root@pgserver etc]# cat pgbackrest.conf
\n[global]
\nrepo-path=\/var\/lib\/pgbackrest
\n[clustpgserver]
\ndb-path=\/var\/lib\/pgsql\/10\/data
\nretention-full=2
\n[root@pgserver etc]#
\n<\/code>
\nIn the file above,
\n\u2022 repo-path is where backup will be stored,
\n\u2022 clusterpgserver is the name of my cluster stanza (free to take what you want as name). A stanza is the configuration for a PostgreSQL database cluster that defines where it is located, how it will be backed up, archiving options, etc.
\n\u2022 db-path is the path of my database files
\n\u2022 retention-full : configure retention to 2 full backups
\nA complete list can be found here<\/a>
\nOnce the configuration file done, we can now create the stanza with the command create-stanza. Note that my PostgreSQL cluster is using the port 5435.
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 stanza-create
\n2018-02-08 14:01:49.293 P00 INFO: stanza-create command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --stanza=clustpgserver
\n2018-02-08 14:01:50.707 P00 INFO: stanza-create command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nAfter we create the stanza, we can verify that the configuration is fine using the check command
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 check
\n2018-02-08 14:03:42.095 P00 INFO: check command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --stanza=clustpgserver
\n2018-02-08 14:03:48.805 P00 INFO: WAL segment 00000001000000000000000C successfully stored in the archive at '\/var\/lib\/pgbackrest\/archive\/clustpgserver\/10-1\/0000000100000000\/00000001000000000000000C-c387b901a257bac304f27865478fd9f768de83d6.gz'
\n2018-02-08 14:03:48.808 P00 INFO: check command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nSince we did not take yet any backup with PgBackRest, the command info for the backups returns error
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info info
\nstanza: clustpgserver
\nstatus: error (no valid backups)
\ndb (current)
\nwal archive min\/max (10-1): 00000001000000000000000C \/ 00000001000000000000000C
\n[postgres@pgserver ~]$
\n<\/code>
\nNow let\u2019s take a backup
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 backup
\n2018-02-08 14:06:52.706 P00 INFO: backup command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --retention-full=2 --stanza=clustpgserver
\nWARN: no prior backup exists, incr backup has been changed to full<\/strong>
\n2018-02-08 14:06:54.734 P00 INFO: execute non-exclusive pg_start_backup() with label \"pgBackRest backup started at 2018-02-08 14:06:53\": backup begins after the next regular checkpoint completes
\n2018-02-08 14:06:55.159 P00 INFO: backup start archive = 00000001000000000000000E, lsn = 0\/E000060
\n2018-02-08 14:07:09.867 P01 INFO: backup file \/var\/lib\/pgsql\/10\/data\/base\/13805\/1255 (592KB, 2%) checksum 61f284092cabf44a30d1442ef6dd075b2e346b7f
\n\u2026
\n\u2026
\n2018-02-08 14:08:34.709 P00 INFO: expire command begin 1.28: --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --retention-archive=2 --retention-full=2 --stanza=clustpgserver
\n2018-02-08 14:08:34.895 P00 INFO: full backup total < 2 - using oldest full backup for 10-1 archive retention
\n2018-02-08 14:08:34.932 P00 INFO: expire command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nWe can see that by default PgBackRest will try to do an incremental backup. But as there is no full backup yet, a full backup will be done. Once full backup done, all future backups will be incremental unless we specify the type of backup.
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 backup
\n2018-02-08 14:26:25.590 P00 INFO: backup command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --retention-full=2 --stanza=clustpgserver
\n2018-02-08 14:26:29.314 P00 INFO: last backup label = 20180208-140653F, version = 1.28
\n2018-02-08 14:26:30.135 P00 INFO: execute non-exclusive pg_start_backup() with label \"pgBackRest backup started at 2018-02-08 14:26:26\": backup begins after the next regular checkpoint completes
\n...
\n2018-02-08 14:27:01.408 P00 INFO: expire command begin 1.28: --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --retention-archive=2 --retention-full=2 --stanza=clustpgserver
\n2018-02-08 14:27:01.558 P00 INFO: full backup total < 2 - using oldest full backup for 10-1 archive retention
\n2018-02-08 14:27:01.589 P00 INFO: expire command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nIf we want to perform another full backup we can specify the option –type=full
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info --db-port=5435 --type=full backup
\n2018-02-08 14:30:05.961 P00 INFO: backup command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --db1-port=5435 --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --retention-full=2 --stanza=clustpgserver --type=full
\n2018-02-08 14:30:08.472 P00 INFO: execute non-exclusive pg_start_backup() with label \"pgBackRest backup started at 2018-02-08 14:30:06\": backup begins after the next regular checkpoint completes
\n2018-02-08 14:30:08.993 P00 INFO: backup start archive = 000000010000000000000012, lsn = 0\/12000028
\n\u2026.
\n\u2026.
\n<\/code>
\nTo have info about our backups
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver info
\nstanza: clustpgserver
\nstatus: ok
\ndb (current)
\nwal archive min\/max (10-1): 00000001000000000000000E \/ 000000010000000000000012
\nfull backup: 20180208-140653F
\ntimestamp start\/stop: 2018-02-08 14:06:53 \/ 2018-02-08 14:08:19
\nwal start\/stop: 00000001000000000000000E \/ 00000001000000000000000E
\ndatabase size: 23.2MB, backup size: 23.2MB
\nrepository size: 2.7MB, repository backup size: 2.7MB
\nincr backup: 20180208-140653F_20180208-142626I
\ntimestamp start\/stop: 2018-02-08 14:26:26 \/ 2018-02-08 14:26:52
\nwal start\/stop: 000000010000000000000010 \/ 000000010000000000000010
\ndatabase size: 23.2MB, backup size: 8.2KB
\nrepository size: 2.7MB, repository backup size: 472B
\nbackup reference list: 20180208-140653F
\nfull backup: 20180208-143006F
\ntimestamp start\/stop: 2018-02-08 14:30:06 \/ 2018-02-08 14:31:30
\nwal start\/stop: 000000010000000000000012 \/ 000000010000000000000012
\ndatabase size: 23.2MB, backup size: 23.2MB
\nrepository size: 2.7MB, repository backup size: 2.7MB
\n[postgres@pgserver ~]$
\n<\/code>
\nNow that we see how to perform backup with pgbackrest, let\u2019s see how to restore.
\nFirst let identify the directory of our database files
\n
\n[postgres@pgserver ~]$ psql
\npsql (10.1)
\nType \"help\" for help.
\npostgres=# show data_directory ;
\ndata_directory
\n------------------------
\n\/var\/lib\/pgsql\/10\/data
\n(1 row)
\npostgres=#
\n<\/code>
\nAnd let\u2019s remove all files in the directory
\n
\n[postgres@pgserver data]$ pwd
\n\/var\/lib\/pgsql\/10\/data
\n[postgres@pgserver data]$ ls
\nbase pg_dynshmem pg_notify pg_stat_tmp pg_wal postmaster.pid
\ncurrent_logfiles pg_hba.conf pg_replslot pg_subtrans pg_xact
\nglobal pg_ident.conf pg_serial pg_tblspc postgresql.auto.conf
\nlog pg_logical pg_snapshots pg_twophase postgresql.conf
\npg_commit_ts pg_multixact pg_stat PG_VERSION postmaster.opts
\n[postgres@pgserver data]$ rm -rf *
\n[postgres@pgserver data]$
\n<\/code>
\nNow if we try to connect, of course we will get errors
\n
\n[postgres@pgserver data]$ psql
\npsql: could not connect to server: No such file or directory
\nIs the server running locally and accepting
\nconnections on Unix domain socket \"\/var\/run\/postgresql\/.s.PGSQL.5435\"?
\n[postgres@pgserver data]$
\n<\/code>
\nSo let\u2019s restore with PgBackRest with the restore command
\n
\n[postgres@pgserver ~]$ pgbackrest --stanza=clustpgserver --log-level-console=info restore
\n2018-02-08 14:52:01.845 P00 INFO: restore command begin 1.28: --db1-path=\/var\/lib\/pgsql\/10\/data --log-level-console=info --repo-path=\/var\/lib\/pgbackrest --stanza=clustpgserver
\n2018-02-08 14:52:03.490 P00 INFO: restore backup set 20180208-143006F
\n2018-02-08 14:52:21.904 P01 INFO: restore file \/var\/lib\/pgsql\/10\/data\/base\/13805\/1255 (592KB, 2%) checksum 61f284092cabf44a30d1442ef6dd075b2e346b7f
\n\u2026.
\n\u2026.
\n2018-02-08 14:53:21.186 P00 INFO: write \/var\/lib\/pgsql\/10\/data\/recovery.conf
\n2018-02-08 14:53:23.948 P00 INFO: restore global\/pg_control (performed last to ensure aborted restores cannot be started)
\n2018-02-08 14:53:28.258 P00 INFO: restore command end: completed successfully
\n[postgres@pgserver ~]$
\n<\/code>
\nAt the end of the backup, a recovery.conf file is created in the data directory
\n
\n[postgres@pgserver data]$ cat recovery.conf
\nrestore_command = '\/usr\/bin\/pgbackrest --log-level-console=info --stanza=clustpgserver archive-get %f \"%p\"'
\n<\/code>
\nNow we can restart the PostgreSQL cluster
\n
\n[postgres@pgserver data]$ pg_ctl start
\nwaiting for server to start....2018-02-08 14:57:06.519 CET [4742] LOG: listening on IPv4 address \"0.0.0.0\", port 5435
\n2018-02-08 14:57:06.522 CET [4742] LOG: listening on IPv6 address \"::\", port 5435
\n2018-02-08 14:57:06.533 CET [4742] LOG: listening on Unix socket \"\/var\/run\/postgresql\/.s.PGSQL.5435\"
\n2018-02-08 14:57:06.551 CET [4742] LOG: listening on Unix socket \"\/tmp\/.s.PGSQL.5435\"
\n2018-02-08 14:57:06.645 CET [4742] LOG: redirecting log output to logging collector process
\n2018-02-08 14:57:06.645 CET [4742] HINT: Future log output will appear in directory \"log\".
\n...... done
\nserver started
\n<\/code>
\nAnd then connect
\n
\n[postgres@pgserver data]$ psql
\npsql (10.1)
\nType \"help\" for help.
\npostgres=#
\n<\/code>
\nConclusion <\/strong>
\nIn this blog we shown in a simple configuration how to perform backup using PgBackRest. This basic configuration can help for first use of PgBackRest. In future articles we will go further in an advanced use of this tool.<\/p>\n","protected":false},"excerpt":{"rendered":"

By Mouhamadou Diaw Many tools can be used to backup PostgreSQL databases. In this blog I will talk about PgBackRest which is a simple tool that can be used to backup and restore a PostgreSQL database. Full, differential, and incremental backups are supported. In this first blog I will present a basic configuration of pgbackprest. […]<\/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":[202,77,1108,854],"type_dbi":[],"class_list":["post-10809","post","type-post","status-publish","format-standard","hentry","category-database-administration-monitoring","tag-backup","tag-postgresql","tag-postgresql-10","tag-restore"],"acf":[],"yoast_head":"\nBackup and Restore PostgreSQL with PgBackRest I - dbi Blog<\/title>\n<meta name=\"description\" content=\"PostgreSQL 10.1, PgBackRest, Backup, Restore\" \/>\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-i\/\" \/>\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 I\" \/>\n<meta property=\"og:description\" content=\"PostgreSQL 10.1, PgBackRest, Backup, Restore\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2018-02-14T14:58:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2023-06-09T14:53:18+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=\"7 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-i\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/\"},\"author\":{\"name\":\"Oracle Team\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"headline\":\"Backup and Restore PostgreSQL with PgBackRest I\",\"datePublished\":\"2018-02-14T14:58:57+00:00\",\"dateModified\":\"2023-06-09T14:53:18+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/\"},\"wordCount\":501,\"commentCount\":0,\"keywords\":[\"Backup\",\"PostgreSQL\",\"PostgreSQL 10\",\"Restore\"],\"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-i\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/\",\"url\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/\",\"name\":\"Backup and Restore PostgreSQL with PgBackRest I - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#website\"},\"datePublished\":\"2018-02-14T14:58:57+00:00\",\"dateModified\":\"2023-06-09T14:53:18+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/#\\\/schema\\\/person\\\/66ab87129f2d357f09971bc7936a77ee\"},\"description\":\"PostgreSQL 10.1, PgBackRest, Backup, Restore\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.dbi-services.com\\\/blog\\\/backup-and-restore-postgresql-with-pgbackrest-i\\\/#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 I\"}]},{\"@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 I - dbi Blog","description":"PostgreSQL 10.1, PgBackRest, Backup, Restore","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-i\/","og_locale":"en_US","og_type":"article","og_title":"Backup and Restore PostgreSQL with PgBackRest I","og_description":"PostgreSQL 10.1, PgBackRest, Backup, Restore","og_url":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/","og_site_name":"dbi Blog","article_published_time":"2018-02-14T14:58:57+00:00","article_modified_time":"2023-06-09T14:53:18+00:00","author":"Oracle Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Oracle Team","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/"},"author":{"name":"Oracle Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"headline":"Backup and Restore PostgreSQL with PgBackRest I","datePublished":"2018-02-14T14:58:57+00:00","dateModified":"2023-06-09T14:53:18+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/"},"wordCount":501,"commentCount":0,"keywords":["Backup","PostgreSQL","PostgreSQL 10","Restore"],"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-i\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/","url":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/","name":"Backup and Restore PostgreSQL with PgBackRest I - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2018-02-14T14:58:57+00:00","dateModified":"2023-06-09T14:53:18+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/66ab87129f2d357f09971bc7936a77ee"},"description":"PostgreSQL 10.1, PgBackRest, Backup, Restore","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/backup-and-restore-postgresql-with-pgbackrest-i\/#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 I"}]},{"@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\/10809","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=10809"}],"version-history":[{"count":1,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10809\/revisions"}],"predecessor-version":[{"id":25762,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/10809\/revisions\/25762"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=10809"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=10809"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=10809"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=10809"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}