Suggested setup for two server deployment

Hi all,

I'm in the process of bringing another server into the loop and using two dedicated machines to power vBulletin. I'd like a bit of input from those of you may be running with similar environments, which set up works best for you.

Two immediate alternatives I see are a shared web/database host running reads and a separate write database vs. completely separating web and database roles. Are you using a master/slave setup or all database on a separate box? What parameters helped you decide?

Thanks in advance!

Best wishes,
Paul

[TECK]

You REALLY need to separate the setup into 2 parts:
1. web server
2. db server

Don't even think about setting some sort of shared process.
Also, you need to strongly consider setting up a load balancer.
lighty will do the job greatly, toss ASAP Crapache... it was designed to ruin your server performance.

[woodysfj40]

one for web, one for db....

in the future, as you grow, you'll add a second web server and initiate load balancing of those two, with one db server in the background....

[EricGT]

Originally Posted by Paul

Hi all,

I'm in the process of bringing another server into the loop and using two dedicated machines to power vBulletin. I'd like a bit of input from those of you may be running with similar environments, which set up works best for you.

Two immediate alternatives I see are a shared web/database host running reads and a separate write database vs. completely separating web and database roles. Are you using a master/slave setup or all database on a separate box? What parameters helped you decide?

Thanks in advance!

Best wishes,
Paul

I have two very powerful servers that can each just barely run my site, if I turn off functions like the search feature. The front-end runs on one and the backend on the other, but each contains the data of the other, so if either box fails, the other will have everything needed to run the whole site (barely). vBulletin already contains the functionality to use a master and slave DB server and I rsync program and image files between the boxes. Redundancy is damned important. Eric

[lauxanh]

Originally Posted by TECK

You REALLY need to separate the setup into 2 parts:
1. web server
2. db server

Don't even think about setting some sort of shared process.
Also, you need to strongly consider setting up a load balancer.
lighty will do the job greatly, toss ASAP Crapache... it was designed to ruin your server performance.

I completely Agree with TECK,

Incase you site grow later, try Litespeed, Lighttpd or Ngix as alternative for Apache. You will like it.

[TECK]

I recently moved from lighty to Nginx. I could not make a better move.