Migrating to Rackspace from another hosting provider
This article provides instructions for developers who are migrating their infrastructure from another hosting provider, such as Azure or Linode, to the Rackspace Cloud. These instructions provide a high-level overview and are not specific to any particular hosting provider. If you need more assistance for complex infrastructures, you can use Rackspace Migration Services.
- A Rackspace Cloud services account
- Access to your account with your current hosting provider
Based on the size and configuration of your existing cloud instance, select an equivalent size and configuration for the Rackspace Cloud Servers instance that you will provision. Consider any resources that you want to migrate from your current hosting provider, including application and database resources.
For an overview of the Rackspace Cloud products, see the Rackspace Core Infrastructure Guide.
Provision and configure the Cloud Servers instance
Depending on the size of your current server and operating system, select an equivalent instance type and provision a new instance on Rackspace Cloud Servers.
Use one of the following methods to transfer your data from your existing hosting provider to your new cloud server. The migration method that you use depends on the nature of your data.
Note: Back up the data on your existing server before you migrate it.
You can use rsync to connect the servers and transfer the data. The following steps describe how to establish communication between your existing server instance and new Rackspace server instance.
- Log in as root to your existing server.
Verify whether rsync is installed on your existing server.
- If rsync is not installed, install it based on your distribution.
Debian or Ubuntu:
apt-get install rsync
Red Hat or CentOS:
yum install rsync
Use SSH to log in to your Rackspace server from your existing server. Generate an SSH key from your existing server if you have not done so already:
ssh-keygen -t rsa -b 4096 -v
Transfer your SSH key to your Rackspace server. Substitute your new Rackspace server’s IP address in the following command.
Copy your existing server files by using rsync. Replace the IP address after
root@with the IP address of your Rackspace cloud server.
Note: Adjust the following command to fit your specific situation. For example, you might need additional excludes or to change the source and destination paths.
rsync --exclude="/sys/*" --exclude="/proc/*" -aHSKDvz -e ssh / email@example.com:/media/xvda/
Besides rsync, you can transfer data from an existing server to a Rackspace server in a number of different ways. The following methods upload your existing data to Rackspace Cloud Files. After the data is uploaded, you can then download and restore it on your new server.
Use OpenStack Object Storage (swift)
Install OpenStack Object Storage (swift) on your existing server and directly copy your data from your existing server to Cloud Files, without downloading the files locally.
Install a GUI tool on your local computer
In certain cases, such as if your existing server is Windows based, you need to install a GUI tool (such as Cyberduck) to upload data to Cloud Files.
Use the Cloud Control Panel to upload files
The Cloud Control Panel enables you to upload data from your local computer to your new server. This method is useful when you do not want to install additional software to transfer your data. However, we do not recommend downloading your data locally because it is not as secure as using the other methods.
After your data is uploaded to Cloud Files, download and restore the data on your server.
After the data from your existing server is stored on your new Rackspace server, make any necessary configuration changes for your application and database.
Test after migration
Hosting providers have their own configurations, syntax, and services, so it is important to test your new Rackspace configuration. Use the following techniques:
- Thoroughly test the applications deployed on your Rackspace server.
- Make any changes to your configuration files as necessary. These changes could include any reference to hostnames, IP addresses, and file paths.
Implement monitoring and backup solutions on your cloud server and focus on enhancing security.
Continue the conversation in the Rackspace Community.
©2017 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License