From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | "Al-Salami, Adel" <saa(at)klinkhammer(dot)com> |
Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-cluster-hackers(at)postgresql(dot)org" <pgsql-cluster-hackers(at)postgresql(dot)org> |
Subject: | Re: Microsoft Cluster for Failsafe |
Date: | 2011-09-09 08:37:47 |
Message-ID: | CABUevEzDXDWKA54KaN0GbHtRPF0qjzMZ3Af3N26oUUUBUGK2gg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
On Fri, Sep 9, 2011 at 08:54, Al-Salami, Adel <saa(at)klinkhammer(dot)com> wrote:
> Thanks for the prompt response,
>
> Good to hear that, but really I cannot find a document how to configure Postgres as Failover on a 2 node MS cluster (one data store which could be owned by one node at a time and two Postgres Instances on both nodes one is active and the other is passive, just like oracle Failsafe on ms cluster), the available documentation is only mentioning the Replication and standby are the only choices for Postgres High availability and Clustering-Failover not.
You set it up like a "generic service" I think it's called in MSCS. In
a group along with the storage resource and the IP address. And make
sure you have all your postgresql data on that disk. How that's done
should be in the MS documentation.
This is not a PostgreSQL feature really, but one of MSCS, that's why
it's not included in the PostgreSQL documentation. What we have is at
http://www.postgresql.org/docs/9.0/static/different-replication-solutions.html,
under "shared disk failover" - that's the MSCS solution.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Fabricio Mota | 2011-09-10 01:43:31 | Re: Hi all! |
Previous Message | Al-Salami, Adel | 2011-09-09 06:54:45 | Re: Microsoft Cluster for Failsafe |