On Tue, 04 May 1999, Justin Ryan \[PHT\] wrote:
>
>there is little.. well.. nothing, that we can do about this right now.. we
>can put the stuff on the servers in oakland but then we are limited to a
>T-1's bandwidth, which do you think is more important? our image will be
>better protected by the T-1, b/c that won't fail, but it will be
>congested.. also, it will be down when we move, which is a bad bad thing..
>but maybe we could coordinate something and point the address of the
>cluster to the utah server after we move.. i don't know, I'm trying to
>help coordinate this, and I'm going to be setting up the script that will
>display the license, ask for info, and then allow the file to be
>downloaded.. I was going to do it in perl but If I can do it in C that
>will definitely help the server load..
>
Here is a relatively simple method for moving a web server with a
minimum of down time.
Here are my assumptions:
1. You have a web site (www.pht.com) at location A.
2. You are leaving location A in the near future.
3. You have a new location B where you want to move your web site.
4. There will be some period of time where you will be maintaining
both locations.
5. You are not losing the IP address for the original machine (at
least not immediately.)
Here is what I would do:
1. Alter your web site (www.pht.com) so that the Apache server runs
on a port other than 80, for example, 8080. Install squid on the
system and use it as a pass through. In this type of setup, squid
receives traffic on port 80 and redirects it to port 8080, where
Apache handles it. This allows squid to serve static pages from
it's cache (which is faster than apache) and lets apache handle any
dynamic stuff.
3. Set up your new web site (www2.pht.com) at your new location. This
server can either be run on port 80 or better yet, port 8080 and set
up squid to do the same type of passthrough as at the old site.
4. Once the second server is up and ready, change squid's conf file to
redirect to the new server instead of the old one and restart squid.
(You will only be unavailable for the amount of time it takes to
restart squid.)
5. Change your DNS setup so that the old name (www.pht.com) has an
appropriate IP address for your new site, ipalias this name to your
new server and rename the old server to something else (oldwww.pht.com).
Keep this server going for about a week so that the DNS change has
ample time to be propogated. In this week, the old server will
redirect any queries that arrive at the old IP address and redirect
them to the new server. You should see traffic taper off to the
old machine as the DNS change propogates until it reaches next to
nothing, at which time you can turn off your old server.
Tom
--
+-----------------------+-------------------------+------------------------+
| Tom Schenk | Use Linux! | All opinions expressed |
| [EMAIL PROTECTED] | Friends don't let | are mine and not those |
| [EMAIL PROTECTED] | friends do Windows! | of my employer. |
+-----------------------+-------------------------+------------------------+
---------------------------------------------------------------------------
Send administrative requests to [EMAIL PROTECTED]
