| From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgbackrest - question about restoring cluster to a new cluster on same server |
| Date: | 2019-09-19 01:15:00 |
| Message-ID: | 87a7b1m6i3.fsf@jsievers.enova.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Ron <ronljohnsonjr(at)gmail(dot)com> writes:
> Hi,
>
> (Thanks, Stephen, for helping with my earlier problem.)
>
> Scenario: there's data corruption on production server, so we need to
> do a PITR restore from "a few days ago" of the cluster holding the
> prod databases to a second cluster on that same VM in order to try and
> find the missing data and load it back into the prod cluster.
>
> Other than putting a high I/O load on the LUN where repo-path is
> located (from both writing WALs to it and reading the backed up
> files), will there be any problems when "pg_ctl start" processes
> recovery.conf and applies the WAL files to the new cluster while the
> prod cluster is writing new WAL files.
There should be no issues *if* you have insured that the 2 server
configurations do not overlap each other in any way.
HTH
> Does my question make sense?
>
> Thanks
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken Tanzer | 2019-09-19 01:26:29 | Re: PostgreSQL License |
| Previous Message | Ron | 2019-09-19 00:55:34 | Re: PostgreSQL License |