currently I have 1 server / 1 site apache 2.2 openSUSE Linux ( LAMP ) ( no MOVE TO other os/DIST!!) important: I have zero load or traffic problems, zero CPU/memory problems - hence no urgent need for any complicated solution. the purpose of extension is purely quality! my expansion now is to have my second new server used to further improve the quality of surfing experience for my ONE site. I have heavy traffic and now the following HW available ( only part of it in use by these hours ): 2 servers = 4 sata drives each server 2 CPU ( dual x86_64 ) I would like to split up my traffic into priorities as below: 1a. admin, mysql, apache, nameserver, mail on ONE server = ONE drive first server 1b. same server second drive for ALL system logging and backup only 2a. all other text / flat file traffic on first drive second server 2b. heavy download traffic = ONE subfolder of my site on second drive on second server anyone ever done something comparable ? ONE site on 2 servers / 2 IPs one apache or 2 apache ? as said above - each of the 2 servers is capable to handle the FULL traffic alone by CPU/RAM etc on a single drive. I just love to split up my various sub-folders / sections of my high traffic site ( more than 600'000 hits / day, 12GB/day next few weeks double or triple ) onto 3 drives on both available servers for even faster better surfing quality. any help by EXPERIENCED server admin welcome. you may post URL to howtos ( googling so far has given no such results as most common situations have the opposite i.e. one server many sites ) also any additional security aspects for splitting up traffic to 2 separate servers welcome!
I have it now - running perfectly SINCE YEARS please specify WHY and provide basis of your experience - like how many root servers YOU run/configure/manage since how many years to give me a picture of value of your one line above. for now I have all on ONE server/ONE drive - as said clearly above with ZERO problems since years under heavy load.
im in this game for 10 years now, having my own dedicated servers since 2001. for me personally atm i only administer one server, but i have root-logins to ~30 customer´s servers to regularly fine-tune on the settings if needed. WHY NOT http and mail/dns on the same box?? simply because HTTP is the by far most intensivley used protocol, and a clogged http then also means slow DNS resolution and slow mail-delivery. even worse-- if dns is not responding delivering mailservers will not even know that the domain has a mailserver... sure they retry sending later and it will work then, but delay is delay. i totally believe that your site is doing fine even under relatively heavy load, but if there´s a DDOS going onto a resource-intensive Php-script, i bet it will not only clog the httpd, also the other services will suffer.
ok but as clearly pointed out LOAD etc is ZERO problem now with one server / one drive hence the separation will be as above listed unless there is a really heavy security reason for doing otherwise. now with current setup ALL works perfect - with multiple resources even much better than perfect. that part was no real issue - apache config however might be ... but therefor i love to have one admin-experience with one large site on one or several servers - specially relevant to howto split up in apache config.
if all is perfect and my answers dont satisfy you, i see no need to further go into your topic. you seem to know everything better anyway, so my last word is fallen in this topic. have a nice evening.
just creat a subdomain in ur 2rd server and point the subdomain to ur 2rd server by adding A entire to it