public inbox for [email protected]  

help / color / mirror / Atom feed

From: masheed ullah <[email protected]>
To: sa sa <[email protected]>
Cc: [email protected]
Subject: Re: Postgresql Wal archive and Barman setup
Date: Wed, 1 Jul 2026 10:15:14 +0300
Message-ID: <CAHr8x_s-EBi4Fk-1aM1xB0iFn9p35+inu6SNN=LVpAZyuo+W2w@mail.gmail.com> (raw)
In-Reply-To: <CAEu96cXnBOEiDTC+uCRJwNWqaLT-+ApgA_VOehdfO-9Ntmsc9w@mail.gmail.com>
References: <CAEu96cXnBOEiDTC+uCRJwNWqaLT-+ApgA_VOehdfO-9Ntmsc9w@mail.gmail.com>

You need to actively monitor archive location to avoid space issue.

Schedule a job to send alert email when archive location full to 80% or 90%

Best Regards,
*Masheed Ullah*



On Tue, Jun 30, 2026, 11:36 PM sa sa <[email protected]> wrote:

> Hello All,
>
>  I have a scenario, where I need some suggestions and improvements if
> applicable.
>
> Our setup in brief
> 1) Primary --> standby
>     using archive_command = rsync to primary local location and standby
> local location
> 2) Primary --> Barman
>     Using streaming. Barman backup location is /nfs/DD9
> 3) Archive cleanup on primary is setup via crontab to every 14 days.
>
> Here is my scenario, If my barman nfs is down for 5 days and my local
> archive location is filled up during this time. what will happen.
>
> if my /srv/archive (location archive wal location) on primary and standby
> is 100% full during this time.
> my /srv/data is going to be 100% full , causing my cluster to go down.
>
> So what are the suggestions to avoid this situation.
>
> Thanks,
> Sa
>

view thread (3+ messages)  latest in thread

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]
  Subject: Re: Postgresql Wal archive and Barman setup
  In-Reply-To: <CAHr8x_s-EBi4Fk-1aM1xB0iFn9p35+inu6SNN=LVpAZyuo+W2w@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