pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Backup issue
6+ messages / 5 participants
[nested] [flat]

* Backup issue
@ 2005-09-17 07:49 Marcin Giedz <marcin.giedz@eulerhermes.pl>
  2005-09-17 16:31 ` Re: Backup issue Jeff Frost <jeff@frostconsultingllc.com>
  2005-09-19 16:52 ` Re: Backup issue Scott Marlowe <smarlowe@g2switchworks.com>
  0 siblings, 2 replies; 6+ messages in thread

From: Marcin Giedz @ 2005-09-17 07:49 UTC (permalink / raw)
  To: pgsql-admin

Hello...

This is what I have now: postgresql 8.0.1 - database weights about 60GB 
and increases about 2GB per week. Nowadays I do backup every day - 
according to simple procedure (pg_start_backup:rsync 
data:pg_stop_backup:save wals produced during backup). On 1Gb internal 
network it usually takes me about 1h to perform this procedure.

But what if my database has ~200GB and more (I know this is a future 
:D)? From my point of view it won't be good idea to copy entire database 
to backup array. I would like to here opinions about this case - what do 
you propose? Maybe some of you already do something like this?

Regards,
Marcin Giedz



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Backup issue
  2005-09-17 07:49 Backup issue Marcin Giedz <marcin.giedz@eulerhermes.pl>
@ 2005-09-17 16:31 ` Jeff Frost <jeff@frostconsultingllc.com>
  1 sibling, 0 replies; 6+ messages in thread

From: Jeff Frost @ 2005-09-17 16:31 UTC (permalink / raw)
  To: Marcin Giedz <marcin.giedz@eulerhermes.pl>; +Cc: pgsql-admin

Marcin,

What I have done in the past is setup a bi-monthly base backup 
(pg_start_backup:rsync data:pg_stop_backup) and archive the WAL files between 
base backups with the archive_command option in postgresql.conf, saving 2 base 
backups and removing anything older than the oldest base backup.  If you use 
rsync with the --link-dest option you can possibly save much space between the 
two base backups if you do not have many deletes in your DB.  The --link-dest 
option assume you are rsyncing to a filesystem which supports hardlinks.  I 
also gzip the WAL files when archiving them.

> But what if my database has ~200GB and more (I know this is a future :D)? 
> From my point of view it won't be good idea to copy entire database to backup 
> array. I would like to here opinions about this case - what do you propose? 
> Maybe some of you already do something like this?

-- 
Jeff Frost, Owner 	<jeff@frostconsultingllc.com>
Frost Consulting, LLC 	http://www.frostconsultingllc.com/
Phone: 650-780-7908	FAX: 650-649-1954



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Backup issue
  2005-09-17 07:49 Backup issue Marcin Giedz <marcin.giedz@eulerhermes.pl>
@ 2005-09-19 16:52 ` Scott Marlowe <smarlowe@g2switchworks.com>
  1 sibling, 0 replies; 6+ messages in thread

From: Scott Marlowe @ 2005-09-19 16:52 UTC (permalink / raw)
  To: Marcin Giedz <marcin.giedz@eulerhermes.pl>; +Cc: pgsql-admin

On Sat, 2005-09-17 at 02:49, Marcin Giedz wrote:
> Hello...
> 
> This is what I have now: postgresql 8.0.1 - database weights about 60GB 
> and increases about 2GB per week. Nowadays I do backup every day - 
> according to simple procedure (pg_start_backup:rsync 
> data:pg_stop_backup:save wals produced during backup). On 1Gb internal 
> network it usually takes me about 1h to perform this procedure.
> 
> But what if my database has ~200GB and more (I know this is a future 
> :D)? From my point of view it won't be good idea to copy entire database 
> to backup array. I would like to here opinions about this case - what do 
> you propose? Maybe some of you already do something like this?

I'd look at using PITR replication, with a monthly or so fresh, whole 
backup instead of a whole backup every day.



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Backup issue
@ 2019-09-05 10:32 mallikarjun t <mallit333@gmail.com>
  2019-09-05 11:39 ` Re: Backup issue Luca Ferrari <fluca1978@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: mallikarjun t @ 2019-09-05 10:32 UTC (permalink / raw)
  To: Pgsql-admin <pgsql-admin@lists.postgresql.org>

Dear All,

I try to take remote backup and  restore to local EDB Advanced Server this
error is coming, If any one knows this issue please clarify me?

Please look into the error message:

[postgres@localhost bin]$ pg_dump -h 192.168.211.148 -p 5432 -Fc -n
myschema -f /tmp/schema_my.custom
Password:
pg_dump: [archiver (db)] query failed: ERROR:  unrecognized configuration
parameter "qreplace_function"
pg_dump: [archiver (db)] query was: SHOW qreplace_function


Regards,
Malli.

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Backup issue
  2019-09-05 10:32 Backup issue mallikarjun t <mallit333@gmail.com>
@ 2019-09-05 11:39 ` Luca Ferrari <fluca1978@gmail.com>
  2019-09-05 11:49   ` Re: Backup issue mallikarjun t <mallit333@gmail.com>
  0 siblings, 1 reply; 6+ messages in thread

From: Luca Ferrari @ 2019-09-05 11:39 UTC (permalink / raw)
  To: mallikarjun t <mallit333@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>

On Thu, Sep 5, 2019 at 12:59 PM mallikarjun t <mallit333@gmail.com> wrote:
>
> Dear All,
>
> I try to take remote backup and  restore to local EDB Advanced Server this error is coming, If any one knows this issue please clarify me?
>
> Please look into the error message:
>
> [postgres@localhost bin]$ pg_dump -h 192.168.211.148 -p 5432 -Fc -n myschema -f /tmp/schema_my.custom
> Password:
> pg_dump: [archiver (db)] query failed: ERROR:  unrecognized configuration parameter "qreplace_function"
> pg_dump: [archiver (db)] query was: SHOW qreplace_function

That's an EDB internal configuration parameter, could it be you don't
have permissions or you are using community-edition pg_dump against
EDB?
<https://www.enterprisedb.com/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/11/EDB_P...;





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: Backup issue
  2019-09-05 10:32 Backup issue mallikarjun t <mallit333@gmail.com>
  2019-09-05 11:39 ` Re: Backup issue Luca Ferrari <fluca1978@gmail.com>
@ 2019-09-05 11:49   ` mallikarjun t <mallit333@gmail.com>
  0 siblings, 0 replies; 6+ messages in thread

From: mallikarjun t @ 2019-09-05 11:49 UTC (permalink / raw)
  To: Luca Ferrari <fluca1978@gmail.com>; +Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>

Dear Members,


I am trying to take backup of postgreSQL Community and restore to EDB
Advanced Server.

Now I will get this error on EDB Advanced Server.

Please rectify the issue.

Regards,
Malli.

On Thu, Sep 5, 2019 at 5:10 PM Luca Ferrari <fluca1978@gmail.com> wrote:

> On Thu, Sep 5, 2019 at 12:59 PM mallikarjun t <mallit333@gmail.com> wrote:
> >
> > Dear All,
> >
> > I try to take remote backup and  restore to local EDB Advanced Server
> this error is coming, If any one knows this issue please clarify me?
> >
> > Please look into the error message:
> >
> > [postgres@localhost bin]$ pg_dump -h 192.168.211.148 -p 5432 -Fc -n
> myschema -f /tmp/schema_my.custom
> > Password:
> > pg_dump: [archiver (db)] query failed: ERROR:  unrecognized
> configuration parameter "qreplace_function"
> > pg_dump: [archiver (db)] query was: SHOW qreplace_function
>
> That's an EDB internal configuration parameter, could it be you don't
> have permissions or you are using community-edition pg_dump against
> EDB?
> <
> https://www.enterprisedb.com/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/11/EDB_P...
> >
>

^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~2019-09-05 11:49 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-09-17 07:49 Backup issue Marcin Giedz <marcin.giedz@eulerhermes.pl>
2005-09-17 16:31 ` Jeff Frost <jeff@frostconsultingllc.com>
2005-09-19 16:52 ` Scott Marlowe <smarlowe@g2switchworks.com>
2019-09-05 10:32 Backup issue mallikarjun t <mallit333@gmail.com>
2019-09-05 11:39 ` Luca Ferrari <fluca1978@gmail.com>
2019-09-05 11:49   ` mallikarjun t <mallit333@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox