| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com>, Andreas Joseph Krogh <andreas(at)visena(dot)com> |
| Cc: | Daulat Ram <Daulat(dot)Ram(at)exponential(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres Point in time Recovery (PITR), |
| Date: | 2019-10-18 11:47:05 |
| Message-ID: | 3ff2963f-daab-81d4-ab1a-569fe1c8857b@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/18/19 11:29 AM, Luca Ferrari wrote:
> On Fri, Oct 18, 2019 at 10:30 AM Andreas Joseph Krogh
> <andreas(at)visena(dot)com> wrote:
>> We use barman (https://www.pgbarman.org/) for continuous streaming backup and I had to restore from it once, and it went like this:
>
> Just for the records, here's an example of restore with pgbackrest:
>
> % sudo -u postgres pgbackrest --stanza=miguel \
> --log-level-console=info --delta restore
> ...
> INFO: restore backup set 20190916-125652F
> INFO: remove invalid files/paths/links from /postgres/pgdata/11
> INFO: cleanup removed 148 files, 3 paths
> ...
> INFO: write /postgres/pgdata/11/recovery.conf
> INFO: restore global/pg_control (performed last
> to ensure aborted restores cannot be started)
> INFO: restore command end: completed successfully (5113ms)
pgBackRest also has a tutorial on PITR:
https://pgbackrest.org/user-guide.html#pitr
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron | 2019-10-18 11:48:09 | Re: Create role like role |
| Previous Message | Luca Ferrari | 2019-10-18 11:24:12 | Re: stable for each row before insert trigger |