11 Replies Latest reply: Oct 14, 2013 5:31 PM by coocooforcocoapuffs
kevin209 Level 1 Level 1 (0 points)

Hi --


Is there a way to set up IP Failover in OS X Lion Server.  I see instructions for previous server editions, but can't locate any for the Lion release.  I tried to edit the hostconfig files like listed for previous releases and this did not work.



Mac mini, Mac OS X (10.7), Lion Server
  • nei0angei0 Level 1 Level 1 (5 points)

    Nope sorry sir. It has been removed!!!!!!!!!!!!!!

  • nei0angei0 Level 1 Level 1 (5 points)

    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.

  • lingem Level 1 Level 1 (0 points)

    Can you share those scripts, or are they publicly available?

  • nei0angei0 Level 1 Level 1 (5 points)

    Sure if there is still a need I will be publishing my solution soon. I am permantely moving away from OSX for any server related activities.

  • coocooforcocoapuffs Level 3 Level 3 (845 points)

    Sure would love to see a documented solution to this... I have two Lion-based mac mini servers to play with, and that actually need this functionality. Best of luck!

  • lingem Level 1 Level 1 (0 points)

    Yes, there is still need for this. Would be great if you shared information about the process and source code/scripts.

  • nei0angei0 Level 1 Level 1 (5 points)

    What is everyone looking to monitor specifically for fail over? The ones I designed specifically were for a file share server. If either SMB or AFP was down, it would shut the server off and the back up server would then kick on its services and take the IP. If you had other things like a web server on the same box, it would go down also. There is a way to separate (where there is a will there is a way) but I would need to look into it.


    So everyone, please tell me what your heart's desires are.


    Thank you

  • coocooforcocoapuffs Level 3 Level 3 (845 points)

    I would just use for web server services. The most common application here would be when one mac mini server went down, that the other mac mini server would kick in. Thx!

  • John Lockwood Level 5 Level 5 (6,700 points)

    If you made your scripts modular it should be possible to make it fit more configurations. First would be the need for a heartbeat monitor (and server). Then would be a script to take over the IP, and then would be a script to start (or restart) a service e.g. file-services (AFP and/or SMB), web, email, calendar.


    The hearbeat monitor script could have lines calling scripts which would start specific service(s) and if you comment out or uncomment a line it would start the service.


    For the benefit of everyone else, some services could be managed by a DNS loadbalancer and the use of VIPs (virtual IP addresses). However OpenDirectory and PasswordServer and DHCP would not be possible this way, so these services as used to be possible with Snow Leopard Server would need an IP-failover approach like discussed here.

  • nei0angei0 Level 1 Level 1 (5 points)

    Ok, I am almost done cleaning up the code and making it more universal. I had to go back to a few versions, right now it doesn't do heartbeat in the traditional sense (a daemon waiting for input on one server, and a daemon outputting data on another) rather it is just two different ping scripts with timeout thresholds that control the flow of actions. I am not sure what avenue I should use to share the code base. Any suggstions?

  • coocooforcocoapuffs Level 3 Level 3 (845 points)

    I have no expierece publishing, but this site seems good to download stuff:


    best of luck with that!