DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding;
	b=h+HOQKN2ezOl5MZQPuC58U6hyTHcnVhUsXvEQqs1ApAdVWQLVhlypVogTZ3F25YLM7Va/pgdcWtts1jJFC14Sk+GNfXdpl6YHu/8Va2nC9xffdR5/aqyPpvRTBdYLmjowWoVq5A8Z0barzQca2KquFbyzvxpB1TwCgX+ISoiLrg=
Message-ID: <47E81BA9.303@gmail.com>
Date: Mon, 24 Mar 2008 14:22:49 -0700
From: paul rivers <rivers.paul@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: "Matthew T. O'Connor" <matthew@zeut.net>
CC: Steve Poe <steve.poe@gmail.com>, pgsql-performance@postgresql.org
Subject: Re: Planning hot/live backups?
References: <721b21dc0803241323u73443060w3a1912d52714549b@mail.gmail.com>
	<47E8128E.1060600@zeut.net>
In-Reply-To: <47E8128E.1060600@zeut.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Matthew T. O'Connor wrote:
> Steve Poe wrote:
>> The owners of the animal hospital where I work at want to consider 
>> live/hot
>> backups through out the day so we're less likely to lose a whole
>> day of transaction.  We use Postgresql 8.0.15. We do 3AM
>> backups, using pg_dumpall, to a file when there is very little activity.
>
>
>
> You probably want to look into PITR, you can have a constant ongoing 
> backup of your data and never lose more than a few minutes of data.  
> The overhead isn't all the big especially if you are shipping the log 
> files to a separate server.
>
>

I'll second that.  PITR is IMHO the way to go, and I believe you'll be 
pleasantly surprised how easy it is to do.  As always, test your backup 
strategy by restoring.  Even better, make a point of periodically 
testing a restore of production backups to a non-production system.

Paul