From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Mark Steben <msteben(at)autorevenue(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_xlog volume question |
Date: | 2009-02-06 18:12:43 |
Message-ID: | 1233943963.15061.16.camel@jd-laptop.pragmaticzealot.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, 2009-02-06 at 12:52 -0500, Mark Steben wrote:
> Hello listers,
>
> I'm designing a PITR backup / recovery scenario where I'm log-shipping to
> another location and recovering using a tar backup and log roll forward.
> The plan is to save a week's worth of logs and restore nightly using the
> accumulated logs to that point. A daily full backup is too
> expensive and time consuming - it takes over 36 hours to transport it over
> the network to the recovery site. So we're going with the weekly backup and
> saving the weeks worth of logs.
>
> As you well know, I will require a LOT of storage for the xlogs. I'm
> currently creating about 2GB of logs every hour. Is there a config
> parameter to reduce the amount that Xlog takes up?
No. I would suggest using pg_standby or pitrtools (which requires
pg_standby) to manage this. I would also suggest just restoring as the
logs become available. If you can't process 2G in an hour over the
network do it at night.
Joshua D. Drake
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-02-06 18:26:11 | Re: pg_xlog volume question |
Previous Message | Mark Steben | 2009-02-06 17:52:56 | pg_xlog volume question |