| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | 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 09:29:04 |
| Message-ID: | CAKoxK+7PpV6G16nuXhuUjUN_SNVjUsVM2s5ns_AMUvksgys52A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick FICHE | 2019-10-18 09:51:04 | Execute a function through fdw |
| Previous Message | Олег Самойлов | 2019-10-18 09:18:21 | Re: stable for each row before insert trigger |