{"id":8177,"date":"2020-02-04T10:23:14","date_gmt":"2020-02-04T09:23:14","guid":{"rendered":"https:\/\/blog.capdata.fr\/?p=8177"},"modified":"2020-02-04T10:23:14","modified_gmt":"2020-02-04T09:23:14","slug":"postgresql-comparatif-entre-barman-et-pgbackrest","status":"publish","type":"post","link":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/","title":{"rendered":"PostgreSQL : Comparatif entre Barman et pgBackRest"},"content":{"rendered":"<a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-twitter nolightbox\" data-provider=\"twitter\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Twitter\" href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F8177&#038;text=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"twitter\" title=\"Share on Twitter\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-linkedin nolightbox\" data-provider=\"linkedin\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Linkedin\" href=\"https:\/\/www.linkedin.com\/shareArticle?mini=true&#038;url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F8177&#038;title=PostgreSQL%20%3A%20Comparatif%20entre%20Barman%20et%20pgBackRest\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"linkedin\" title=\"Share on Linkedin\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-mail nolightbox\" data-provider=\"mail\" rel=\"nofollow\" title=\"Share by email\" href=\"mailto:?subject=PostgreSQL%20%3A%20Comparatif%20entre%20Barman%20et%20pgBackRest&#038;body=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20:%20https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F8177\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"mail\" title=\"Share by email\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" \/><\/a><p>Il existe plusieurs types de sauvegardes sur PostgreSQL :<\/p>\n<ul>\n<li>Logique :\n<ul>\n<li>Export (pg_dump, pg_dumpall)<\/li>\n<\/ul>\n<\/li>\n<li>Physique :\n<ul>\n<li>A froid : (copie de tous les dossiers, instance \u00e9teinte)<\/li>\n<li>A chaud : (copie de tous les dossiers et des wals, instance ouverte)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<pre>\r\n<em>Vocabulaire :\r\n\tRPO (Recovery Point Objective) : Perte de Donn\u00e9es Maximale Admissible\r\n\tRTO (Recovery Time Objective) : Dur\u00e9e Maximale d\u2019Interruption Admissible\r\n<\/em><\/pre>\n<p>Avec un RPO faible, la perte de donn\u00e9es admissible est tr\u00e8s faible, voire nulle. Il faudra alors utiliser une solution de type sauvegarde \u00e0 chaud, PITR, r\u00e9plication (synchrone ou asynchrone).<br \/>\nAvec un RTO faible, la dur\u00e9e d\u2019interruption de service doit \u00eatre faible. Pour cela il faut une proc\u00e9dure avec le moins d\u2019actions et le moins d\u2019acteurs possible. Il faudra utiliser la r\u00e9plication et les solutions de haute disponibilit\u00e9. Ou dans le cas de perte de donn\u00e9es, utiliser une solution de PITR.<br \/>\nR\u00e9cemment j\u2019ai d\u00fb faire un comparatif de deux outils de sauvegardes PostgresQL, qui sont Barman et pgBackRest. Ces deux outils que nous \u00e9tudierons permettent de faire des sauvegardes physiques \u00e0 chaud et du Point In Time Recovery (PITR, Restauration \u00e0 un point pr\u00e9cis dans le temps). <\/p>\n<h2>Pr\u00e9sentation des outils :<\/h2>\n<h3>Barman (version 2.09) :<\/h3>\n<p>Barman (Backup And Restore MANager) est un outil d\u00e9velopp\u00e9 en Python, compatible uniquement avec les environnements Linux\/Unix. Il est principalement maintenu par la soci\u00e9t\u00e9 2ndQuadrant Italia.<\/p>\n<h3>pgBackRest (version 2.19) :<\/h3>\n<p>pgBackRest est un outil de gestion de sauvegardes PITR \u00e9crit en perl, par David Steele de Crunchy Data. Il est maintenu par Crunchy Data, une migration en C est en cours.<\/p>\n<h2>Comparatif fonctionnel :<\/h2>\n<table>\n<thead>\n<tr>\n<th>G\u00c9N\u00c9RALIT\u00c9S<\/th>\n<th>BARMAN<\/th>\n<th>PGBACKREST<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>GitHub<\/td>\n<td><a href='https:\/\/github.com\/2ndquadrant-it\/barman' target='_blank' rel=\"noopener noreferrer\">https:\/\/github.com\/2ndquadrant-it\/barman<\/a><\/td>\n<td><a href='https:\/\/github.com\/pgbackrest\/pgbackrest' target='_blank' rel=\"noopener noreferrer\">https:\/\/github.com\/pgbackrest\/pgbackrest<\/a><\/td>\n<\/tr>\n<tr>\n<td>Fait par<\/td>\n<td>2ndquadrant<\/td>\n<td>Crunchy Data<\/td>\n<\/tr>\n<tr>\n<td>Langage<\/td>\n<td>Python<\/td>\n<td>C \/ Perl (Migration en C)<\/td>\n<\/tr>\n<tr>\n<td>Installation<\/td>\n<td>yum \/ apt-get \/ apt install<\/td>\n<td>yum \/ apt-get \/ apt install<\/td>\n<\/tr>\n<tr>\n<td>Pr\u00e9requis<\/td>\n<td>Python >= 3.4 + modules\tperl + librairies<br \/>\n\t\t\trsync >= 3.0.4 (optionnel pour PostgreSQL >= 9.2)<\/td>\n<td>rsync<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><\/p>\n<table>\n<thead>\n<tr>\n<th>FONCTIONNALIT\u00c9S<\/th>\n<th>BARMAN<\/th>\n<th>PGBACKREST<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Architectures possible<\/td>\n<td>client\/serveur et mode local<\/td>\n<td>client\/serveur et mode local<\/td>\n<\/tr>\n<tr>\n<td>Catalogue centralis\u00e9<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Multithread\u00e9<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Permet de lancer des scripts automatiquement<\/td>\n<td>Oui<\/td>\n<td>Non<\/td>\n<\/tr>\n<tr>\n<td>Configuration<\/td>\n<td>Configuration centralis\u00e9e<\/td>\n<td>Configuration r\u00e9partie sur tous les serveurs<\/td>\n<\/tr>\n<tr>\n<td>Gestion et Administration<\/td>\n<td>Gestion et administration centralis\u00e9es (sur le serveur barman)<\/td>\n<td>Commandes d&#8217;utilisation r\u00e9parties : backup depuis le serveur, restauration depuis le client<\/td>\n<\/tr>\n<tr>\n<td>Gestion du stockage Cloud<\/td>\n<td>Oui (Amazon S3 Compatible Object Storage)<\/td>\n<td>Oui (Amazon S3 Compatible Object Storage)<\/td>\n<\/tr>\n<tr>\n<td>Chiffrement des sauvegardes<\/td>\n<td>Non<\/td>\n<td>Oui (chiffrage\/d\u00e9chiffrage par le serveur Postgres)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><\/p>\n<table>\n<thead>\n<tr>\n<th>SAUVEGARDE<\/th>\n<th>BARMAN<\/th>\n<th>PGBACKREST<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Sauvegarde Full<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Sauvegarde Diff\u00e9rentielle<\/td>\n<td>Non<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Sauvegarde Incr\u00e9mentale<\/td>\n<td>Oui (rsync + hardlink)<\/td>\n<td>Oui (checksum)<\/td>\n<\/tr>\n<tr>\n<td>Gestion de la r\u00e9tention<\/td>\n<td>count et\/ou nombre de jours (fen\u00eatre de restauration)<\/td>\n<td>count (au niveau full, diff\u00e9rentielle et WALs). Permet de r\u00e9duire la r\u00e9tention des WALs. (Exemple : fen\u00eatre de PITR de 7 jours et on garde les full des 4 derni\u00e8res semaines)<\/td>\n<\/tr>\n<tr>\n<td>Compression des backups<\/td>\n<td>Non<\/td>\n<td>Oui, choix du niveau de compression<\/td>\n<\/tr>\n<tr>\n<td>Compression r\u00e9seau<sup>1<\/sup><\/td>\n<td>Oui<\/td>\n<td>Oui, si les backups ne sont pas compress\u00e9s<\/td>\n<\/tr>\n<tr>\n<td>Supporte les backups concurrents<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Interruption d&#8217;une sauvegarde<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Reprise d&#8217;une sauvegarde en \u00e9chec<\/td>\n<td>Non<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Gestion des clusters<\/td>\n<td>Non, sauvegarde \u00e0 faire sur les deux n\u0153uds ou choix du n\u0153ud \u00e0 sauvegarder \u00e0 changer manuellement<\/td>\n<td>Oui, sauvegarde le n\u0153ud master (par d\u00e9faut) ou le n\u0153ud standby. D\u00e9tection du r\u00f4le des n\u0153uds automatique (utile dans le cas de HA)<\/td>\n<\/tr>\n<tr>\n<td>Liste des sauvegardes<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>D\u00e9tails des sauvegardes<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<pre>\r\n<em><sup>1<\/sup> La compression r\u00e9seau consiste \u00e0 compresser les fichiers pour r\u00e9duire la bande passante utilis\u00e9e pour le transfert r\u00e9seau. Les fichiers sont d\u00e9compress\u00e9s \u00e0 la fin du transfert. (i.e. pas de gain de volum\u00e9trie sur le stockage).<\/em>\r\n<\/pre>\n<p><\/p>\n<table>\n<thead>\n<tr>\n<th>WALs<\/th>\n<th>BARMAN<\/th>\n<th>PGBACKREST<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Archivage des WALS<\/td>\n<td>Par streaming et\/ou par l&#8217;archive_comand\n\t\t\t<\/td>\n<td>L&#8217;archive_command est modifi\u00e9e pour utiliser la commande &#8220;pgbackrest archive-push&#8221;.  L&#8217;envoi peut \u00eatre synchrone ou asynchrone. Dans ce second cas, les WALs sont copi\u00e9s sur un autre FS (local ou NFS). Un autre processus pgbackrest les envoie ensuite sur le serveur de sauvegarde. Ce mode permet aussi une restauration plus rapide.<\/td>\n<\/tr>\n<tr>\n<td>Compression des WALs<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Purge des WALs<\/td>\n<td>Fait lors de la purge des anciens backups<\/td>\n<td>Fait par \u00ab pgbackrest expire \u00bb ou en auto lors d&#8217;un backup. Les wals li\u00e9s \u00e0 une sauvegarde ne peuvent pas \u00eatre supprim\u00e9s.<\/td>\n<\/tr>\n<tr>\n<td>R\u00e9cup\u00e9ration des WALs pour la recovery (restore ou standby)<\/td>\n<td>barman get-wal<\/td>\n<td>pgbackrest archive-get<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><\/p>\n<table>\n<thead>\n<tr>\n<th>RESTAURATION<\/th>\n<th>BARMAN<\/th>\n<th>PGBACKREST<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Restauration inplace<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Restauration sur serveur autre ou \u00e0 une autre destination<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Restauration PITR<\/td>\n<td>Oui<\/td>\n<td>Oui<\/td>\n<\/tr>\n<tr>\n<td>Choix du backup sur lequel la restauration doit s\u2019appuyer<\/td>\n<td>Oui<\/td>\n<td>Non, par d\u00e9faut prend le dernier backup<\/td>\n<\/tr>\n<tr>\n<td>Choix des bases \u00e0 restaurer<\/td>\n<td>Non<\/td>\n<td>Oui<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Synth\u00e8se g\u00e9n\u00e9rale :<\/h2>\n<p>Les deux outils compar\u00e9s lors de ces tests ont chacun leurs avantages et leurs inconv\u00e9nients.<\/p>\n<h3>Barman<\/h3>\n<p>Les avantages :<\/p>\n<ul>\n<li>Streaming des wals<\/li>\n<li>Faible charge (CPU et RAM)<\/li>\n<li>R\u00e9tention en nombre de jours<\/li>\n<li>Stockage des backups vers Amazon S3 Compatible Object Storage<\/li>\n<li>Choisit le bon backup sur lequel s\u2019appuyer pour restaurer<\/li>\n<\/ul>\n<p>Les limites :<\/p>\n<ul>\n<li>Pas de compression des sauvegardes<\/li>\n<li>Pas de sauvegarde diff\u00e9rentielle<\/li>\n<li>Pas de gestion des clusters de haute disponibilit\u00e9<\/li>\n<li>Restauration plus lente<\/li>\n<li>Pas de reprise de sauvegarde en \u00e9chec<\/li>\n<li>Restauration de l\u2019instance uniquement<\/li>\n<\/ul>\n<h3>pgBackRest<\/h3>\n<p>Les avantages :<\/p>\n<ul>\n<li>Compression des sauvegardes<\/li>\n<li>Sauvegardes Full \/ Diff\u00e9rentielle \/ Incr\u00e9mentale<\/li>\n<li>Gestion diff\u00e9renci\u00e9e de la r\u00e9tention (Full \/ Diff\u00e9rentielle \/ Wals)<\/li>\n<li>Restauration plus rapide<\/li>\n<li>Gestion des clusters de haute disponibilit\u00e9<\/li>\n<li>Choix des bases \u00e0 restaurer<\/li>\n<li>Stockage des backups vers Amazon S3 Compatible Object Storage<\/li>\n<li>Chiffrement des sauvegardes (utile notamment pour les sauvegardes vers le cloud)<\/li>\n<\/ul>\n<p>Les limites : <\/p>\n<ul>\n<li>Charge CPU plus \u00e9lev\u00e9e (compression, chiffrement)<\/li>\n<li>Pas de streaming des wals<\/li>\n<li>Ne sait pas choisir le bon backup sur lequel s\u2019appuyer pour restaurer (prend le dernier par d\u00e9faut)<\/li>\n<\/ul>\n<h3>Conclusion :<\/h3>\n<p>Le choix d\u2019un outil d\u00e9pend du contexte dans lequel il sera utilis\u00e9. En fonction de ce dernier, il faudra privil\u00e9gier certaines fonctionnalit\u00e9s, ce qui orientera la d\u00e9cision. Chaque contexte \u00e9tant diff\u00e9rent, j\u2019esp\u00e8re que ce comparatif permettra de vous aider dans le choix de votre outil de sauvegarde de vos instances Postgres.<br \/>\nIl peut \u00eatre int\u00e9ressant de r\u00e9aliser des tests en conditions proches du r\u00e9el. <b>Et surtout, pensez \u00e0 tester vos sauvegardes et proc\u00e9dures r\u00e9guli\u00e8rement.<\/b><\/p>\n<h2>Sources :<\/h2>\n<p><a href='https:\/\/www.pgbarman.org' target='_blank' rel=\"noopener noreferrer\">https:\/\/www.pgbarman.org<\/a><br \/>\n<a href='https:\/\/www.pgbackrest.org' target='_blank' rel=\"noopener noreferrer\">https:\/\/www.pgbackrest.org<\/a><br \/>\n<a href='https:\/\/www.dalibo.com' target='_blank' rel=\"noopener noreferrer\">Dalibo<\/a><\/p>\n<a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-twitter nolightbox\" data-provider=\"twitter\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Twitter\" href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F8177&#038;text=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"twitter\" title=\"Share on Twitter\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/twitter.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-linkedin nolightbox\" data-provider=\"linkedin\" target=\"_blank\" rel=\"nofollow\" title=\"Share on Linkedin\" href=\"https:\/\/www.linkedin.com\/shareArticle?mini=true&#038;url=https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F8177&#038;title=PostgreSQL%20%3A%20Comparatif%20entre%20Barman%20et%20pgBackRest\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px;margin-right:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"linkedin\" title=\"Share on Linkedin\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/linkedin.png\" \/><\/a><a class=\"synved-social-button synved-social-button-share synved-social-size-24 synved-social-resolution-single synved-social-provider-mail nolightbox\" data-provider=\"mail\" rel=\"nofollow\" title=\"Share by email\" href=\"mailto:?subject=PostgreSQL%20%3A%20Comparatif%20entre%20Barman%20et%20pgBackRest&#038;body=Article%20sur%20le%20blog%20de%20la%20Capdata%20Tech%20Team%20%3A%20:%20https%3A%2F%2Fblog.capdata.fr%2Findex.php%2Fwp-json%2Fwp%2Fv2%2Fposts%2F8177\" style=\"font-size: 0px;width:24px;height:24px;margin:0;margin-bottom:5px\"><img loading=\"lazy\" decoding=\"async\" alt=\"mail\" title=\"Share by email\" class=\"synved-share-image synved-social-image synved-social-image-share\" width=\"24\" height=\"24\" style=\"display: inline;width:24px;height:24px;margin: 0;padding: 0;border: none;box-shadow: none\" src=\"https:\/\/blog.capdata.fr\/wp-content\/plugins\/social-media-feather\/synved-social\/image\/social\/regular\/48x48\/mail.png\" \/><\/a>","protected":false},"excerpt":{"rendered":"<p>Il existe plusieurs types de sauvegardes sur PostgreSQL : Logique : Export (pg_dump, pg_dumpall) Physique : A froid : (copie de tous les dossiers, instance \u00e9teinte) A chaud : (copie de tous les dossiers et des wals, instance ouverte) Vocabulaire&hellip; <a href=\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\" class=\"more-link\">Continuer la lecture <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":8182,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[266],"tags":[93,353,359,360,355,354,361,338,357,358,362,363,356],"class_list":["post-8177","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-postgresql","tag-backup","tag-barman","tag-database","tag-instance","tag-pgbackrest","tag-pgbarman","tag-pitr","tag-postgres","tag-restauation","tag-restore","tag-rpo","tag-rto","tag-sauvegarde"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>PostgreSQL : Comparatif entre Barman et pgBackRest - Capdata TECH BLOG<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"PostgreSQL : Comparatif entre Barman et pgBackRest - Capdata TECH BLOG\" \/>\n<meta property=\"og:description\" content=\"Il existe plusieurs types de sauvegardes sur PostgreSQL : Logique : Export (pg_dump, pg_dumpall) Physique : A froid : (copie de tous les dossiers, instance \u00e9teinte) A chaud : (copie de tous les dossiers et des wals, instance ouverte) Vocabulaire&hellip; Continuer la lecture &rarr;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\" \/>\n<meta property=\"og:site_name\" content=\"Capdata TECH BLOG\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-04T09:23:14+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2019\/12\/sauvegarde-image.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"585\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Capdata team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Capdata team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\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:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\"},\"author\":{\"name\":\"Capdata team\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/bfd9395c8ba4fa125792a543377035e9\"},\"headline\":\"PostgreSQL : Comparatif entre Barman et pgBackRest\",\"datePublished\":\"2020-02-04T09:23:14+00:00\",\"dateModified\":\"2020-02-04T09:23:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\"},\"wordCount\":1006,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"keywords\":[\"backup\",\"barman\",\"database\",\"instance\",\"pgbackrest\",\"pgbarman\",\"pitr\",\"Postgres\",\"restauation\",\"restore\",\"RPO\",\"RTO\",\"sauvegarde\"],\"articleSection\":[\"PostgreSQL\"],\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\",\"url\":\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\",\"name\":\"PostgreSQL : Comparatif entre Barman et pgBackRest - Capdata TECH BLOG\",\"isPartOf\":{\"@id\":\"https:\/\/blog.capdata.fr\/#website\"},\"datePublished\":\"2020-02-04T09:23:14+00:00\",\"dateModified\":\"2020-02-04T09:23:14+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/blog.capdata.fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"PostgreSQL : Comparatif entre Barman et pgBackRest\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.capdata.fr\/#website\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"name\":\"Capdata TECH BLOG\",\"description\":\"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting\",\"publisher\":{\"@id\":\"https:\/\/blog.capdata.fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.capdata.fr\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.capdata.fr\/#organization\",\"name\":\"Capdata TECH BLOG\",\"url\":\"https:\/\/blog.capdata.fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"contentUrl\":\"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp\",\"width\":800,\"height\":254,\"caption\":\"Capdata TECH BLOG\"},\"image\":{\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.capdata.fr\/#\/schema\/person\/bfd9395c8ba4fa125792a543377035e9\",\"name\":\"Capdata team\",\"sameAs\":[\"https:\/\/www.capdata.fr\"],\"url\":\"https:\/\/blog.capdata.fr\/index.php\/author\/admin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"PostgreSQL : Comparatif entre Barman et pgBackRest - Capdata TECH BLOG","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:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/","og_locale":"fr_FR","og_type":"article","og_title":"PostgreSQL : Comparatif entre Barman et pgBackRest - Capdata TECH BLOG","og_description":"Il existe plusieurs types de sauvegardes sur PostgreSQL : Logique : Export (pg_dump, pg_dumpall) Physique : A froid : (copie de tous les dossiers, instance \u00e9teinte) A chaud : (copie de tous les dossiers et des wals, instance ouverte) Vocabulaire&hellip; Continuer la lecture &rarr;","og_url":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/","og_site_name":"Capdata TECH BLOG","article_published_time":"2020-02-04T09:23:14+00:00","og_image":[{"width":585,"height":400,"url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2019\/12\/sauvegarde-image.jpg","type":"image\/jpeg"}],"author":"Capdata team","twitter_card":"summary_large_image","twitter_misc":{"\u00c9crit par":"Capdata team","Dur\u00e9e de lecture estim\u00e9e":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#article","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/"},"author":{"name":"Capdata team","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/bfd9395c8ba4fa125792a543377035e9"},"headline":"PostgreSQL : Comparatif entre Barman et pgBackRest","datePublished":"2020-02-04T09:23:14+00:00","dateModified":"2020-02-04T09:23:14+00:00","mainEntityOfPage":{"@id":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/"},"wordCount":1006,"commentCount":3,"publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"keywords":["backup","barman","database","instance","pgbackrest","pgbarman","pitr","Postgres","restauation","restore","RPO","RTO","sauvegarde"],"articleSection":["PostgreSQL"],"inLanguage":"fr-FR","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/","url":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/","name":"PostgreSQL : Comparatif entre Barman et pgBackRest - Capdata TECH BLOG","isPartOf":{"@id":"https:\/\/blog.capdata.fr\/#website"},"datePublished":"2020-02-04T09:23:14+00:00","dateModified":"2020-02-04T09:23:14+00:00","breadcrumb":{"@id":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.capdata.fr\/index.php\/postgresql-comparatif-entre-barman-et-pgbackrest\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/blog.capdata.fr\/"},{"@type":"ListItem","position":2,"name":"PostgreSQL : Comparatif entre Barman et pgBackRest"}]},{"@type":"WebSite","@id":"https:\/\/blog.capdata.fr\/#website","url":"https:\/\/blog.capdata.fr\/","name":"Capdata TECH BLOG","description":"Le blog technique sur les bases de donn\u00e9es de CAP DATA Consulting","publisher":{"@id":"https:\/\/blog.capdata.fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.capdata.fr\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/blog.capdata.fr\/#organization","name":"Capdata TECH BLOG","url":"https:\/\/blog.capdata.fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/","url":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","contentUrl":"https:\/\/blog.capdata.fr\/wp-content\/uploads\/2023\/01\/logo_capdata.webp","width":800,"height":254,"caption":"Capdata TECH BLOG"},"image":{"@id":"https:\/\/blog.capdata.fr\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/cap-data-consulting\/mycompany\/"]},{"@type":"Person","@id":"https:\/\/blog.capdata.fr\/#\/schema\/person\/bfd9395c8ba4fa125792a543377035e9","name":"Capdata team","sameAs":["https:\/\/www.capdata.fr"],"url":"https:\/\/blog.capdata.fr\/index.php\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8177","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/comments?post=8177"}],"version-history":[{"count":12,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8177\/revisions"}],"predecessor-version":[{"id":8275,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/posts\/8177\/revisions\/8275"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media\/8182"}],"wp:attachment":[{"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/media?parent=8177"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/categories?post=8177"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.capdata.fr\/index.php\/wp-json\/wp\/v2\/tags?post=8177"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}