X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 963BE3A6086 for ; Tue, 7 Dec 2004 03:55:09 +0000 (GMT) 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 96146-10 for ; Tue, 7 Dec 2004 03:55:01 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id EEDFB3A610A for ; Tue, 7 Dec 2004 03:54:33 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id iB73sN4E097925 for ; Tue, 7 Dec 2004 03:54:24 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id iB73o0jD096750 for pgsql-admin@postgresql.org; Tue, 7 Dec 2004 03:50:00 GMT (envelope-from news) From: Christopher Browne X-Newsgroups: pgsql.admin Subject: Re: Need Help in Taking Backups Date: Mon, 06 Dec 2004 22:25:02 -0500 Organization: cbbrowne Computing Inc Lines: 21 Message-ID: References: <674d1f8a041206062862d3480a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:nL4/q7zRnloYFEuiwnHuDn4ENfk= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200412/52 X-Sequence-Number: 15638 In the last exciting episode, gourish@gmail.com (Gourish Singbal) wrote: > Whats the Best plan to take Backups for Postgres 7.4.5 database > considering the database is 24/7 and transaction based. Well, you can take a pg_dump to get the state of the system at a point in time. That's very easy, although it's anyone's guess whether that's an acceptable answer or not. But you really need to specify your 'disaster modelling' and recovery requirements in _much_ greater detail. It may be that in order to keep recovery time down, you'll need to use a replication system such as Slony-I to give you a "hot backup" that's sitting just a few transactions behind. Or perhaps the answer will be to wait for "sophistication" for 8.0 and record transaction logs in order to use PITR. -- let name="cbbrowne" and tld="gmail.com" in name ^ "@" ^ tld;; http://linuxfinances.info/info/postgresql.html "We defeated the enemy with teamwork and the hammer of not bickering." -- The Shoveller, Mystery Men