Moving sites

[MasterRacker]

I have a physical Windows 2003/IIS6 server hosting a number of ArcGIS based web maps that needs to be replaced. Later this year we will be building a new VM with Windows 2008R2/IIS 7.5 to host these sites.

My question involves the transition period when I have some sites on each server and how I get people to them. The outside world currently sees all sites as

http://gis.mysite.com/mapxxx.

Our ISP maps gis.mysite.com to a specific external address and my internal DNS maps gis.mysite.com to the internal address of the server. The firewall has a 1 to 1 address translation.

Do I have to try and cluster the two servers or is there some other way to manage a staged transition? I can probably take everything down for a day and try to move everything at once, but I would like to avoid that if I can.

Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[Wullie]

Hi mate,

Do you have data that is updated in real time and needs to be transferred over? By this I mean if you had the 2 sites live and people were hitting the old server, would there be any database inserts or any files written to the old server that would need to be transferred over or is everything static?

1) If it's just static files and there are no database inserts etc, then just get everything setup on the new server and when you are ready, make the necessary DNS changes to point the site to the new server. It will take some time for some users to get the new DNS records due to cache but they would hit the old server during the transition so there would be no problem or any downtime involved.

2) If there are any database inserts, you can look into taking everything down for a very short period while you transfer the DB over to the new server and then update the old server so it points to the new DB server address. This way involves minimal downtime and means both front-end interfaces are pointing to the new DB so any updates are stored on the new server.

3) If you have dynamically generated files that need to be written to the server and accessible for future requests, you would probably be best to take the site down on the old server and setup a redirect to the new IP address, so any requests that do hit the old server are transferred over albeit with the IP address but this would only be temporary. This would involve downtime while you move the files over.

I hope this helps but if I maybe didn't understand your request or you want any clarification, please let me know.


Wullie

The pessimist complains about the wind. The optimist expects it to change. The leader adjusts the sails. - John Maxwell