Subject: Re: PG backrest restore
To: Aldo Sarmiento <aldo@bigpurpledot.com>
References: 
 <CAHX=r6z7_DrwKfNOUCohRnbTfk5xxQAfQ4_yMVCu5a3WDQr+mg@mail.gmail.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
From: Stefan Fercot <stefan.fercot@dalibo.com>
Message-ID: <a9a1fbec-e0b1-0fe2-1367-9050a2c2ab77@dalibo.com>
Date: Thu, 11 Jan 2018 10:41:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: 
 <CAHX=r6z7_DrwKfNOUCohRnbTfk5xxQAfQ4_yMVCu5a3WDQr+mg@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="9zXGBSza4wP52esK1KnolflBcjsShipH0"
Precedence: bulk

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9zXGBSza4wP52esK1KnolflBcjsShipH0
Content-Type: multipart/mixed; boundary="2ORbLwxDvbuykWCNY9ygHOghZHYd1PdvW";
 protected-headers="v1"
From: Stefan Fercot <stefan.fercot@dalibo.com>
To: Aldo Sarmiento <aldo@bigpurpledot.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: <a9a1fbec-e0b1-0fe2-1367-9050a2c2ab77@dalibo.com>
Subject: Re: PG backrest restore
References: <CAHX=r6z7_DrwKfNOUCohRnbTfk5xxQAfQ4_yMVCu5a3WDQr+mg@mail.gmail.com>
In-Reply-To: <CAHX=r6z7_DrwKfNOUCohRnbTfk5xxQAfQ4_yMVCu5a3WDQr+mg@mail.gmail.com>

--2ORbLwxDvbuykWCNY9ygHOghZHYd1PdvW
Content-Type: multipart/alternative;
 boundary="------------597EE8173C0AC1AE96D6D8EF"
Content-Language: fr-classic

This is a multi-part message in MIME format.
--------------597EE8173C0AC1AE96D6D8EF
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi,

Do you have some restore_command in the recovery.conf of your replica ?

i.e.

restore_command =3D '/usr/bin/pgbackrest --stanza=3Ddemo archive-get %f "=
%p"'


On 01/11/2018 10:37 AM, Aldo Sarmiento wrote:
> I have streaming replication setup between a master/slave. The other
> day the slave had some issues and couldn=E2=80=99t be brought up before=
 WAL
> logs got archived via pgbackrest archive command. Is there a way to
> bring the replica up to date using the pg backrest archives so that I
> can start streaming again? Currently it=E2=80=99s complaining that the =
master
> doesn=E2=80=99t have the WAL logs in pg_xlog directory to do so. Thank =
you, Aldo

--=20
Stefan FERCOT
http://dalibo.com - http://dalibo.org


--------------597EE8173C0AC1AE96D6D8EF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>Hi,</p>
    <p>Do you have some restore_command in the recovery.conf of your
      replica ?</p>
    <p>i.e. <br>
    </p>
    <pre class=3D"execute-body-output">restore_command =3D '/usr/bin/pgba=
ckrest --stanza=3Ddemo archive-get %f "%p"'</pre>
    <br>
    <div class=3D"moz-cite-prefix">On 01/11/2018 10:37 AM, Aldo Sarmiento=

      wrote:<br>
    </div>
    <blockquote type=3D"cite"
cite=3D"mid:CAHX=3Dr6z7_DrwKfNOUCohRnbTfk5xxQAfQ4_yMVCu5a3WDQr+mg@mail.gm=
ail.com">
      <div style=3D"white-space:pre-wrap">I have streaming replication se=
tup between a master/slave. The other day the slave had some issues and c=
ouldn=E2=80=99t be brought up before WAL logs got archived via pgbackrest=
 archive command.

Is there a way to bring the replica up to date using the pg backrest arch=
ives so that I can start streaming again? Currently it=E2=80=99s complain=
ing that the master doesn=E2=80=99t have the WAL logs in pg_xlog director=
y to do so.

Thank you,
Aldo </div>
    </blockquote>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Stefan FERCOT
<a class=3D"moz-txt-link-freetext" href=3D"http://dalibo.com">http://dali=
bo.com</a> - <a class=3D"moz-txt-link-freetext" href=3D"http://dalibo.org=
">http://dalibo.org</a></pre>
  </body>
</html>

--------------597EE8173C0AC1AE96D6D8EF--

--2ORbLwxDvbuykWCNY9ygHOghZHYd1PdvW--

--9zXGBSza4wP52esK1KnolflBcjsShipH0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEGqVD/TfbxT1NtG2cKv35I2qhWC8FAlpXMVAACgkQKv35I2qh
WC87iggAqX64x5ak1kM616u5m066iQ8101zKCBMflmxAjmKc/rNw+qWxYH7jWSSD
3Qu/05DFkaxN1NQ02UYv3q5gncMiyMnWwYF0uPzh3RAmHvtE5YYIZRH3ylpYFibE
Begs2sHhX1LOQe2Nqfzsnu6E0gsTEXuLifEE/YtNgvKRkTIEwLgMIf+MOsi8W55M
G9F7KplETwAP1y5w7yLhKScd4JdCjTI0jzv5Ng0B0bl6MXT1V2VNqoOWxaO+Pb/W
/p8f56Y7lJkTQqycpeIXz9g7W9PI5YtqozO3/OIZTqf0HYXAN02DGPFP2yNh27Ev
18xheiNgL/1roNPu+xpm9vLr8ZxAnw==
=DXKZ
-----END PGP SIGNATURE-----

--9zXGBSza4wP52esK1KnolflBcjsShipH0--