Moving an azure Web site between data centers

Last week when I added jquery to my podcast site, I talked about using cloud services wisely. I want to avoid wasting any unnecessary bandwidth costs. The results were great and my bandwidth for this month was within budget.

I continue to look for ways to optimize and calculate the gold in the cloud service. I found that when my site was running in the American West http://www.aliyun.com/zixun/aggregation/13357.html ">azure data Center, the database (by Carl Franklin's podcast company management is running in the north-central United States. That means I'm spending bandwidth for calling my database. What's more, I was on the Open Internet (although I've opened a firewall to visit) to access a SQL Server, which is slower, not the best way.

It's not normal to keep a Web site so far away from the SQL data center, and of course, you usually place your site and database at the same time. Azure also jumps out of the way when you create linked resources and put them together.

However, Carl has returned the database and the original site settings for a while, and I've just redesigned it recently and recently put it on Azure. In addition, the Hanselminutes Podcast management backstage is in the north-central, so we'll see ourselves in this position before.

The Azure Web server is open in the North Central data Center, so it took me a lunch time to move my site. Although you can't just move as simply as clicking the "Move" button, it's really easy to redeploy. As you can see on the YouTube video above, the entire process, including DNS changes, took less than 15 minutes.

Here are the steps I've made:

I made a new website on the new datacenter I made it sharable so I could use a custom domain (or you can be customized) I took the domain name of the West American site and put it on the portal to the north-central site. If the site is important, When I wait I will do a load balancer and keep both sites, but the total loading time is almost 5 minutes, so I don't have to worry about that. I make sure the database in the North Central and my site is a "linked resource" I make sure my heart site is in the set link string is correct i download the new Web site's published profile and re-export it to WebMatrix (or Visual Studio, and so on) to publish the Web site with a new release profile Clear DNS and visit the site to make sure it is viable delete old site

It works well and I am very glad to see this result. My next golden step (and a good offsite load balancing optimization) will move all the images to the CDN so that friends overseas can get a border cache ... This means Australians will see pictures of the site from the nearby data center. I do this extra benefit with less bandwidth than I spend on the site.