From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Nicos Panayides <nicos(at)magneta(dot)com(dot)cy> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Off-site storage for PITR logs |
Date: | 2010-03-14 08:50:12 |
Message-ID: | 1268556612.3825.5025.camel@ebony |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, 2010-03-12 at 18:40 +0200, Nicos Panayides wrote:
> I am planning an off-site backup solution for a fairly busy
> (mostly-write) 8.3 database. The database is currently about 200GB in
> size. I though about using log shipping and cold standby since it's easy
> in terms of administration and also offers point in time recovery.
>
> The database generates about 3 PITR log files per minute. If my
> calculations are correct the sites need to be connected with a 7MBit
> connection and the logs will need about 68GB of storage per day!
>
> Does anyone have any suggestions on how to significantly reduce the
> volume of log files or recommend another off-site backup solution that
> would require less bandwidth and storage?
Consider turning off full_page_writes which will permanently minimise
the amount of WAL traffic, as well as being an integrated and
fully-supported option with Postgres. You will need additional
non-volatile cache on your disks to ensure that is a safe option, though
that will yield performance advantages also.
--
Simon Riggs www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Axel Rau | 2010-03-14 16:18:51 | Re: remote pg_dump hangs always at same table |
Previous Message | Axel Rau | 2010-03-13 22:34:16 | Re: remote pg_dump hangs always at same table |