X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 49837D9382 for ; Mon, 19 Sep 2005 13:52:57 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 24158-03 for ; Mon, 19 Sep 2005 16:52:44 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id 16483D93C0 for ; Mon, 19 Sep 2005 13:52:44 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 19 Sep 2005 11:52:44 -0500 Subject: Re: Backup issue From: Scott Marlowe To: Marcin Giedz Cc: pgsql-admin@postgresql.org In-Reply-To: <432BCAA0.6020902@eulerhermes.pl> References: <432BCAA0.6020902@eulerhermes.pl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1127148764.30120.102.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Mon, 19 Sep 2005 11:52:44 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 required=5 tests=[AWL=0.005] X-Spam-Level: X-Archive-Number: 200509/199 X-Sequence-Number: 18936 On Sat, 2005-09-17 at 02:49, Marcin Giedz wrote: > Hello... > > This is what I have now: postgresql 8.0.1 - database weights about 60GB > and increases about 2GB per week. Nowadays I do backup every day - > according to simple procedure (pg_start_backup:rsync > data:pg_stop_backup:save wals produced during backup). On 1Gb internal > network it usually takes me about 1h to perform this procedure. > > But what if my database has ~200GB and more (I know this is a future > :D)? From my point of view it won't be good idea to copy entire database > to backup array. I would like to here opinions about this case - what do > you propose? Maybe some of you already do something like this? I'd look at using PITR replication, with a monthly or so fresh, whole backup instead of a whole backup every day.