Re: perl path issue - Mailing list pgsql-general

From Prakash Ramakrishnan
Subject Re: perl path issue
Date
Msg-id CAA2eZXw8mRr_WjtX4YPCbVd=RS-kauqfTqGAM-qycAQefNhF8w@mail.gmail.com
Whole thread Raw
In response to Re: perl path issue  (Ravi Krishna <ravi_krishna@aol.com>)
Responses Re: perl path issue
Re: perl path issue
List pgsql-general
Hi Ravi,

Not , am saying we have the daily backup and full backup in prod server only and there is one database like a4 the db size is 1.5TB.
so am not restore again in prod .
Am taking directly single backup restore in dev its means in dev server only restore the database in new cluster.
existing cluster we cant restore backups.
so thats why am struggling the issue getting some perl issue and remote option terminated otherwise wont disturb anyone and need to solve this issue.
this activity has been planned every 3 weeks.

Regards,
Prakash.R

On Tue, May 14, 2019 at 3:10 PM Ravi Krishna <ravi_krishna@aol.com> wrote:
>
> Note - if am taking same prod single database backup and restore in new cluster no use for us and it will take more time.
> so business and team they need every 3 weeks for restore in dev server one single database and cant we do it in pg_dump and restore .
> They want using pgbackrest tool the db size is huge so tats why am trying remote restore option.

I am baffled.  Are you telling that you are restoring it back on prod (using remote restore option),
which effectively means overwriting prod db.  Also you never gave this information until now. You
should have shared full details.

I have not used pgbackest, but I have read the FAQ. If I am not mistaken it has single db restore option too. So you can restore
the db in dev.




--



Thanks,
Prakash.R
PostgreSQL - Offshore DBA support TCS / Nielsen Infrastructure Team On call : +91-8939599426

pgsql-general by date:

Previous
From: Ravi Krishna
Date:
Subject: Re: perl path issue
Next
From: Ravi Krishna
Date:
Subject: Re: perl path issue