Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 5997A634863 for ; Tue, 17 Mar 2009 02:26:26 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 79845-07 for ; Tue, 17 Mar 2009 02:26:22 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mail.postgresql.org (Postfix) with ESMTP id 47CED633107 for ; Tue, 17 Mar 2009 02:26:24 -0300 (ADT) Received: by qw-out-2122.google.com with SMTP id 8so763090qwh.61 for ; Mon, 16 Mar 2009 22:26:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=tG8fr5+Uuq0Bbe8DUw2BiqbqDwsQPgk/cfBFBq+NiiY=; b=RgLCwSmHSHPg8mJRd2vi7Ga0J6hKzSqigP8vvg+0CN65UEpJNVWlsr6uOCc67W211o jULsqLZ0UURghpGdzQLOW14JimzfcRbHLMe2qICFvh8EsM3R58ssqAa7z4lQbggLxd73 aQBMhhkT2MVawhzgsjn9eViYiN/sSRJ2dWhP8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=vaKClXaZ0oWxWs4eDRC5ejoaUchAYExavYTxWdER5EdQcKuhFvH0y9DF+BelAH5D3x S6Cv2HZRm2wXRBbhrAsblFCenKWbHO4EKmJ7rlrPv6RXDq+JSEy/UqAo9lbbCHI7KAaX fCKwgnoSwDrOCjBo9OlyH6VhXBDnfY4X/7DN8= MIME-Version: 1.0 Received: by 10.224.36.202 with SMTP id u10mr7088761qad.122.1237267583296; Mon, 16 Mar 2009 22:26:23 -0700 (PDT) In-Reply-To: <5FFF8E9361C5D84EBBAF70C1931CDDE303FD90CA@BTCMVEXC1-PRD.hq.netapp.com> References: <5FFF8E9361C5D84EBBAF70C1931CDDE303D6C954@BTCMVEXC1-PRD.hq.netapp.com> <49BEB50C.60708@kaltenbrunner.cc> <5FFF8E9361C5D84EBBAF70C1931CDDE303FD90CA@BTCMVEXC1-PRD.hq.netapp.com> Date: Mon, 16 Mar 2009 23:26:23 -0600 Message-ID: Subject: Re: deployment query From: Scott Marlowe To: "Nagalingam, Karthikeyan" Cc: Stefan Kaltenbrunner , pgsql-general@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200903/636 X-Sequence-Number: 145222 On Mon, Mar 16, 2009 at 11:15 PM, Nagalingam, Karthikeyan wrote: > Thanks Stefan for all your answers. My last question is "What is the > Mostly used Disaster Recovery Solution for Postgresql in storage > environment." We use two methods of backup to keep the database afloat amid things going horribly wrong. We have 1 or more slony backup dbs that allow for failover and load balancing. We have offsite pg_dump backups which are transferred via ssh to an offsite server in case of catastrophic failure in the data center (like a huge power surge) that kills both servers. We routinely restore backup sets or parts of them for various testing scenarios.