MIME-Version: 1.0
References: <CAJTGK=ChxzghGkw+YR0sXNoUOvKSPXLW_EeP0ZNmB_7HFA=2+A@mail.gmail.com>
In-Reply-To: <CAJTGK=ChxzghGkw+YR0sXNoUOvKSPXLW_EeP0ZNmB_7HFA=2+A@mail.gmail.com>
From: Muhammad Usman Khan <usman.k@bitnine.net>
Date: Sat, 7 Sep 2024 10:34:23 +0500
Message-ID: <CAPnRvGtX5hS+buPr=1=TtOddsUx_+0DRAaYL59MKG8k6suWxQg@mail.gmail.com>
Subject: Re: barman with postgres server/s
To: postgr user <postgruser@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000012d092062180e11f"
Archived-At: <https://www.postgresql.org/message-id/CAPnRvGtX5hS%2BbuPr%3D1%3DTtOddsUx_%2B0DRAaYL59MKG8k6suWxQg%40mail.gmail.com>
Precedence: bulk

--00000000000012d092062180e11f
Content-Type: text/plain; charset="UTF-8"

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 <postgruser@gmail.com> 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
>

--00000000000012d092062180e11f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>I had the opportunity to work with barman. In m=
y opinion, to configure barman, you should have a separate=C2=A0dedicated=
=C2=A0system.=C2=A0

Configure WAL archiving properly to ensure that all transaction logs are st=
reamed to Barman like the following=C2=A0<br>archive_command =3D <span clas=
s=3D"gmail-hljs-string">&#39;rsync %p barman@backup_server:/path/to/backup/=
%f&#39;</span><br>Regular=C2=A0monitoring is required. You can check status=
 via barman check command<div>Use streaming replication by using this comma=
nd &#39;streaming_archiver=3Don&#39; in the barman.conf file.</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, =
6 Sept 2024 at 18:24, postgr user &lt;<a href=3D"mailto:postgruser@gmail.co=
m">postgruser@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div dir=3D"ltr">Does anyone know a best practice wh=
en it comes to installing barman?<div><br></div><div>Would barman be on its=
 own system or does it make sense=C2=A0to have it running on a cascaded pos=
tgres server?</div><div><br></div><div>I&#39;m just getting started with it=
 so I&#39;d like to see how others have implemented=C2=A0its use in a varie=
ty of different implementations of postgres servers or server.</div><div><b=
r></div><div><br></div><div>Thank you</div></div>
</blockquote></div>

--00000000000012d092062180e11f--