Subj : question
To   : David Calafrancesco
From : Bob Seaborn
Date : Fri Apr 11 2003 08:33 am

 > Bob Seaborn wrote in a message to David Calafrancesco:
 >
 >BS>       I'm about to give up on it altogether, and replace the server
 >BS> with a newer box, hopefully a faster dual cpu system with more RAM
 >BS> & HD available.  I was hoping that I could find a solution to this
 >BS> perplexing problem to give us breathing room to be abkle to utilize
 >BS> a slow/deliberate switchover to the new system, plus give me a
 >BS> decent learning curve.
 >
 > Then here is what you need to look at and consider for a smooth
 > migration.

      Actually, we did this last night, built a new dual cpu box, plugged in
a 5gb drive for boot, and a 30gb one for data, and migrated all the sub-domains 
that we host to it.  They were the easiest to migrate as they had no complex 
ftp configs.  We plan to finish things off this weekend, assuming all goes 
well.


 >
 > Look at the services the machine is offering, ensure that each service
 > is being directed to a specific hostname. For example, web services go
 > to www.hostname.dom and file services go to ftp.hostname.dom,
 > smtp.host... pop.host... etc etc. Once you have that part in place (and

      So far, all we needed to consider is wwww.* and mail.* for the domains.

 > from what you said it is already there for at least web and ftp but I
 > don't know what hostname you were using for the other services) then you

      Actually, www.*, ftp.*, and mail.* are all I can think of.

 > can pick a part of the system and move it over to a new host. Once each
 > service is it's own hostname, they can be directed to any physical
 > system you may need to send it to via dns. A CNAME record is just fine
 > for most of these (except the MX for the domain can't be a CNAME).

      We do have a partial class-C block of ip's to play with, and also can
control our own dns, etc.

 >
 > You can you tell powerweb to turn off ALL web services, right? That

      As far as I can tell, it's all or nothing.  I _think_ (maybe) I can
control public ftp, but don't recall anything else.  I did change the number of 
ip's Powerweb controls from 28 to 1 which allowed us to place the replacement 
box online quickly.  :)

 > would allow it to do the smtp/pop3 and maybe even ftp for a while as you
 > build a new solution for the email & ftp services.

      Done, took about 3 hours.

 >
 > If you can do that, then a very quick short term solution is to leave it
 > in place while you build a new email solution, drop apache 1.3.25 into
 > place for the web content, and you are back in business... total work
 > required maybe an hour if you need to read up on apache configs,
 > otherwise it is as long as it takes to get the package and unzip it and
 > edit the httpd.conf file.
 >
 > Once you at least have apache up on the OS2 system and powerweb not
 > talking http anymore, your probes for proxy will go away (eventually
 > anyway) as soon as it is circulated that you are no longer an open
 > proxy.
 >
 > That's your quickest path... shutdown web inside powerweb if you can,
 > otherwise direct www.whatever to a different host. You can then shift
 > the powerweb to an irregular port if you can't just shut it down
 > entirely. Optimal would be a firewall software on the box that would
 > stop all connections to the shifted port as a last resort.


      Like I said, all but one ip is now running via Apache, configured with
ispman, under linux now.  The new box is refusing proxy requests, and 
consumption of my bandwidth has dropped considerably.

      I hate to give up on OS/2, but the route we took was at least 2 days
shorter, and we ended up with a much faster box in the process.  Dual P2-500's 
instead of a single P2-266, with less overhead.

--- GEcho/32 & IM 2.50
 * Origin: http://www.nwstar.com (1:140/12)

.