pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Naomi Walker <nwalker@eldocomp.com>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Steve Burrows <steve@jla.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Backing up large databases
Date: Wed, 3 May 2006 09:58:32 -0700
Message-ID: <4458E138.6010904@eldocomp.com> (raw)

Simon Riggs wrote:
> On Fri, 2006-04-28 at 15:57 +0000, Steve Burrows wrote:
>> I am struggling to find an acceptable way of backing up a PostgreSQL
>> 7.4 database. 

Depending on your OS and hardware setup, you may have other options,
such as Veritas snapshotting.  It is expensive, but saves time.
>>
>> The database is quite large, currently it occupies about 180GB,
>> divided into two elements, a set of active tables and a set of archive
>> tables which are only used for insertions. 
>>
>> I ran pg_dump -Fc recently, it took 23.5 hours to run, and output a
>> single file of 126GB. Obviously as the database continues to grow it
>> will soon be so large that it cannot be pg_dumped within a day.
>> Running rsync to do a complete fresh copy of the pgsql file structure
>> took 4 hours, but later that day running another iteration of rsync
>> (which should have only copied changed files) took 3 hours, and I
>> cannot afford to have the db down that long.
>>
>> Anybody with any ideas? 
> 
> You need not backup the whole database in one go.
> 
> You can copy only changed data out of the tables using your knowledge of
> the mail store. That way you'll not need to have such a long running
> backup and it won't be so large either. You can then reassemble the
> pieces later into a new table in case of recovery.
> 


-- 
----------------------------------------------------------------------------
Naomi Walker                          Chief Information Officer
Eldorado Computing, Inc.              nwalker@eldocomp.com 602-604-3100
----------------------------------------------------------------------------
What lies behind us and what lies before us are tiny matters compared to
what lies within us.     - William Morrow
----------------------------------------------------------------------------

-- CONFIDENTIALITY NOTICE --

Information transmitted by thisĀ e-mail is proprietary to MphasiS and/or its Customers and is intended for use only by the individual or entity to which it is addressed, and may contain information that isĀ privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please notify us immediately at mailmaster@mphasis.com and delete this mail from your records.



view thread (10+ messages)  latest in thread

Message-ID: <4458E138.6010904@eldocomp.com>
Permalink:  ../4458E138.6010904@eldocomp.com/
Also on:    postgresql.org/message-id/4458E138.6010904@eldocomp.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: nwalker@eldocomp.com, simon@2ndquadrant.com, steve@jla.com
  Subject: Re: Backing up large databases
  In-Reply-To: <4458E138.6010904@eldocomp.com>
  References: <4458E138.6010904@eldocomp.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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