Message-ID: <dbb641c11b5fd71c9f24ee886853dcea556ea027.camel@cybertec.at>
Subject: Re: Re. Backup
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Sushil Shirodkar <sushilps@hotmail.com>,
	"pgsql-admin@lists.postgresql.org"
	 <pgsql-admin@lists.postgresql.org>
Date: Thu, 03 Aug 2023 21:01:05 +0200
In-Reply-To: 
 <PH7PR10MB6225BB0156769A0E7B9C945AD408A@PH7PR10MB6225.namprd10.prod.outlook.com>
References: 
	<PH7PR10MB6225BB0156769A0E7B9C945AD408A@PH7PR10MB6225.namprd10.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/dbb641c11b5fd71c9f24ee886853dcea556ea027.camel%40cybertec.at>
Precedence: bulk

On Thu, 2023-08-03 at 17:20 +0000, Sushil Shirodkar wrote:
> We take regular backup along with WALs everyday no issues, but one day of
> the week regularly backup fails with the following error.
>=20
> ERROR: =C2=A0requested WAL segment 0000000C000008A10000000B has already b=
een removed
>=20
> We know the reason there is heavy database activity going during this per=
iod. But
> trying to avoid addition of more WAL files, is there any way to modify ou=
r backup
> command below which will take just the snapshot and not worry about the W=
ALs?=C2=A0
> playing with diff. options but no luck.=C2=A0=C2=A0
>=20
> pg_basebackup -h ${MASTER_TCP_ADDRESS} -U ${REP_USER} -D ${BACKUP_DIR} -X=
 fetch -Ft -zPw >>$LOG

You need the WAL, otherwise you cannot recover the backup.

Use "-X stream" instead of "-X fetch", and the problem will go away.

Yours,
Laurenz Albe
--=20
Cybertec | https://www.cybertec-postgresql.com