Hi Ariz,
I agree that simple failover configurations are "so yesterday". Having
said that, they seem to remain the lowest-hanging-fruit solution for
those needing to eliminate a single point of failure without the time
and budget to extend this to a proper load-balanced configuration. What
are you
> Implementing a Failover cluster to run a redundant website infra
> sounds lazy to me. You should consider implementing a Load-Balanced
> Cluster instead. Start by looking into the following tools:
> - Load Balancer: BigIP or simply use Apache HTTPD's mod_proxy_balancer[2]
> - Replication of Web A
Deja vu
Yup. Willing to help here. Email mo na lang ako kung ano kailangan
mong tulong :)
On Fri, Dec 14, 2012 at 2:03 PM, claive alvin Acedilla
wrote:
> Ramil, this is very good by DepEd because there are no translation efforts
> in the Philippines.
> In the Middle East, everything in English m
Hi Bong,
Your question reminded me of my projects and PLUG presentations[1]
back in 2002 -2005. I'm just surprised to hear that people are still
recommending the use of Heartbeat/DRBD for implementing a redundant
website infrastructure. Back then, DRBD isn't fast enough for our
application and mad
Hi Bong,
I agree with Christian in that the DRBD (RAID-1 over LAN) + Heartbeat
would be the top-of-mind suggestion for your requirement. Applied
somewhat literally, you end up with the unfortunate situation of having
one server sitting idly, possibly even failing without anyone noticing,
until one
Hi Bong,
I usually do DRBD+Heartbeat for HA setup. DRBD for realtime sync (aka network
RAID1) and Heartbeat for communication between the two servers.
http://www.linux-ha.org/wiki/Heartbeat
http://www.drbd.org/
Hope this helps.
Regards,
- CF
On Mar 1, 2013, at 2:48 PM, Caloocan Gangsta wrote
6 matches
Mail list logo
