Discussion Locked

Routing traffic to a backup webserver

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We run several websites using our own webservers and leased line at our main office. We've recently opened a second office with a second leased line and would like to locate our backup webserver there. Is it possible to configure our setup so thatif our main webserver is unavailable traffic is automatically routed to our backup webserver, and if so, how? I've spoken to our ISP and they can't offer a solution.

5 replies

by fgarber

There are several options to handle your situation. The "free" one is by far the least desirable. If you host your own dns server you can set up a round robin where every other hit to the web site goes to the backup server. However if one server is down then every other hit will get a "server not available" page. There are some hardware solutions on the market that will keep track of the server farm and if one is down will route traffic to the others but they are fairly expensive. It depends how much your business requires up time of the web site whether it is worth the expense. I have details about the hardware solution at my office. If you want I can email them to you Tuesday.

by kevin anderson

I'm a bit of a cheapskate, so generally, I'll look for cheap solutions for things, and if they work, then that's great.

How about...

Set up a Linux Server as a router. It doesn't need to be much of a PC, a p100 would easily do.

Have the Linux box set up as the address of your web server. I'll call the Linux box 10.10.10.10. Your Primary Web Server can be 10.10.10.20 (same network). Your newer remote web server can be 10.20.10.10 (Different Network).

Internet DNS will show www.you.com pointing to 10.10.10.10.

10.10.10.10 will port forward TCP on Port 80 to 10.10.10.20.

Every Minuite, the Linux box will Ping 10.10.10.10. If it recieves a reply, it will stay the same. If there is no reply, it will remove the port forwarding to 10.10.10.20, and add a port forwarding entry pointing to 10.20.10.10. At this point, I would continue to ping 10.10.10.20. When I again recieved a response, I would remove the forwarding to 10.20.10.10, and reforward it to 10.10.10.20.Then the initial ping check would start.

This isn't exactly an enterprise solution, but it'll cover you in case of line failures, and complete server crashes, power outages (affecting the server, but not the Linux box), even upgrades.

Keep in mind that if the web server crashes, but the Server itself continues to run, you will recieve a reply to the ping, and things will not switch over.

If your company NEEDS this website up, 100% 24/7, then budget and buy yourself a better solution. If it's just a preference, then this should meet your needs.

Kev.

This discussion is closed to new replies.