Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have an application server running on Ubuntu that is accessed via a public URL that is widely known and used by all of my users to get to our service. I have a second, twin server (with its own, unique TCP/IP address, obviously) that is a hot spare for the production server.
What is the best way to fail over from the main server to the hot spare? I cannot wait for DNS servers around the world to update their caches. Should I bring down the main server (which is probably down anyway, or why would I be failing over to the spare), reconfigure the spare with the TCP/IP address on the broken main server, and then reboot the spare?
A load balancer is probably in the future for this site. At the moment, it does not have one. Online production server is backed up daily and these backups are applied to the standby server. No real-time synch at the moment.
Have a look at Linux-HA or LVS. In a nutshell, your DNS records resolve to a Floating IP/Virtual IP. Heartbeat will determine which server is active thus, getting the Virtual IP. This failover should be automatic.
I agree that the desired long-term solution is a high availability cluster configuration. At the moment I am just trying to set up a manual fail-over between two identical application servers.
I agree that the desired long-term solution is a high availability cluster configuration. At the moment I am just trying to set up a manual fail-over between two identical application servers.
what do you use for a firewall? you could use destination nat
can you build another server that has two nics? you could easily make a linux router and you could use iptables with dnat and change the dnat ip based on which host you want to use manually and use masquerading so the external IP never changes
what ports and protocols does the app require? I could give you an example of what I'm talking about
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.