| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Prakash Ramakrishnan <prakash(dot)ramakrishnan(dot)ap(at)nielsen(dot)com> |
| Cc: | Ravi Krishna <ravi_krishna(at)aol(dot)com>, David Steele <david(at)pgmasters(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: perl path issue |
| Date: | 2019-05-14 14:45:33 |
| Message-ID: | 388b82cb-239f-a340-b133-f0115ac77915@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/14/19 7:40 AM, Prakash Ramakrishnan wrote:
> Hi Adrian,
>
> Prod server retention periods ,
>
> [global]
> repo1-path=/pgBACKUP/A4_sydcosafpp001
> *retention-diff=3*
> *retention-full=1*
> *retention-archive=2*
> start-fast=y
> process-max=12
> archive-async=y
>
> Dev server currently we dont have only restore need to do prod to dev.
The issue is we are having trouble figuring out how the backups are
getting from one location to another and in what order. So could you
layout that out like I showed earlier:
prod Pg db --pgBackRest--> some_host/some_dir/some_file @daily
dev Pg db <--pgBackRest -- some_host/some_dir/some_file @3 weeks
>
> Regards,
> Prakash.R
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rene Romero Benavides | 2019-05-14 17:04:54 | Re: terminating walsender process due to replication timeout |
| Previous Message | Prakash Ramakrishnan | 2019-05-14 14:40:08 | Re: perl path issue |