Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 328869FB6E7 for ; Thu, 31 May 2007 02:30:36 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 83341-07 for ; Thu, 31 May 2007 02:30:22 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.234]) by postgresql.org (Postfix) with ESMTP id D9CA09FB4F9 for ; Thu, 31 May 2007 02:30:22 -0300 (ADT) Received: by wr-out-0506.google.com with SMTP id 68so47041wri for ; Wed, 30 May 2007 22:30:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Xax9i+Ch1iEdLK3JLZGepgqjer2F0I5Eam+ClexSBTLfuFhoJvWAz6qA2rUrHuqriKHCWJWVGG3RwAekSI7UyLmGN5i+RMoFvT/24IOsHcsqATvwSxVSnC83B8ECeJjJ8Go5jsuM3XR/lj3Sb/ZtTUJ04Y4qhyiAHouhblOXzGU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=rfSTfTE0S2xheYS1Zrw1MF0+loGG6A5RDsRbskVq+GGxrtpbwgC02Z9GziuNkVS8VuiVUznhPBqPqN0Z5ljl9TDRXlJeCKPamciDyw6sREv1j64aQ/6Gea0o2TB2pEm2tRZ1Af1bdUvvrgF+BPbG5Sp+npAJfaVMjP1Xr/PlJm4= Received: by 10.82.138.6 with SMTP id l6mr15259182bud.1180589420853; Wed, 30 May 2007 22:30:20 -0700 (PDT) Received: by 10.82.146.20 with HTTP; Wed, 30 May 2007 22:30:20 -0700 (PDT) Message-ID: <1c66bda80705302230p7ed40acam8f39e3fea2a00ac6@mail.gmail.com> Date: Thu, 31 May 2007 17:30:20 +1200 From: adey To: "Fernando Ike de Oliveira" Subject: Re: High Avaliable in the PostgreSQL. Cc: pgsql-admin@postgresql.org In-Reply-To: <20070530164208.2657ee91@localhost> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_13046_21046523.1180589420818" References: <20070530164208.2657ee91@localhost> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/327 X-Sequence-Number: 25647 ------=_Part_13046_21046523.1180589420818 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline HP was providing CA (Continuous Access) software that was claimed to provide WAN SAN replication by repeating IO in exactly the sequence it was generated on the master, to the slave. SO while there was a delay, updates on the slave would be sequentially intact, providing a good level of integrity for database rollback on the slave in the event of recovery on the slave / DR system. I'm not sure this would be sufficient for 99.9% uptime though, as there would be some startup requirements on the slave. On 5/31/07, Fernando Ike de Oliveira wrote: > > Hi, > > > I need solution to PostgreSQL for High Available, originally > was 99,7% but considering the current necessities, change percentual > to 99,99%. I think in solution probability pgpool-2 or Heartbeat + > GFS. The PostgreSQL servers will be in different physical places. > > Suggestions? > > > > Kind Regards, > -- > Fernando Ike > http://www.midstorm.org/~fike/weblog > > ---------------------------(end of broadcast)--------------------------- > TIP 3: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faq > ------=_Part_13046_21046523.1180589420818 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline HP was providing CA (Continuous Access) software that was claimed to provide WAN SAN replication by repeating IO in exactly the sequence it was generated on the master, to the slave. SO while there was a delay, updates on the slave would be sequentially intact, providing a good level of integrity for database rollback on the slave in the event of recovery on the slave / DR system. I'm not sure this would be sufficient for 99.9% uptime though, as there would be some startup requirements on the slave.

On 5/31/07, Fernando Ike de Oliveira <fike@midstorm.org> wrote:
Hi,


       I need solution to PostgreSQL for High Available, originally
was 99,7% but considering the current necessities, change percentual
to 99,99%. I think in solution probability  pgpool-2 or Heartbeat +
GFS. The PostgreSQL servers will be in different physical places.

       Suggestions?



Kind Regards,
--
Fernando Ike
http://www.midstorm.org/~fike/weblog

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

              http://www.postgresql.org/docs/faq

------=_Part_13046_21046523.1180589420818--