|
On 13/5/19 12:20 μ.μ., Prakash
Ramakrishnan wrote:
Hi Adrian,
Yes am using edb standard edition and installed
pgbackrest in prod and dev.
nothing different am trying to restore the backup prod to
dev cluster .
Can't
load '/usr/lib64/perl5/vendor_perl/auto/DBD/Pg/Pg.so'
for module DBD::Pg: libpq.so.5: cannot open shared
object file: No such file or directory at
/usr/lib64/perl5/DynaLoader.pm line 190.
at /loader/0x1ec1528/pgBackRest/Db.pm line 10.
at /loader/0x1ec1528/pgBackRest/Main.pm line
12.
pgBackRest::Main::__ANON__('Can\'t load
\'/usr/lib64/perl5/vendor_perl/auto/DBD/Pg/Pg.so\...')
called at /usr/share/perl5/vendor_perl/Carp.pm line 100
How did you install libdbd-pg-perl ?
There is a dependency from libdbd-pg-perl to libpq5 .
May be above path is corrupt or something issue not able
to load the path.
Regards,
Prakash.R
On
5/10/19 6:49 PM, Prakash Ramakrishnan wrote:
> Hi Adrian,
If I am following the below correctly you have EDB Postgres
and
pgBackRest running together on the prod server, correct?
If so what was done different/is different on the dev server?
>
> 1) How was the production Postgres installed(EDB, native
packages) and
> on what OS?
>
> prod has been installed edb standard edition .run file
and os CENTOS 7.5
>
> 2) The dev Postgres is the one installed using EDB
installer, correct?
>
> yes
>
> 3) Define working fine. In other words where you/are you
using a backup
> method other then pgBackRest on the production and dev
server?
>
> Please find prod config file and backup details,
>
> ==> cat /etc/pgbackrest.conf
> [global]
> repo1-path=/pgBACKUP/A4_sydcosafpp001
> retention-diff=3
> retention-full=1
> retention-archive=2
> start-fast=y
> process-max=12
> archive-async=y
>
>
> [global:archive-push]
> process-max=4
>
> [A4_sydcosafpp001]
> pg1-path=/Postgres/pgDATA/data
> postgres@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/postgres
> ==> cd /pgBACKUP/A4_sydcosafpp001/
> archive/ backup/
> postgres@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/postgres
> ==> cd
/pgBACKUP/A4_sydcosafpp001/backup/A4_sydcosafpp001/
>
postgres@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/pgBACKUP/A4_sydcosafpp001/backup/A4_sydcosafpp001
> ==> ls -lrth
> total 114K
> drwxr-x---. 4 postgres postgres 44 Jan 7 01:08
backup.history
> drwxr-x---. 3 postgres postgres 96 May 4 21:30
20190504-190001F
> drwxr-x---. 3 postgres postgres 96 May 5 19:41
> 20190504-190001F_20190505-190002I
> drwxr-x---. 3 postgres postgres 96 May 6 20:28
> 20190504-190001F_20190506-190002I
> drwxr-x---. 3 postgres postgres 96 May 7 20:26
> 20190504-190001F_20190507-190004I
> drwxr-x---. 3 postgres postgres 96 May 8 20:28
> 20190504-190001F_20190508-190002I
> drwxr-x---. 3 postgres postgres 96 May 9 20:32
> 20190504-190001F_20190509-190001I
> drwxr-x---. 3 postgres postgres 96 May 10 20:32
> 20190504-190001F_20190510-190001I
> lrwxrwxrwx. 1 postgres postgres 33 May 10 20:32 latest
->
> 20190504-190001F_20190510-190001I
> -rw-r-----. 1 postgres postgres 5.7K May 10 20:32 backup.info
> <http://backup.info>
> -rw-r-----. 1 postgres postgres 5.7K May 10 20:32
backup.info.copy
>
>
>
> 4) When you say single database are you talking about a
particular
> database in the Postgres cluster or the entire cluster?
>
> we need restore for single database for single cluster.
>
> 5) Why is pgBackRest essential to this? In other words
why not use the
> Postgres pg_dump/pg_restore tools?
>
> pgbackrest tool need for backup and restore larger
databases.
> if suppose am using pg_dump and restore they wont accept
it and taking
> too much time using parallel option also so we use for
pgbackrest.
>
>
> On Fri, May 10, 2019 at 9:44 PM Adrian Klaver <adrian.klaver@xxxxxxxxxxx
> <mailto:adrian.klaver@xxxxxxxxxxx>>
wrote:
>
> 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>
> > <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@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/postgres
> >
> >
> >
> > On Fri, May 10, 2019 at 8:15 PM Adrian Klaver
> <adrian.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>
> > <mailto:adrian.klaver@xxxxxxxxxxx
> <mailto:adrian.klaver@xxxxxxxxxxx>>>
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.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>
> <mailto:adrian.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>>
> >
> >
> >
> > --
> >
> >
> >
> > Thanks,
> > Prakash.R
> > PostgreSQL - Offshore DBA support TCS / Nielsen
Infrastructure
> Team On
> > call : +91-8939599426
>
>
> --
> Adrian Klaver
> adrian.klaver@xxxxxxxxxxx
<mailto:adrian.klaver@xxxxxxxxxxx>
>
>
>
> --
>
>
>
> Thanks,
> Prakash.R
> PostgreSQL - Offshore DBA support TCS / Nielsen
Infrastructure Team On
> call : +91-8939599426
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Thanks,
Prakash.R
PostgreSQL - Offshore DBA support TCS / Nielsen
Infrastructure Team On call : +91-8939599426
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
|
