This article describes the process of migrating an existing First Generation
(First Gen) Cloud Server to a Next Generation (Next Gen) Cloud Server with
little to no downtime by using Cloud Load Balancers and Cloud Server Images. To learn
more about the Next Generation Cloud Servers platform and the migration process,
see Next-Generation Cloud Servers migration considerations and options.
Note: This article assumes that you host your Cloud Servers and Domain Name
Servers (DNS) with Rackspace. However, if you host DNS elsewhere, you need to
perform the steps in the Repoint your DNS to the load balancer
section of this article by using the DNS portal where the DNS is hosted.
The load balancer makes a seamless migration from First Gen server to a Next Gen
server possible. Use it to update your DNS entries by having your stale DNS
entry traffic continue to reach your Cloud Server while allowing the updated
traffic to pass through the load balancer.
Log in to the Cloud Control Panel.
In the top navigation bar, click Select a Product > Rackspace Cloud.
Select Networking > Load Balancers.
Click Create Load Balancer.
In the Identification section, enter a name and select the same region that your server is in.
In the Configuration section, select Accessible on the Public Internet for Virtual IP.
Click Create Load Balancer.
On the main Cloud Load Balancers page of the Cloud Control Panel, click
the name of the load balancer that you just created.
On the load balancer details page, go to the Nodes section, click
Add Cloud Servers, and add the First Gen server to the load balancer.
Note: If you have SSL termination on your server, you need additional
configuration. Enable SSL termination through the load balancer or have two
load balancers sharing the same IP address to direct HTTP and HTTPS traffic
to your server.
At the top of the Cloud Control Panel,
click Select a Product > Rackspace Cloud, then select Networking > Cloud DNS.
Select the domain that is currently pointing to your First Gen server.
On the domain details page, click the gear icon next to your
select Modify Record.
In the pop-up dialog box, enter the IP address of the load balancer in the
Type the load balancer's IP address in to your browser's address bar to
verify your website is loading correctly.
Follow the steps in this section to create an image of the First Gen server.
You can use this image to create a Next Gen server.
Note: If you are on a Linux server with under 40 GB of disk in use, you can
resize down to a 1 GB flavor before taking the image. When you create the new
Next Gen server from the image, you can choose any flavor that allows you to
boot the server from a volume, as described in the
Boot a server from a Cloud Block Storage volume article.
On the Cloud Servers page of the Cloud Control Panel,
click the gear icon next to the First Gen server that you are imaging and select
In the pop-up dialog box, enter a name for the image in the Saved Image Name field.
Select the Next Generation Cloud Server Image option.
Click Create Image.
Use the following steps to create a Next Gen server from the First Gen server image.
In the top navigation bar of the Cloud Control Panel,
select Servers > Saved Images.
Click the gear icon next to the image you created in the previous section
and select Create Server with Image.
Name your server and choose your preferred flavor.
Click Create Server at the bottom of the page.
After the server has been created, attach it to your load balancer by performing
the following steps.
Go to the details page for the load balancer.
Under Nodes, click Add Cloud Servers.
Select the server that you created in the previous section and then click
Add Selected Servers.
Use the following steps to remove the First Gen server that you added
previously from the load balancer:
Note: You can remove the First Gen server by using the Edit Node Condition
feature instead. With this option, anyone currently on the server is unaffected
by the transition but is not permitted to start any new connections.
a. Click the gear icon next to the First Gen server and select Edit Node Condition.
b. In the pop-up dialog box, select Draining Connections.
c. Click Save Condition.
Your server traffic now uses your Next Gen server.
At this time, you can delete the load balancer, but you must update the DNS.
Optionally, you can keep the load balancer and add a second copy of the server
behind it to increase your availability. For more information, see
Tiered configuration using Cloud Load Balancers.
To synchronize data on a Windows server, we recommend that you use FTP.
Updated 22 days ago