pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Stephen Frost <sfrost@snowman.net>
To: Mike C <smith.not.western@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: WAL and pg_dump
Date: Fri, 23 Dec 2005 09:48:31 +0000
Message-ID: <1135331311.2964.559.camel@localhost.localdomain> (raw)
In-Reply-To: <bd0eabd0512221734v3d474ba1o8a8b9bfd3ebbdf24@mail.gmail.com>
References: <bd0eabd0512121418h4c39a3e6mc71947264e18656f@mail.gmail.com>
	<1135208028.2964.329.camel@localhost.localdomain>
	<bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com>
	<1135289852.2964.542.camel@localhost.localdomain>
	<bd0eabd0512221734v3d474ba1o8a8b9bfd3ebbdf24@mail.gmail.com>

On Fri, 2005-12-23 at 14:34 +1300, Mike C wrote:

>         Is space your limiting factor?
> 
> Yes, space is our limiting factor. A pg_dump archive format backup
> takes about 40mins for 25GB. A restore IIRC takes about 2 hours.
> However the size of the database is expected to grow to about 120 GB
> within a few months and by the end of 2006 over 400 GB. The current
> capacity of our DS 400 SAN is 600 GB. at 400GB my only backup option
> with the existing hardware is pg_dump. However I suspect now that I
> really should be looking at additional hardware.

You should be looking at backup designs that do not require you to dump
the complete database each time. That way your backup and recovery times
increase linearly.

Best Regards, Simon Riggs




view thread (12+ messages)  latest in thread

Message-ID: <1135331311.2964.559.camel@localhost.localdomain>
Permalink:  ../1135331311.2964.559.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1135331311.2964.559.camel@localhost.localdomain

 · 

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: simon@2ndquadrant.com, sfrost@snowman.net, smith.not.western@gmail.com
  Subject: Re: WAL and pg_dump
  In-Reply-To: <1135331311.2964.559.camel@localhost.localdomain>
  References: <bd0eabd0512121418h4c39a3e6mc71947264e18656f@mail.gmail.com> <1135208028.2964.329.camel@localhost.localdomain> <bd0eabd0512221309r5bcb41e2s69e9a7fdc8cb9edb@mail.gmail.com> <1135289852.2964.542.camel@localhost.localdomain> <bd0eabd0512221734v3d474ba1o8a8b9bfd3ebbdf24@mail.gmail.com> <1135331311.2964.559.camel@localhost.localdomain>

* 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