From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Prakash Ramakrishnan <prakash(dot)ramakrishnan(dot)ap(at)nielsen(dot)com> |
Cc: | 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-10 16:14:16 |
Message-ID: | 1e51499e-a684-66d8-b69e-0fa8777ab300@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/10/19 7:50 AM, Prakash Ramakrishnan wrote:
> Hi Adrian,
>
> Production backup working fine now and previously dev server also
> working fine.
>
> Now the business team wants to restore the single database using
> pgbackrest tool so we have setup the pgbackrest.conf file is like to
> point prod .
The above is not much to go on. So a list of questions below. Please
answer them all, thanks:
1) How was the production Postgres installed(EDB, native packages) and
on what OS?
2) The dev Postgres is the one installed using EDB installer, correct?
3) Define working fine. In other words where you/are you using a backup
method other then pgBackRest on the production and dev server?
4) When you say single database are you talking about a particular
database in the Postgres cluster or the entire cluster?
5) Why is pgBackRest essential to this? In other words why not use the
Postgres pg_dump/pg_restore tools?
As to below, this more then a Perl issue it is a package incompatibility
issue.
>
> and directly restore the backup from prod so thats why not able to do
> some perl issue .
>
> database size is huge so they giving pressure and below is the config file,
>
> ==> cat /etc/pgbackrest.conf
> #[global]
> #repo1-path=/Postgres/pgBACKUP/A4_sydcosausd001
> #retention-diff=4
> #retention-full=4
> #retention-archive=2
> #start-fast=y
> #process-max=4
> #archive-async=y
>
>
> #[global:archive-push]
> #process-max=4
>
> #[A4_sydcosausd001]
> #db-path=/Postgres/pgDATA/data
>
> *
> *
> *[global]*
> *repo1-host=sydcosafpp001.enterprisenet.org
> <http://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
>
>
>
> On Fri, May 10, 2019 at 8:15 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>
> On 5/10/19 7:36 AM, Prakash Ramakrishnan wrote:
> > Hi Adrian,
> >
> > I did the installation for like ,
> >
> > postgresql-10.4-1-linux-x64.run file.
> >
> > pgbackrest - yum install
> >
> https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-redhat96-9.6-3.noarch.rp
>
> >
> <https://download.postgresql.org/pub/repos/yum/9.6/redhat/rhel-7-x86_64/pgdg-redhat96-9.6-3.noarch.rpm>m
> >
> >
> > yum install pgbackrest
>
> As explained upstream that is not going to work. The package YUM is
> installing is assuming that it will be working with Postgres installed
> from packages in the same repo. That is not the case. You might be able
> to download the pgBackrest source and build it pointing at the Perl in
> the EDB install, but I have no idea how to make that happen.
> >
> >
> > now what is the problem means we have to trying restore the
> backup prod
> > to dev server.
> >
>
> So was the prod backup taken with pgBackRest?
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>
>
>
> --
>
>
>
> Thanks,
> Prakash.R
> PostgreSQL - Offshore DBA support TCS / Nielsen Infrastructure Team On
> call : +91-8939599426
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2019-05-10 19:14:37 | Re: Hot Standby Conflict on pg_attribute |
Previous Message | Tom Lane | 2019-05-10 16:13:58 | Re: Query on pg_stat_activity table got stuck |