From: | Prakash Ramakrishnan <prakash(dot)ramakrishnan(dot)ap(at)nielsen(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(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-15 09:37:01 |
Message-ID: | CAA2eZXxx4OZYqEZM8xGVCKSfU7YwjtK7bCfOhGZ0a2vTuSLY2A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Adrian,
I don't much about pgbackrest i think it will take backup from archives Now
only one the issue means perl cant load.
Regards,
Prakash.R
On Tue, May 14, 2019 at 8:15 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> 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
>
--
Thanks,
Prakash.R
PostgreSQL - Offshore DBA support TCS / Nielsen Infrastructure Team On call
: +91-8939599426
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-05-15 14:20:54 | Re: perl path issue |
Previous Message | AYahorau | 2019-05-15 07:04:12 | Re: terminating walsender process due to replication timeout |