Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 9FCAA9FB283 for ; Wed, 17 Jan 2007 11:15:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 70739-08-2 for ; Wed, 17 Jan 2007 11:15:07 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from perth.mailnetwork.co.uk (perth.mailnetwork.co.uk [80.175.28.46]) by postgresql.org (Postfix) with ESMTP id F11A49FB254 for ; Wed, 17 Jan 2007 11:15:12 -0400 (AST) Received: from [213.146.139.35] (port=17243 helo=[172.21.18.250]) by perth.mailnetwork.co.uk with esmtpa (Exim 4.63) (envelope-from ) id 1H7CVJ-0001VH-7f; Wed, 17 Jan 2007 15:15:09 +0000 Message-ID: <45AE3D9A.7010908@mailnetwork.co.uk> Date: Wed, 17 Jan 2007 15:15:38 +0000 From: "Andy Shellam (Mailing Lists)" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Shoaib Mir CC: Yogvinder Singh , pgsql-admin@postgresql.org Subject: Re: Incremental Backup of a particular database References: <001201c73a3e$33bbaf70$0404a8c0@central.newgen.local> <45AE370B.2070805@mailnetwork.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/134 X-Sequence-Number: 24290 Shoaib Mir wrote: > Even with ver 8.1 you can use WAL archive backups (PITR) to implement > an incremental backup strategy. Yes, true, but it's harder with 8.1 as you always have to start from a base backup and roll WAL logs forward - without a custom script you cannot "wait" for new WAL logs to arrive and apply them on top of a base backup. There is a project in PgFoundry to allow for warm-standby in the 8.0 and 8.1 series, however this is reportedly built-in to 8.2 now. > > ------------- > Shoaib Mir > EnterpriseDB (www.enterprisedb.com ) > > On 1/17/07, *Andy Shellam (Mailing Lists)* > > wrote: > > I believe the option for a "warm standby" (which sounds like it is > what > you need) was made available in 8.2.0. > You'd have to look at the manual though, I haven't had time to > investigate, and I'm not sure whether it's cluster-wide, or > database-specific. > > > Yogvinder Singh wrote: > > Hi Ppl, > > > > I have Two PostgreSQL Database Servers. The situation is like this:- > > 1) On first database server ball the operations (i.e live > server) will > > be done. This server may contain n number of databases. > > > > 2) On the second database server, i want to keep one particular > > database (from the first database server ) and keep it updated > to the > > latest from the First Database Server. I just want to be able to > take > > some sort of incremental backup from the first server and restore it > > to the second server. > > > > Is this situation feasible. How can i take an incremental backup > of a > > particular database out of many databases? On which version this is > > supported? IF not supported, is there any alternative way to handle > > this situatio. > > > > Regards, > > Yogvinder Singh, > > Disclaimer :- This e-mail message > > including any attachment may contain confidential, proprietary or > > legally privileged information. It should not be used by who is not > > the original intended recipient. If you have erroneously > received this > > message, you are notified that you are strictly prohibited from > using, > > copying, altering or disclosing the content of this message. Please > > delete it immediately and notify the sender. Newgen Software > > Technologies Ltd and / or its subsidiary Companies accept no > > responsibility for loss or damage arising from the use of the > > information transmitted by this email including damage from > virus and > > further acknowledges that any views expressed in this message are > > those of the individual sender and no binding nature of the message > > shall be implied or assumed unless the sender does so expressly > with > > due authority of Newgen Software Technologies Ltd and / or its > > subsidiary Companies, as applicable. > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > > > !DSPAM:37,45ae3b61137103926781350!