For those of us that do not recall the plan details, if you're looking
for hotswap on sipxconfig, there's quite a bit to mirror to get right
and honestly, no real need because it's not in critical path.  Are you
looking to have hotswap of user portal portion of sipXconfig? That
makes sense, If so those files are not nec., but all of postgres is,
you have that setup already?


On Wed, Sep 22, 2010 at 11:36 AM, Krisztian Ganyai
<[email protected]> wrote:
> Hi,
>
> You might remember, that some months ago I was drafting an HA plan with
> 3 nodes trying to solve the sipxconfig and mediaservices SPOF.
>
> The basic idea was to set up node 1 on site A and node 2 + 3 on site B.
> Node 1(config+media services) and node 2(redundant proxy) form a
> traditional HA SIP cluster. When node 1 fails, the node 3 on site B
> comes up and takes over IP address and role of node 1 and vice versa.
> For this, some file/DB replication has to be in place and additionally
> some mechanism to make sure the system is always in a valid state. The
> system is supposed to stay fully functional with any 2 of the nodes
> running at a given time(excluding failover time).
>
> In the recent weeks I had some time to work on this and managed to put
> together the file replication and IP failover part, which is in a quite
> good shape now. Last week I started adding the control of the sipXecs
> "on top of it" and there is some progress as well. When creating a user
> on node 1 and pulling network cable out of it, shortly after the node 3
> comes up and the newly created user is visible there.
>
> Where I'm kind of stuck at the moment is the /var/sipxdata directory.
> Could someone please tell me which directories are _NOT_ necessary in it
> from replication point of view? I suppose /var/sipxdata/tmp/ is not and
> I'm not entirely sure about /var/sipxdata/process-state/. Are there any
> others, which could be excluded?
>
> Thanks in advance,
> Chris
>
> PS: In case of questions, please don't hesitate to ask.
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to