|
Roberto,
Thank you for the response.
>Let's take another approach. Can you tell me how your requirements for
>knowing when the first system is not reachable anymore and how much the
>maximal system downtime and failover to the new system can be? I think of
>writing a little (100 lines of code or so) shell script to flush the
>table in case of a down status, flush the original table and set up the
>new one. Can be done really fast, believe me. It's cheating but works
>and the customer doesn't know that.
Very well. Basically we need to know within a reasonable time frame, say 5
minutes at the outside, that the servers is down via email/pager/some other
notification. Failover should obviously be performed during this time
frame. Of course 5 minutes is a "LONG" time in the land of 9x5 guarantee's,
but lets just say that is the Maximum allowed time.
What you are proposing I had already been thinking of trying. Although I
was only going to write the script that would flush the table and create a
redirect to the secondary server. I thought of using heartbeat to check the
status of the real servers, and then should RS1 fail, then it would fun an
"alert"/routing script that would redirect requests to the remote FOS. Do
you think this would work in the situation? Can you think of any other
solutions that might be plausible?
Thank you
Ben Shellrude
Sr. Network Analyst
|
