{"id":2739,"date":"2012-12-07T05:56:00","date_gmt":"2012-12-07T04:56:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/"},"modified":"2012-12-07T05:56:00","modified_gmt":"2012-12-07T04:56:00","slug":"barman-une-solution-pour-vos-backups-postgresql","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/","title":{"rendered":"Barman: une solution pour vos backups PostgreSQL"},"content":{"rendered":"<p><img decoding=\"async\" class=\"blog-image aligncenter\" src=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png\" alt=\"\" \/><\/p>\n<p>L&#8217;objet de ce posting est de d\u00e9crire la mise en place et l&#8217;utilisation d&#8217;un gestionnaire de sauvegarde pour un cluster de\u00a0 base postgresql. Barman &#8211; acronyme de &#8220;backup recovery manager&#8221;- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C&#8217;est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.<\/p>\n<p>La soci\u00e9t\u00e9 2ndQuadrant est \u00e0 l&#8217;origine de ce projet qui a \u00e9t\u00e9 financ\u00e9 par une aide de la CEE.<\/p>\n<h3>1 &#8211; Installation du serveur de backup.<\/h3>\n<p>L&#8217;installation de l&#8217;outil peut se faire sur un serveur d\u00e9di\u00e9 ou sur le serveur PostgreSQL lui-m\u00eame.<\/p>\n<h4>1.1 &#8211; Validation des pre-requis<\/h4>\n<p>L&#8217;installation de Barman n\u00e9cessite d&#8217;avoir un acc\u00e8s root, voici la liste des pr\u00e9-requis.<\/p>\n<ul>\n<li>Linux\/Unix<\/li>\n<li>Python 2.6 or 2.7<\/li>\n<li>Python modules: *\n<ul>\n<li>argh<\/li>\n<li>psycopg2<\/li>\n<li>python-dateutil &lt; 2.0 (since version 2.0 requires python3)<\/li>\n<li>distribute (optional)<\/li>\n<\/ul>\n<\/li>\n<li>PostgreSQL &gt;= 8.4<\/li>\n<li>rsync &gt;= 3.0.4<\/li>\n<\/ul>\n<p>La v\u00e9rification des modules python peut \u00eatre faite avec la commande yokl -l<\/p>\n<p>exemple :<br \/>\n<samp><a href=\"mailto:root@ubuntu:~#\">root@ubuntu:~#<\/a> yolk -l | grep psycopg2<\/samp><samp><\/samp><samp>psycopg2\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &#8211; 2.4.5\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 &#8211; active development (\/usr\/local\/lib\/python2.7\/dist-packages\/psycopg2-2.4.5-py2.7-linux-x86_64.egg)<\/samp><\/p>\n<p><strong>Nota<\/strong> : La v\u00e9rification des modules python peut etre saut\u00e9 car l&#8217;installation v\u00e9rifie les d\u00e9pendances et charge les modules n\u00e9cessaires.<\/p>\n<p>V\u00e9rifier l&#8217;installation du package python-setuptools est suffisant.<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">sudo apt-get install python-setuptools\nReading package lists... Done\nBuilding dependency tree\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \nReading state information... Done\npython-setuptools is already the newest version.<\/pre>\n<h4>1.2 &#8211; Cr\u00e9ation de l&#8217;utilisateur barman<\/h4>\n<p>L&#8217;outils a besoin d&#8217;un utilisateur g\u00e9rant les backup<br \/>\n<samp>adduser &#8211;home \/home\/barman<\/samp><\/p>\n<h4>1.3 &#8211; Cr\u00e9ation des binaires<\/h4>\n<p>Installation des fichiers sources par copie puis extraction de ceux-ci\u00a0dans un r\u00e9pertoire local, ensuite on\u00a0construit et installe l&#8217;application avec les commandes ci-dessous.<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">.setup.py build\nsudo .setup.py install<\/pre>\n<h4>1.4 &#8211; ssh configuration.<\/h4>\n<p>Barman a besoin que les connexions entre le serveur de backups et les serveurs PostgreSQL \u00e0 sauvegarder soient transparentes. Pour cela on param\u00e8tre ssh avec une authentification par clef priv\u00e9e, publique. On proc\u00e8de \u00e0 la cr\u00e9ation des clefs puis \u00e0 une copie vers le serveur postgresql. <a href=\"postgres@srvdata1\">&#8216;postgres@srvdata1&#8217;<\/a>&#8220;, and check in: ~\/.ssh\/authorized_keysto make sure we haven&#8217;t added extra keys that you weren&#8217;t expecting.<\/p>\n<h4>\u00a01.5 &#8211; Configuration de la connexion PostgreSQL<\/h4>\n<p>Pour que l&#8217;outil acc\u00e9de aux informations \u00e0 sauvegarder\u00a0on configure le serveur postgresql en autorisant la connexion depuis le utilisateur barman. Pour cela modifier le fichier\u00a0pg_hba.conf de votre cluster de base en ajoutant la ligne suivante qui autorise une connexion sans demande de mot de passe entre les deux machines: <samp>host\u00a0\u00a0\u00a0 postgres\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 postgres\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.165.130\/32\u00a0\u00a0\u00a0\u00a0\u00a0 trust<\/samp> Verifier la bonne communication\u00a0par la commande ci-dessous depuis votre serveur barman. <samp>psql -c &#8216;SELECT version()&#8217; -U postgres -h srvdata1 -p 54321<\/samp><\/p>\n<h4>1.6\u00a0&#8211; Cr\u00e9ation du r\u00e9pertoire de sauvegarde.<\/h4>\n<p>Nous utiliserons ici un point de montage \/u03<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">cd \/u03\nsudo mkdir -p \/u03\/barman\nsudo chown barman:barman \/u03\/barman<\/pre>\n<h4>1.7 &#8211; Configuration de barman.<\/h4>\n<p>Elle se fait par copie du fichier barman.conf\u00a0dans \/etc et son adaptation \u00e0 notre situation<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">[barman]\n; Main directory\nbarman_home = \/u03\/barman\n; System user\nbarman_user = barman; Log location\nlog_file = \/home\/barman\/log\/barman.log\n; Default compression level: possible values are None (default), bzip2, gzip or custom\ncompression = gzip\n; 'main' PostgreSQL Server configuration\n[dbi]\n; Human readable description\ndescription =\u00a0 \"dbi PostgreSQL Database\"\n;\u00a0SSH options\nssh_command = ssh <a href=\"mailto:postgres@srvdata1\">postgres@srvdata1<\/a>\n; PostgreSQL connection string\nconninfo = host=\"srvdata1\" user=\"postgres\" port=54321<\/pre>\n<h4>1.8 &#8211; V\u00e9rification de la configuration<\/h4>\n<p>Une fois l&#8217;ensemble de ces param\u00e8trages pos\u00e9s, l&#8217;outil barman nous permet de v\u00e9rifier la configuration avec les deux commandes show-server et check, dont vous avez le r\u00e9sultat ci-dessous.<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"mailto:barman@pgbkpsrv:\/u03\/barman\/dbi$\">barman@pgbkpsrv:\/u03\/barman\/dbi$<\/a> barman show-server dbi\nServer dbi:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 active: true\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 description: dbi PostgreSQL Database\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ssh_command: ssh <a href=\"mailto:postgres@srvdata1\">postgres@srvdata1<\/a>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 conninfo: host=\"srvdata1\" user=\"postgres\" port=54321\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 backup_directory: \/u03\/barman\/dbi\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 basebackups_directory: \/u03\/barman\/dbi\/base\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 wals_directory: \/u03\/barman\/dbi\/wals\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 incoming_wals_directory: \/u03\/barman\/dbi\/incoming\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 lock_file: \/u03\/barman\/dbi\/dbi.lock\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 compression: gzip\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 custom_compression_filter: None\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 custom_decompression_filter: None\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 retention_policy: None\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 wal_retention_policy: None\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 current_xlog: 00000001000000000000001F\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 last_shipped_wal: None\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 archive_command: (disabled)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 server_txt_version: 9.1.4\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 data_directory: \/u01\/pgdata\/dbi\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 archive_mode: off\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 config_file: \/u01\/pgdata\/dbi\/postgresql.conf\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hba_file: \/u01\/pgdata\/dbi\/pg_hba.conf\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ident_file: \/u01\/pgdata\/dbi\/pg_ident.conf\n\n<a href=\"mailto:barman@pgbkpsrv:~$\">barman@pgbkpsrv:~$<\/a> barman check dbi\nServer dbi:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ssh: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PostgreSQL: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 archive_mode: FAILED (please set it to 'on')\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 archive_command: FAILED (please set it accordingly to documentation)\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 directories: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 compression settings: OK<\/pre>\n<p>On constate \u00e0 l&#8217;ex\u00e9cution de ces commandes qu&#8217;il nous reste \u00e0 configurer l&#8217;archivage du cluster de base.<\/p>\n<h3>2 &#8211;\u00a0Mise en oeuvre d&#8217;une sauvegarde<\/h3>\n<p>Pour cela nous allons d&#8217;abord\u00a0mettre le cluster de base en mode archive log, nous validerons ensuite la configuration avec les deux commandes\u00a0utilis\u00e9es pr\u00e9c\u00e9demment, enfin nous lancerons un backup.<\/p>\n<h4>2.1 &#8211; Passage en mode archive log<\/h4>\n<p>Il suffit de modifier du fichier postgresql.conf de votre cluster de base en changeant les trois param\u00e8tres ci-dessous :<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\">wal_level = 'archive' # For PostgreSQL &gt;= 9.0\narchive_mode = on\narchive_command = 'rsync -a %p barman@pgbkpsrv:\/u03\/barman\/dbi\/incoming\/%f'<\/pre>\n<h4>2.2 &#8211; restart du serveur postgresql<\/h4>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"mailto:ostgres@srvdata1:\/u01\/pgdata\/dbi$\">ostgres@srvdata1:\/u01\/pgdata\/dbi$<\/a> pg_ctl restart\nwaiting for server to shut down.... done\nserver stopped\nserver starting<\/pre>\n<h4>2.3 &#8211; V\u00e9rification<\/h4>\n<p>Lancement de la commande check<\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"mailto:barman@pgbkpsrv:\/u03\/barman\/dbi$\">barman@pgbkpsrv:\/u03\/barman\/dbi$<\/a> barman check dbi\nServer dbi:\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ssh: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PostgreSQL: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 archive_mode: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 archive_command: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 directories: OK\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 compression settings: OK<\/pre>\n<p>Nous constatons que tout est\u00a0conforme.<\/p>\n<h4>2.4 &#8211; Execution d&#8217;un backup.<\/h4>\n<p>Il s&#8217;agit de lancer la commande \u00e0 partir du serveur de\u00a0sauvegarde\u00a0comme ci-dessous. L&#8217;application prendra en charge l&#8217;ensemble des \u00e9tapes pour mettre le cluster de base en mode backup, puis copier les fichiers et finaliser la sauvegarde.<samp><\/samp><samp><\/samp><samp><br \/>\n<\/samp><\/p>\n<pre class=\"brush: actionscript3; gutter: true; first-line: 1\"><a href=\"mailto:barman@pgbkpsrv$\">barman@pgbkpsrv$<\/a> barman backup dbi\n<a href=\"mailto:barman@pgbkpsrv:\/u03\/barman\/dbi$\">barman@pgbkpsrv:\/u03\/barman\/dbi$<\/a> barman backup dbi\nStarting backup for server dbi in \/u03\/barman\/dbi\/base\/20120809T075347\nBackup start at xlog location: 0\/4A8DC890 (00000001000000000000004A, 008DC890)\nCopying files.\nfile has vanished: \"\/u01\/pgdata\/dbi\/base\/16660\/pg_internal.init\"\nCopy done.\nAsking PostgreSQL server to finalize the backup.\nBackup end at xlog location: 0\/4EBE4858 (00000001000000000000004E, 00BE4858)\nBackup completed<\/pre>\n<h3>3 &#8211; Conclusion<\/h3>\n<p>Barman nous fourni un ensemble de commandes nous permettant de mettre en oeuvre des sauvegardes online sur un serveur externe. La mise en oeuvre est simple, je vous propose d&#8217;aborder\u00a0dans un autre post le plus important: la restauration.<\/p>\n<p>Ref\u00e9rence: <a href=\"http:\/\/www.pgbarman.org\/\">http:\/\/www.pgbarman.org\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>L&#8217;objet de ce posting est de d\u00e9crire la mise en place et l&#8217;utilisation d&#8217;un gestionnaire de sauvegarde pour un cluster de\u00a0 base postgresql. Barman &#8211; acronyme de &#8220;backup recovery manager&#8221;- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C&#8217;est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs [&hellip;]<\/p>\n","protected":false},"author":28,"featured_media":2740,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[199],"tags":[202,329,77],"type_dbi":[],"class_list":["post-2739","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hardware-storage","tag-backup","tag-barman","tag-postgresql"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.2 (Yoast SEO v27.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Barman: une solution pour vos backups PostgreSQL - dbi Blog<\/title>\n<meta name=\"description\" content=\"L&#039;objet de ce posting est de d\u00e9crire la mise en place et l&#039;utilisation d&#039;un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de &quot;backup recovery manager&quot;- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C&#039;est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.\" \/>\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\/barman-une-solution-pour-vos-backups-postgresql\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Barman: une solution pour vos backups PostgreSQL\" \/>\n<meta property=\"og:description\" content=\"L&#039;objet de ce posting est de d\u00e9crire la mise en place et l&#039;utilisation d&#039;un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de &quot;backup recovery manager&quot;- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C&#039;est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2012-12-07T04:56:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png\" \/>\n\t<meta property=\"og:image:width\" content=\"196\" \/>\n\t<meta property=\"og:image:height\" content=\"118\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Open source 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=\"Open source Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 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\/barman-une-solution-pour-vos-backups-postgresql\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/\"},\"author\":{\"name\":\"Open source Team\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"headline\":\"Barman: une solution pour vos backups PostgreSQL\",\"datePublished\":\"2012-12-07T04:56:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/\"},\"wordCount\":709,\"commentCount\":0,\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png\",\"keywords\":[\"Backup\",\"Barman\",\"PostgreSQL\"],\"articleSection\":[\"Hardware &amp; Storage\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/\",\"name\":\"Barman: une solution pour vos backups PostgreSQL - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png\",\"datePublished\":\"2012-12-07T04:56:00+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b\"},\"description\":\"L'objet de ce posting est de d\u00e9crire la mise en place et l'utilisation d'un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de \\\"backup recovery manager\\\"- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C'est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png\",\"contentUrl\":\"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png\",\"width\":196,\"height\":118},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Barman: une solution pour vos backups PostgreSQL\"}]},{\"@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\/59554f0d99383431eb6ed427e338952b\",\"name\":\"Open source Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g\",\"caption\":\"Open source Team\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Barman: une solution pour vos backups PostgreSQL - dbi Blog","description":"L'objet de ce posting est de d\u00e9crire la mise en place et l'utilisation d'un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de \"backup recovery manager\"- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C'est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.","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\/barman-une-solution-pour-vos-backups-postgresql\/","og_locale":"en_US","og_type":"article","og_title":"Barman: une solution pour vos backups PostgreSQL","og_description":"L'objet de ce posting est de d\u00e9crire la mise en place et l'utilisation d'un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de \"backup recovery manager\"- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C'est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.","og_url":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/","og_site_name":"dbi Blog","article_published_time":"2012-12-07T04:56:00+00:00","og_image":[{"width":196,"height":118,"url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png","type":"image\/png"}],"author":"Open source Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Open source Team","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/"},"author":{"name":"Open source Team","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"headline":"Barman: une solution pour vos backups PostgreSQL","datePublished":"2012-12-07T04:56:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/"},"wordCount":709,"commentCount":0,"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png","keywords":["Backup","Barman","PostgreSQL"],"articleSection":["Hardware &amp; Storage"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/","url":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/","name":"Barman: une solution pour vos backups PostgreSQL - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage"},"image":{"@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage"},"thumbnailUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png","datePublished":"2012-12-07T04:56:00+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/59554f0d99383431eb6ed427e338952b"},"description":"L'objet de ce posting est de d\u00e9crire la mise en place et l'utilisation d'un gestionnaire de sauvegarde pour un cluster de base postgresql. Barman - acronyme de \"backup recovery manager\"- pour PostgreSQL est le logiciel sur lequel nous nous pencherons. C'est un outil permettant de centraliser la gestion des sauvegardes dans une situation avec plusieurs serveurs.","breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#primaryimage","url":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png","contentUrl":"https:\/\/www.dbi-services.com\/blog\/wp-content\/uploads\/sites\/2\/2022\/04\/2e1ax_default_entry_image4.png","width":196,"height":118},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/barman-une-solution-pour-vos-backups-postgresql\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Barman: une solution pour vos backups PostgreSQL"}]},{"@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\/59554f0d99383431eb6ed427e338952b","name":"Open source Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/eb4fb12e386e8c41fdef0733e8114594cf2653e4f55e9fa2161442b8eaf3f657?s=96&d=mm&r=g","caption":"Open source Team"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/open-source-team\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2739","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\/28"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=2739"}],"version-history":[{"count":0,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/2739\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media\/2740"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=2739"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=2739"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=2739"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=2739"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}