Fail over replacement software-My only option was to create a process made up of 3 scripts that fully simulate what heartbeatd and failoverd provided on the previous systems. They check for constant availability and monitor services. When issues are detected they try and repair the issue, then fail over if not successful. Right I am using this with Two servers that do not share the same file pool. They nightly sync so if a fail over occurs, the data is from the night before until we can bring the main server up and sync it.
While mourning the loss of of High Availability built-in, I have the need to do exactly what you've achieved. Would it be too much to ask you to share your scripts with me (obviously munge the sensitive stuff)
Best regards - Anton
A sad day indeed, but the need is diminishing as well. I can wrap up the scripts but in reality they are quite custom even excuding the sensetive stuff. Do you have any Applescript experience? Also what services are you looking to fail over? Please let me know and I will do what I can to help you.
I sincerely appreciate your offer.
As for Applescript experience.. some, but I wouldn't call it my major. However, I'm totally comfortable with the idea of 'rolling my sleeves up & getting stuck in'.. Fortunately (for me) Applescript is easy to read/understand, being mostly plain English.
At this time we are only talking web services and MySQL, but I have a sneaky suspicion that we are likely to see significant feature creep.. so, ideally, I'd love to be able to clone the entire machine, soup to nuts.