You can configure your load-balancers to have sticky sessions, or route traffic however you like. The only problem is price, and is it overkill for this situation. Your IP change is the cheapest and simplest. It will also have a period of downtime until you can get to the server to make the switch. Also, you want to configure your first machine to _not_ come up and grab the prod IP address. So, just some logic that would:
1. run a hearbeat from the backup server which checks the health of the prod server 2. If the prod server is unavailable: configure a NIC with the prod IP, and bring it up. 3. on the prod server, don't bring up the prod IP. Just setup multiple IPs on a single nic, and make the prod IP the secondary on both boxes: http://www.linuxhomenetworking.com/wiki/index.php/Quick_HOWTO_:_Ch03_:_Linux_Networking#Multiple_IP_Addresses_on_a_Single_NIC good luck, speeves On Mon, Sep 14, 2009 at 12:19 PM, Brian Dumbledore <[email protected]>wrote: > > >Have had really good luck with Coyote Point load balance hardware. Set up > >2 (or more, we had 5) servers running the same apps and then the LB in > >front to guide traffic. We used to use client vars (instead of session > >vars) to manage user-to-app connections that were seamless even across > >server switches. > > Thanks for the tip. Quick q, does the LB also support failover? My concern > is not loadbalancing, I want only one srever taking all traffic at any given > time, I just want the second server to take over when the main server fails. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:326275 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
