High availability using heartbeat s/w across a WAN
Hey guys, im currently doing some research on implementing a high availability system across a WAN link and would like help on certain areas. This is a scaled down project so I might end up using router simulators like gns3, vyatta etc instead real hardware. Also it'll involve two webservers on each side on the WAN(actually both server's will be next to each other so it's more like a fake WAN connection).
First, from peoples exprience, what are good choices of WAN connections (frame relay, leased lines etc) for such a system since failover is mostly dependent on the heartbeat monitor?
Second, is it even possible to transmit heartbeats across the WAN. I'm sure latency will be a concern but like I said this is scaled down and is for testing..
From read linux-ha.org's tutorials, I found that most setups are on same LAN and a serial(RS232) connection is used between the servers/machines.
In precis, I want to be able to achieve failover across a "fake WAN" (if you like).
Any responses or even pointers will be appreciated
|diff -u: What's New in Kernel Development||Sep 04, 2015|
|Android Candy: Copay—the Next-Generation Bitcoin Wallet||Sep 03, 2015|
|The True Internet of Things||Sep 02, 2015|
|September 2015 Issue of Linux Journal: HOW-TOs||Sep 01, 2015|
|September 2015 Video Preview||Sep 01, 2015|
|Using tshark to Watch and Inspect Network Traffic||Aug 31, 2015|
- diff -u: What's New in Kernel Development
- Using tshark to Watch and Inspect Network Traffic
- Problems with Ubuntu's Software Center and How Canonical Plans to Fix Them
- September 2015 Issue of Linux Journal: HOW-TOs
- Concerning Containers' Connections: on Docker Networking
- The True Internet of Things
- Android Candy: Copay—the Next-Generation Bitcoin Wallet
- Firefox Security Exploit Targets Linux Users and Web Developers
- Where's That Pesky Hidden Word?
- A Project to Guarantee Better Security for Open-Source Projects