public inbox for [email protected]
help / color / mirror / Atom feedFrom: Muhammad Usman Khan <[email protected]>
To: postgr user <[email protected]>
Cc: [email protected]
Subject: Re: barman with postgres server/s
Date: Sat, 7 Sep 2024 10:34:23 +0500
Message-ID: <CAPnRvGtX5hS+buPr=1=TtOddsUx_+0DRAaYL59MKG8k6suWxQg@mail.gmail.com> (raw)
In-Reply-To: <CAJTGK=ChxzghGkw+YR0sXNoUOvKSPXLW_EeP0ZNmB_7HFA=2+A@mail.gmail.com>
References: <CAJTGK=ChxzghGkw+YR0sXNoUOvKSPXLW_EeP0ZNmB_7HFA=2+A@mail.gmail.com>
Hi,
I had the opportunity to work with barman. In my opinion, to configure
barman, you should have a separate dedicated system. Configure WAL
archiving properly to ensure that all transaction logs are streamed to
Barman like the following
archive_command = 'rsync %p barman@backup_server:/path/to/backup/%f'
Regular monitoring is required. You can check status via barman check
command
Use streaming replication by using this command 'streaming_archiver=on' in
the barman.conf file.
On Fri, 6 Sept 2024 at 18:24, postgr user <[email protected]> wrote:
> Does anyone know a best practice when it comes to installing barman?
>
> Would barman be on its own system or does it make sense to have it running
> on a cascaded postgres server?
>
> I'm just getting started with it so I'd like to see how others have
> implemented its use in a variety of different implementations of postgres
> servers or server.
>
>
> Thank you
>
view thread (2+ messages)
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: barman with postgres server/s
In-Reply-To: <CAPnRvGtX5hS+buPr=1=TtOddsUx_+0DRAaYL59MKG8k6suWxQg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox