Thread: Reeving an error while taking the backup using "pg_basebackup" utility.

On Tue, Aug 28, 2018 at 07:19:12AM +0530, Raghavendra Rao J S V wrote:
> pg_basebackup: could not get transaction log end position from server:
> FATAL:  requested WAL segment 00000001000002850000008F has already been
> removed
>
> Please guide me why and how to handle this error. Do you want me to change
> any of the option in my pg_basebackup command let me know.

This means that while taking a backup, a checkpoint has come in and has
recycled past segments.  Lack of luck it is, as depending on the load
you may see such failures.  One way to correct the problem would be to
take a base backup without WAL segments included and with a WAL archive
used by the base backup taken.  A second is to use a physical
replication slot which guarantee the presence of the wanted segments.
--
Michael

On 08/27/2018 06:49 PM, Raghavendra Rao J S V wrote:
> Hi All,
> 
> We are using below command to take the backup of the database.
> 
> *$PGHOME/bin/pg_basebackup -p 5433 -U postgres -P -v -x --format=tar 
> --gzip --compress=1 --pgdata=- -D /opt/rao *
> 
> While taking the backup we have received below error.
> 
> transaction log start point: 285/8F000080
> 
> **
> 
> pg_basebackup: could not get transaction log end position from server: 
> FATAL:  requested WAL segment 00000001000002850000008F has already been 
> removed
> 
> Please guide me why and how to handle this error. Do you want me to 
> change any of the option in my pg_basebackup command let me know.

-X stream

See link below.

> 
> Please clarify me what it means *--pgdata=--D* in my above 
> *pg_basebackup *command.

https://www.postgresql.org/docs/10/static/app-pgbasebackup.html


> -- 
> Regards,
> Raghavendra Rao J S V
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com