pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Daulat Ram <Daulat.Ram@exponential.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: Barman
Date: Thu, 31 Oct 2019 19:56:46 +0100
Message-ID: <20191031185646.g6rmxczyowdhpeyg@development> (raw)
In-Reply-To: <MN2PR01MB5854D3BA0EBEEC8EDA58CE1A9B630@MN2PR01MB5854.prod.exchangelabs.com>
References: <MN2PR01MB5854D3BA0EBEEC8EDA58CE1A9B630@MN2PR01MB5854.prod.exchangelabs.com>

On Thu, Oct 31, 2019 at 05:29:34PM +0000, Daulat Ram wrote:
>Hi All,
>
>We have configured postgres 11.2 in streaming replication (primary &
>Standby)  on docker and I am looking to initiate the Postgres backup
>using barman. As I know there are few options for taking backup using
>barman.
>
>RSYNC backup
>Incremental Backups
>Streaming Backup with continuous WAL streaming
>Centralized and Catalogued Backups
>
>Which is the best option for backup using barman? So that we can keep
>the database safe in case of disaster? I feel the Incremental Backups
>are most useful to perform the PITR but I want to know the experts
>suggestions.
>

You're mixing a number of topics, here. Firstly, all backups done by
barman are centralized and catalogued, that's pretty much one of the
main purposes of barman.

When it comes to backup methods, there are two basic methods. rsync and
postgres (which means pg_basebackup). This is about creating the initial
base backup. Both methods then can replicate WAL by either streaming or
archive_command.

So first you need to decide whether to use rsync and pg_basebackup,
where rsync allows advanced features like incremental backup, parallel
backup and deduplication.

Then you need to decide whether to use archive_command or streaming
(i.e. pg_receivexlog).

The "right" backup method very much depends on the size of your
database, activity, and so on. By default you should probably go with
the default option, described as "scenario 1" in the barman docs, i.e.
pg_basebackup (backup_method = postgres) and WAL streaming.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (3+ messages)  latest in thread

Message-ID: <20191031185646.g6rmxczyowdhpeyg@development>
Permalink:  ../20191031185646.g6rmxczyowdhpeyg@development/
Also on:    postgresql.org/message-id/20191031185646.g6rmxczyowdhpeyg@development

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tomas.vondra@2ndquadrant.com, Daulat.Ram@exponential.com, pgsql-general@lists.postgresql.org, pgsql-performance@lists.postgresql.org
  Subject: Re: Barman
  In-Reply-To: <20191031185646.g6rmxczyowdhpeyg@development>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox