| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | KK CHN <kkchn(dot)in(at)gmail(dot)com> |
| Cc: | Ruben Morais <ruben(dot)gmorais(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgbackrest check info fails without success |
| Date: | 2025-08-15 16:45:54 |
| Message-ID: | CAKAnmmKbzOkpJDpV7Om=A-sEYhoYs_TGn_AoNo39nUEMCiohnA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Aug 13, 2025 at 7:20 AM KK CHN <kkchn(dot)in(at)gmail(dot)com> wrote:
> INFO: archive-push command begin 2.52.1: [pg_wal/000000010000001900000010]
> --archive-async --compress-type=zst --exec-id=4180767-84540d74
> --log-level-console=info --log-level-file=debug --log-level-stderr=info
> --pg1-path=/data/edb/as16/data --pg-version-force=16 --process-max=6
> --repo1-host=10.50.2.202 --repo1-host-user=pgbackrest --repo1-path=/DB_BKUP
> --spool-path=/var/spool/pgbackrest --stanza=K_Repo
> ERROR: [062]: stop file exists for stanza K_Repo
> ...
> So the N/W latency badly affects the Pgbackrest working ?
>
No - see the ERROR above. You have a stop file that you need to remove. See:
https://pgbackrest.org/user-guide.html#start-stop
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2025-08-18 02:36:48 | Re: analyze-in-stages post upgrade questions |
| Previous Message | Greg Sabino Mullane | 2025-08-15 16:40:18 | Re: Questions about the continuity of WAL archiving |