Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIieR-0000Ux-4F for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jan 2023 04:05:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pIieQ-00028B-12 for pgsql-admin@arkaria.postgresql.org; Fri, 20 Jan 2023 04:05:14 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIieP-000282-MW for pgsql-admin@lists.postgresql.org; Fri, 20 Jan 2023 04:05:13 +0000 Received: from tamriel.snowman.net ([70.109.60.50]) by magus.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pIieJ-00057z-6z for pgsql-admin@lists.postgresql.org; Fri, 20 Jan 2023 04:05:13 +0000 Received: by tamriel.snowman.net (Postfix, from userid 1000) id A7D985F7BA; Thu, 19 Jan 2023 23:05:05 -0500 (EST) Date: Thu, 19 Jan 2023 23:05:05 -0500 From: Stephen Frost To: Sbob Cc: Pgsql-admin Subject: Re: pgbackrest questions Message-ID: References: <10b9ec6d-414a-a92d-c053-84d679788214@quadratum-braccas.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Dbw/ZlmMl4RZ4DZo" Content-Disposition: inline In-Reply-To: <10b9ec6d-414a-a92d-c053-84d679788214@quadratum-braccas.com> User-Agent: Mutt/2.1.4 (2021-12-11) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Dbw/ZlmMl4RZ4DZo Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Greetings, * Sbob (sbob@quadratum-braccas.com) wrote: > 1) can I set recovery_target_action =3D 'pause' with a pgbackrest restore= and > then restart with a new timestamp if the data I am looking for has not yet > been restored? Yes you can set --target-action=3Dpause and then pgbackrest will set that for you in the PG config. After the initial restore is done though, you'd likely just change the target in the PG config instead of doing it with pgbackrest since you don't need an actual restore to be done (though you could, I suppose, use --delta with your restore, but that'd still involve a lot of files being restored and all of the WAL being replayed again, things that aren't really necessary...). > 2) can I go grab the base backup and wal files from pgbackrest and=A0 per= form > my own manual recovery if I wanted to? Depending on the options you give to pgbackrest, yes. pgbackrest was designed to allow for a user to use regular command-line tools such as gzip to turn the repo and WAL files back into a working cluster and that continues to work for simple configurations. When bundles or the soon to be released block-level incrementals are done with pgbackrest, however, that won't be possible as those options require that we combine PG files and hunks of files into larger files which aren't easy to pull back apart. Thanks, Stephen --Dbw/ZlmMl4RZ4DZo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEwf6gbxKhD863zrx/7WyKOINHZFUFAmPKEu0ACgkQ7WyKOINH ZFVIrQ/+P0c9JtliNqO+H/LLEiCZGXk3p63sV2LdfZUAO4vhaO33i5lttB3q/gFb XKNBQsk5Hmgx/kwF4HSUYXvXRxynf5skQBtYBLEp7T60A92YSDcXRgTEevMTauFD fmV5PjZIsE76mwQ2s/YQagFlgok+sV7YRQG41GtPnVI5w4ncNlP5sA6eb7FyhncR 8Ii/FqyvEYmDwVZdWr6A9vWHHzGc54i7WL6tAfwm2/iVgdc9dugeEqs/Uv8NqkPF DnMHbn7YGgv/VY4f6H+zS15IVxmbooz3yHUeNi8eRzXjMBm+PzytymNxcHWrhnNW jC5HRJukksHruDf6gQRsQ56UUqdFQ5JNX4T5fbZhzxS1IVsrpyPdo0JvlkA1H53N VyoXfpsOc0mCN50ibtpbgOdOrUM/xcgRC+xuSFq0pcB5QeXKMEKwkQXW8H8LUxQn xJqxTgRInowgCykZY7XqFgWspM3D4eO7hS+oOTrbuEhGGpDerBmD18Fy7oN7OMYo kpLKsDRVQwtnumLKwYSQ0THEeygVpBTV3EQ0QgT8J/IQyIYaCJargr3j8YaEeS01 oVa2uSqv+QpRBuNL6BPylJtWynMgu2v58DW4S0PCpdG0xuedvvcU2kLldOY/jWR1 LBzgzKsqS1hmDDPWv6kcDl8g81688wnrQQKoFmBPOF2oXb7Wx4U= =L5Wu -----END PGP SIGNATURE----- --Dbw/ZlmMl4RZ4DZo--