2 servers = 1 apache or 2?

I am working on a new FC2 box that will be splitting my websites and mail. But, I am a little confused about routing across my internal network.
I don't have a separate Proxy server ( yet ).

internet->Router->192.168.0.205 (main server box)

on 192.168.0.205 resides a current copy of Apache and ALL my websites and mail server. Now that I have a new server to add to my farm, 192.168.0.206, I want to route some websites that would be on 205 to 206.

would my httpd.conf file on 192.168.0.205 list
<virtual host 192.168.0.206/www/html/dir_of_site?>

I am looking for the syntax to route from 205 to 206.

Also, Would\Could I run a second copy of Apache on 206? Would this conflict?
I'm asking because I may want to migrate my 206 box to be the prime point, ie router->192.168.0.206, instead of the older 205

I hope I have been clear enough about what I am attempting.

Thanks, Frog
__________________
Curious by Nature,
Linux by Choice
DBA_FrogAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

samriCommented:
hi Frog,

It would depend on how your existing websites is currently built.

I would presume that you had several websites, and each had their own Vhost defined as (you mentioned in the text).

So, you had

<VirtualHost 192.168.0.205>
   ServerName  www.site1.com
   ...
</VirtualHost>
<VirtualHost 192.168.0.205>
   ServerName  www.othersite.com
   ...
</VirtualHost>

... and the list goes on.

if this is the case, I would suggest that you built the apache on 192,168.0.206 to be identical as those on 205, and defined the vhost the same as those on 205, except the Vhost container now

<VirtualHost 192.168.0.206>

And for those websites (on 205) that needs to be migrated, remove all directive, and replace it with the Proxy/ProxyPass directive

For example, if you want to move www.mysite.com from 205 to 206, then;

<VirtualHost 192.168.0.205>
  ServerName www.mysite.com
  ProxyPreserveHost On
  ProxyPass               /             http://192.168.0.206/
  ProxyPassReverse   /             http://192.168.0.206/
</VirtualHost>

Also good to enable ProxyPreserveHost to ensure that the request to Apache on 206 would still carry the "Host:" header for www.mysite.com, to ensure the Vhost matching is done correctly.

Some ref:
http://httpd.apache.org/docs-2.0/vhosts/
http://httpd.apache.org/docs-2.0/mod/mod_proxy.html
http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#forwardreverse
http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#examples
http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxypreservehost

HTH.
0
mrielfCommented:
On 192.168.0.205 machine do this:

Turn on Proxy_module in apache
                    LoadModule proxy_module /usr/lib/apache/1.3/libproxy.so

Use VirtualHost section like this:

<VirtualHost x.x.x.x>
    ServerAdmin webmaster@server_on_206.com
    DocumentRoot /anything
    ServerName server_on_206.com
    ProxyRequests Off
    ProxyPass / http://server_on_206.com/
    ProxyPassReverse / http://server_on_206.com/
    ErrorLog /var/log/apache/server_on_206.com.log
    CustomLog /var/log/apache/server_on_206.com-access.log common
</VirtualHost>

Insert server information to host file:

192.168.0.206      server_on_206.com

On 192.168.0.206 Set up your servers....

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DBA_FrogAuthor Commented:
Thank you both for the information.

mrielf: Once I load the module for Proxy_module, will that re-compile Apache?, I've read a little about modules in Apache and I want to make sure I don't have to do any additional steps after loading the module. Other than the obviouse reload of apache.

TIA for the info.
0
mrielfCommented:
Of course you don't need to recompile apache, just restart it... (or reload configuration)
0
DBA_FrogAuthor Commented:
Again, Thank you both for your answers. Since they were very similar I split the points between the two of you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.