This article describes the migration of a .NET web application from Amazon Web Services (AWS) to Rackspace Cloud. It takes an estimated 30 minutes to complete, if you follow the instructions step by step.
These steps assume you have provisioned the Rackspace Cloud services your application will require.
The topology of the application in this scenario is represented in the following figure:
- Microsoft Windows Server on AWS running a .NET web application on Internet Information Services (IIS) (Windows Server 2012 with IIS 8 is used in this use case.)
- Valid and enabled account on Rackspace Cloud
- Identify the resources to migrate, including application and database resources.
- If you have not already, create a Cloud Server instance and any supporting Rackspace Cloud services.
Install software packages
- Install the Rackspace Cloud Files client as follows:
- Connect to the AWS instance by using Remote Desktop Connection.
- After you are connected, install a client that you will use to back up data to Rackspace Cloud Files (for example, Cyberduck, available at http://cyberduck.ch/).
You can use any browser to download the client.
- Create a connection to Rackspace Cloud Files by using your Rackspace account user name and API key.
You will use this connection to back up data during the migration steps.
- Install IIS 8 by using the instructions located at http://www.iis.net/learn/get-started/whats-new-in-iis-8/installing-iis-8-on-windows-server-2012 .
Back up data from AWS to Rackspace Cloud Files
Using the client that you installed in the preceding section (for example, Cyberduck), upload the .NET project folder to the Rackspace Cloud Files container that you created in the article on provisioning your cloud services.
Restore data from Cloud Files to Cloud Servers
- Connect to your Rackspace Cloud Servers instance by using Remote Desktop Connection.
- Copy the .NET web application folder from the Cloud Files container to the cloud server at the following location:
- Open IIS Manager, click Add Website, and enter details: site name, physical path, and host name.
- After the website is created, stop the Default Web Site pre-installed application and start your web application.
Test your application
Click on Browse *:80 (http) to see the application in the browser.
Before making your migrated application available to the public, we recommend weighing some post-migration considerations like the security of your setup, monitoring its availability, and ensuring your data is regularly backed up.
© 2011-2013 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER