I didn't really know where to post this question, but to the best of my knowledge, I believe this is the right place.
I've been a webserver administrator for 5 years, I've always had two servers, one for production and a replica for backup. I've rarely needed the backup server but I have used it for my production server upgrades and system maintenance.
Now, I've been thinking for a while of the best way to setup an environment where both servers are working, they share one database, one source of files, and a shared log file.
We have another system that is basically a content management switch that has three servers attached to it, but the database is oracle and it is on a different server. The content is replicated manually, and most content is on the database.
In my case, my static content is always changing, and my dynamic content is too. Has anyone done a fault tolerent (software based) solution? Or some sort of fail-safe implementation with open source software?
My dreams had awakened when MySQL release a cluster in 4.1, but its still in Aplha, when this becomes stable, I could install the cluster on the two servers, setup a proxy on both that redirect to both servers. So when my main server is up, its the proxy that is serving the pages, but getting requests from both servers, and vice versa.
I also thought of sharing the static content by running rsync to update any change....
But I'd love to know if someone has done something that works... even ideas would do...
Sorry for the long question... But its one of those things that you'll never rest until you know :)