Pgbackrest fails due after an ISP change - Mailing list pgsql-general

From KK CHN
Subject Pgbackrest fails due after an ISP change
Date
Msg-id CAKgGyB-JTZ3ShAyQNMqmc-y0u4=0PzbqCyoCgsJq=EZpSC3-ug@mail.gmail.com
Whole thread Raw
Responses Re: Pgbackrest fails due after an ISP change
List pgsql-general
List,

I am running  a pgbackrest(2.52.1) backup setup for a postgres(16) server(RHEL9.4)  to a repo server RHEL 9.4..   

The pgbackrest was working fine and the remote repo server got regular backups through cron scheduler. 

Suddenly there was an ISP change at our  end,  the VPN tunnel  between DB server and Repo server was lost for  24 hours due to VPN tunnel crash.  later I restored the VPN tunnel

After that  the cron scheduler does not perform the pgbackrest backup. It fails!!!

So I performed a full backup to overcome this ..  But it fails  with the cron command (  38 14 * * 1 pgbackrest --type=full  --stanza=My_Repo backup) 


ERROR: [082]: WAL segment 000000010000022000000038 was not archived before the 60000ms timeout
                                    HINT: check the archive_command to ensure that all options are correct (especially --stanza).
                                    HINT: check the PostgreSQL server log for errors.
                                    HINT: run the 'start' command if the stanza was previously stopped.
                                    --------------------------------------------------------------------
                                    If SUBMITTING AN ISSUE please provide the following information:

                                    version: 2.52.1
                                    command: backup
                                    options: --delta --exec-id=492671-6f2068fc --log-level-console=info --log-level-file=debug --pg1-host=10.x.y.202 --pg1-host-user=enterprisedb --pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=5 --repo1-block --repo1-bundle --repo1-cipher-pass=<redacted> --repo1-cipher-type=aes-256-cbc --repo1-path=/DBBACKUP --repo1-retention-diff=3 --repo1-retention-full=3 --stanza=KTA_Repo --start-fast --type=full
2025-04-21 14:39:07.335 P00   INFO: backup command end: aborted with exception [082]
2025-04-21 14:39:07.335 P00  DEBUG:     command/exit::exitSafe: => 82
2025-04-21 14:39:07.936 P00  DEBUG:     main::main: => 82

How can I make the full backup command not to check the  WAL was archived or not  to the repo server for atleast once ?

Any hint  appreciated .. 

Thanks
Krishane


pgsql-general by date:

Previous
From: "Peter J. Holzer"
Date:
Subject: Re: Order of update
Next
From: Adrian Klaver
Date:
Subject: Re: Order of update