From: | Muhammad Usman Khan <usman(dot)k(at)bitnine(dot)net> |
---|---|
To: | postgr user <postgruser(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: barman with postgres server/s |
Date: | 2024-09-07 05:34:23 |
Message-ID: | CAPnRvGtX5hS+buPr=1=TtOddsUx_+0DRAaYL59MKG8k6suWxQg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(at)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(at)gmail(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | sud | 2024-09-07 09:29:37 | How effectively do the indexing in postgres in such cases |
Previous Message | Brent Wood | 2024-09-07 02:40:48 | Re: Foreign Data Wrappers |