MIME-Version: 1.0
References: 
 <CAEu96cXnBOEiDTC+uCRJwNWqaLT-+ApgA_VOehdfO-9Ntmsc9w@mail.gmail.com>
In-Reply-To: 
 <CAEu96cXnBOEiDTC+uCRJwNWqaLT-+ApgA_VOehdfO-9Ntmsc9w@mail.gmail.com>
From: Venkat Akhil Pavuluri <akhil.venkat@opensource-db.com>
Date: Wed, 1 Jul 2026 12:58:24 +0530
Message-ID: 
 <CAPCUgKrSm3rqQ=yqS-SbFL5awaBN=pT=uxiurhPx9PH9cRaurA@mail.gmail.com>
Subject: Re: Postgresql Wal archive and Barman setup
To: sa sa <ssmaugust@gmail.com>
Cc: pgsql-general@postgresql.org
Content-Type: multipart/alternative; boundary="000000000000ca74c9065587a398"
Archived-At: 
 <https://www.postgresql.org/message-id/CAPCUgKrSm3rqQ%3DyqS-SbFL5awaBN%3DpT%3DuxiurhPx9PH9cRaurA%40mail.gmail.com>
Precedence: bulk

--000000000000ca74c9065587a398
Content-Type: text/plain; charset="UTF-8"

Hi sa sa,

As per the best practices, maintain different mount points for the data
directory and the archive location. In your case, data_directory is
`/srv/data` and the archive location is `/srv/archive`, meaning both reside
on the `/srv/` mount point. If your archive location is on a different
mount point, your archives will fail (which will have its own
repercussions) but your cluster will remain operational.

And also having alert system to send mails will help you as Masheed said.

Thanks and Regards
Venkat Akhil P
OpenSource DB
Your Trusted Data Partner


On Wed, 1 Jul 2026 at 02:06, sa sa <ssmaugust@gmail.com> 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
>

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

<div dir=3D"ltr"><div>Hi sa sa,<br><br>As per the best practices, maintain =
different mount points for the data directory and the archive location. In =
your case, data_directory is `/srv/data` and the archive location is `/srv/=
archive`, meaning both reside on the `/srv/` mount point. If your archive l=
ocation is on a different mount point, your archives will fail (which will =
have its own repercussions) but your cluster will remain operational.=C2=A0=
<br><br>And also having alert system to send mails will help you as Masheed=
 said.<br><br></div><div><div dir=3D"ltr" class=3D"gmail_signature" data-sm=
artmail=3D"gmail_signature"><div dir=3D"ltr">Thanks and Regards<br>Venkat A=
khil P<br>OpenSource DB<br>Your Trusted Data Partner</div></div></div><br><=
/div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" =
class=3D"gmail_attr">On Wed, 1 Jul 2026 at 02:06, sa sa &lt;<a href=3D"mail=
to:ssmaugust@gmail.com">ssmaugust@gmail.com</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Hello All,<div>=
<br></div><div>=C2=A0I have a scenario, where I need some suggestions and i=
mprovements if applicable.</div><div><br></div><div>Our setup in brief</div=
><div>1) Primary --&gt; standby</div><div>=C2=A0 =C2=A0 using archive_comma=
nd =3D rsync to primary local location and standby local location</div><div=
>2) Primary --&gt; Barman</div><div>=C2=A0 =C2=A0 Using streaming. Barman b=
ackup location is /nfs/DD9</div><div>3) Archive cleanup on primary is setup=
 via crontab to every 14 days.</div><div><br></div><div><span style=3D"colo=
r:rgb(0,0,0);font-size:medium">Here is my scenario, If my barman nfs is dow=
n for 5 days and my local archive location is filled up during this time. w=
hat will happen.</span><br></div><div><span style=3D"color:rgb(0,0,0);font-=
size:medium"><br></span></div><div><font color=3D"#000000" size=3D"3">if my=
 /srv/archive (location archive wal location) on primary and standby is 100=
% full during this time.=C2=A0</font></div><div><font color=3D"#000000" siz=
e=3D"3">my /srv/data is going to be 100% full , causing my cluster to go do=
wn.</font></div><div><font color=3D"#000000" size=3D"3"><br></font></div><d=
iv><font color=3D"#000000" size=3D"3">So what are the suggestions to avoid =
this situation.</font></div><div><font color=3D"#000000" size=3D"3"><br></f=
ont></div><div><font color=3D"#000000" size=3D"3">Thanks,</font></div><div>=
<font color=3D"#000000" size=3D"3">Sa</font></div></div>
</blockquote></div>

--000000000000ca74c9065587a398--