Re: PgBackrest directory access from another server

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: PgBackrest directory access from another server
Date: 2025-08-20 10:43:55
Message-ID: CANzqJaB2shnjae_Z+a_wztA+zBjoM-UWf5K3FhxkhGHA8MeyiA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

What happens when repo2-host temporarily (for some arbitrarily long value
of "temporary") becomes inaccessible?

On Tue, Aug 19, 2025 at 11:22 AM bertrand HARTWIG <
hartwig(dot)bertrand(at)gmail(dot)com> wrote:

> hello,
>
> You may have corrupt or inconsistent data …
>
> Why don’t you use repo mirroring via pgBackRest ?
>
> Sample :
>
> [global]
>
> repo1-path=/pgbackrest/repo1
>
> repo2-path=/pgbackrest/repo2
>
> repo2-host= remote-host
>
>
>
> see
> https://pgbackrest.org/configuration.html#section-repository/option-repo-host
>
> sections 7.19 to 7.30
>
>
> Hope it helps
>
>
> Bertrand
>
>
>
>
> Le 19 août 2025 à 15:53, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> a écrit :
>
> Besides lag, is there any harm in rsyncing the contents of a repo-path on
> one server into the repo-path on a different server?
>
>
>

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Achilleas Mantzios 2025-08-20 10:54:59 Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server
Previous Message Michael Banck 2025-08-20 09:48:13 Re: upgrade from 18beta1 to 18beta3 gives : FATAL: database files are incompatible with server