<div>
I have decided something similar to your concept. we have on active and more that one standby. &nbsp;when active dies, any one of the standby becomes active. we have to have a common place to share the info for which we have DB server. &nbsp;<br />
<br />
I am not very much experienced in this area. so I just want to make sure that This idea is ok.<br />
<br />
I am definitely intested in knowing experiences about general failover and heart beats. &nbsp;You can email me or post here as comment. <br />
<br />
thank you for your answer.<br />
<br />

</div>


I have decided something similar to your concept. we have on active and more that one standby.  when active dies, any one of the standby becomes active. we have to have a common place to share the info for which we have DB server.  

I am not very much experienced in this area. so I just want to make sure that This idea is ok.

I am definitely intested in knowing experiences about general failover and heart beats.  You can email me or post here as comment.

thank you for your answer.



<div>
<div class="content wysiwyg-content">
I will have to work on developing a failover software which<br />
identifies that a active system is down and statdby should<br />
become active. &nbsp;<br />
I think of a tcp/ip connection and send messages at a regular interval and &nbsp;if missed at one<br />
system, it could be either system down/ connection broke because of interface down. &nbsp;how do we make sure that the interface is down in the local system or in other standby system.?<br />
<br />
Is there any algorithm to acheive this failover? &nbsp;Is there any other way for finding out other that TCP/IP messaging?<br />
<br />
I would really appreciate if any one suggest me some ideas.<br />
thanks<br />
ramalaks@peri.com<br />

</div>
</div>


I will have to work on developing a failover software which
identifies that a active system is down and statdby should
become active.  
I think of a tcp/ip connection and send messages at a regular interval and  if missed at one
system, it could be either system down/ connection broke because of interface down.  how do we make sure that the interface is down in the local system or in other standby system.?

Is there any algorithm to acheive this failover?  Is there any other way for finding out other that TCP/IP messaging?

I would really appreciate if any one suggest me some ideas.
thanks
ramalaks@peri.com


failover software

Unix is a multitasking, multi-user computer operating system originally developed in 1969 at Bell Labs. Today, it is a modern OS with many commercial flavors and licensees, including FreeBSD, Hewlett-Packard’s UX, IBM AIX and Apple Mac OS-X. Apart from its command-line interface, most UNIX variations support the standardized X Window System for GUIs, with the exception of the Mac OS, which uses a proprietary system.