Can you set the index page to redirect the user to the new IP, such as http://xxx.xxx.xxx.xxx . You can also set your DNS records to expire after 1 minute. Or you could replace the 1 server with the 3, then send the 3 server configuration to the new place. After its setup there. Migrate the database off the single setup to the new location and use the Wan to get to the database while you wait for Dns to roll.
Hope I make sense, Steve ----- Original Message ----- From: "Brook Davies" <[EMAIL PROTECTED]> To: "CF-Server" <[EMAIL PROTECTED]> Sent: Wednesday, May 15, 2002 2:57 PM Subject: Moving a CF web app to a new physical local > Hello, > We are faced with the task of moving our 3 server setup to a new > co-location facility while avoiding any downtime. Let me tell you about our > situation. We have 3 NT servers; mail,web and DB. We DO have one extra > server which is essentially unused. The concern is really for ONE website > on a single domain. > > I considered configuring the unused box with mail,CF, and the DB to serve > as temporary server. I could then move this box to the new facility before > making any DNS changes. I could then update the DNS to point to the new > box. Once the DNS changes had thoroughly propagated, and all of the traffic > was being directed to the single server, I could disconnect the other > servers and move them as well and re configure. > > The problem with this scenario is Data Integrity and disparities between > the DB and any generated files (and there are lots of those). The > application is very write intensive, both to the DB and local drive on the > webserver. I fear that since the DNS would not update at the same time for > everybody, that some users would still be using the old box while other > users are on the new box. Or a user would be on the old box one hour and > then onto the new server the next time they log in, an hour later, and they > would not see their latest changes. Then somehow syncing it up later may be > impossible. So in short, I'm not sure that will work. > > I was thinking about somehow having the new server redirect traffic back to > the original box until we are sure the DNS changed have thoroughly > propagated. Then, we could safely allow the new single server to start > handling all traffic. After some testing, I think this is the way to go. A > redirect from IIS back to the orginal servers. But the problem here, from > what I can tell, is that you can not pass form variables when using an IIS > redirect!!! This is absolutely imperative for us, we need to pass form > variables. Are there any work arounds for this with IIS> > > Any ideas? > Brook Davies > maracasmedia inc. > > > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm ------------------------------------------------------------------------------ To unsubscribe, send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body or visit the list page at www.houseoffusion.com
