Re: perl path issue - Mailing list pgsql-general
From | Adrian Klaver |
---|---|
Subject | Re: perl path issue |
Date | |
Msg-id | 3346d4e1-0c70-4379-69ef-1399ba6ec1e2@aklaver.com Whole thread Raw |
In response to | Re: perl path issue (Prakash Ramakrishnan <prakash.ramakrishnan.ap@nielsen.com>) |
List | pgsql-general |
On 5/15/19 2:37 AM, Prakash Ramakrishnan wrote: > 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. I don't use pgBackRest so I am speculating now, but I believe your issue is due to mixing local and remote operations. From a previous post: [global] repo1-host=sydcosafpp001.enterprisenet.org repo1-host-user=postgres repo1-host-config=/etc/pgbackrest.conf repo1-path=/pgBACKUP/A4_sydcosafpp001/backup/A4_sydcosafpp001 [A4_sydcosafpp001] pg1-path=/Postgres/prakash_pgbackrest postgres(at)sydcosausd001(dot)enterprisenet(dot)org:/home/postgres restore command - pgbackrest --stanza=A4_sydcosafpp001 --log-level-console=info --db-path=/Postgres/prakash_pgbackrest --delta --process-max=2 --db-include=A4_Copy restore --repo1-path=/pgBACKUP/A4_sydcosafpp001/backup/A4_sydcosafpp001 Looks to me are trying to use both a local(repo1-path) and remote(repo1-host*) repo at the same time. Given that the pgBackRest/EDB Postgres combination works on the prod server I would try doing a local only backup on the dev machine of the dev Postgres instance using the dev pgBackRest. This will help confirm whether there is a Perl issue on the dev machine or not. > > Regards, > Prakash.R > > On Tue, May 14, 2019 at 8:15 PM Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > > > -- > > > > Thanks, > Prakash.R > PostgreSQL - Offshore DBA support TCS / Nielsen Infrastructure Team On > call : +91-8939599426 -- Adrian Klaver adrian.klaver@aklaver.com
pgsql-general by date: