IBM Cloud Docs
Migrating a virtual server between classic data centers

Migrating a virtual server between classic data centers

You have two ways to move your virtual server between IBM Cloud® classic infrastructure data centers:

  • Lift and Shift

When you use the Lift and Shift method, you create an image template, provision it, and cancel the old virtual server. The advantage of this method is that it's usually the easier and quicker method to move a virtual server. However, while the image is being made, the virtual server is shut down.

  • System Rebuild

When you use the System Rebuild method, you order a new virtual server and copy the data from the old virtual server to the new virtual server. This method is more involved because you need to rebuild the OS specifics and redeploy the application, which might also involve making modifications. The advantage of this method is that it provides an opportunity to start fresh with a new system or to upgrade to a newer OS.

The method that you choose depends on your business and timeline requirements.

Lift and Shift method

Before you begin

Before you create an image template:

  • Plan for maintenance time

Creating an image template is an intrusive operation and shuts down the virtual server. After the template is complete, the virtual server powers back up. Powering down and up happens automatically and does not require user interaction.

  • Attached storage considerations

Capturing the data on the attached storage is optional. You can select which attached storage disks are part of the image template. The Boot volume is always mandatory.

  • Network-attached storage considerations

Block Endurance and Performance and File storage volumes are not captured as part of the imaging process. You migrate data for these volumes at the OS level by using data migration tools such as scp, rsync, dd, or another third-party tool of choice. These storage services are data center specific. If you are moving your virtual server to a different data center, order new storage volumes at the same location where the new virtual server is being deployed.

Evaluate and create an image template

  1. Evaluate the virtual server that you want to migrate to see which services it is using, such as:

    • Auto scale group
    • Placement group
    • Security group

  2. Log in to the IBM Cloud® console by using your unique credentials.

  3. From the dashboard, click Menu icon Menu icon > Classic Infrastructure > Devices > Device List.

  4. Click the virtual server that you want to use to create an image template.

  5. From the Actions menu, select Create Image Template. Give the template a unique name that is easily recognized. For more information, see Creating an image template.

Provision the new virtual server

  1. From the IBM Cloud® console, click Menu icon Menu icon > Classic Infrastructure > Devices > Device List > Manage > Images.

  2. Locate the image template that you created in Evaluate and create an image template.

  3. Click the Actions Menu icon icon for the image template and select Order < Type of > VSI. < Type of > is the type of virtual server that you are creating.

  4. Change the virtual server location to the new data center. The form defaults to the original virtual server properties. Other than selecting the new location, you can keep or modify the rest of the parameters to better suit the new environment, for example:

    • Enter hostname and domain
    • (Optional) Select or create a placement group
    • Select a virtual server profile
    • (Recommended) Select SSH key
    • Select Uplink port speeds

The new virtual server is automatically given a new IP address on deployment.

Verify and validate the virtual server, and update network resources

  1. After the new virtual server is deployed, verify the virtual server.

  2. Make any OS level modifications that are needed to the virtual server.

  3. (Optional) If block or file storage volumes were part of the original virtual server, create the new volumes and update the iSCSI or NFS configuration on the new virtual server. After created and attached, copy the data over from the old to new virtual server by using your tool of choice.

  4. Update and add or modify any infrastructure resources, such as:

    • Security groups
    • Firewall rules
    • Load balancers
    • VPN
    • DNS

Final check

  1. After you complete the new virtual server verification and are ready to activate the new server, do one last sync of any data drift from the old to new virtual server.

  2. Shut down the old server.

  3. Create one last image template as a backup.

  4. When ready, clean and cancel any unused resources at the old location.

System rebuild method

For this method, you're ordering a new virtual server and copying the data from the old to the new virtual server. Copying the data is handled at the OS level, by using scp, rsync, dd, or another third-party tool.

Evaluate your virtual server

  1. Evaluate the virtual server that you want to migrate so see which services it is using, such as (not an exhaustive list):

    • Auto scale group
    • Placement group
    • Security groups
    • Firewall rules
    • Load balancers

  2. Make sure that similar services are created at the new data center.

Order, provision, and configure the new virtual server

  1. Log in to the IBM Cloud® console by using your unique credentials.

  2. Click the Virtual Server for Classic tile in the catalog.

  3. Provision the new virtual server:

    • Enter a hostname and domain
    • (Optional) Select or create a placement group
    • Select a location
    • Select a virtual server profile
    • (Recommended) Select an SSH key
    • Add an extra attached storage disk, if necessary
    • Select Uplink port speeds

  4. (Optional) If block or file volumes were part of the original virtual server, create the new volumes and attach them to the new virtual server.

  5. Configure the OS on the new virtual server.

  6. Install all of the appropriate packages applications.

  7. Copy the data from the old server to the new server by using scp, rsync, dd, or another third-party tool.

  8. Update and add or modify any infrastructure resources, such as:

    • Security groups
    • Firewall rules
    • Load balancers
    • VPN
    • DNS

Verify and validate

  1. Verify the new virtual server.

  2. When you're ready to make the new virtual server active, power off the old server.

  3. Create an image template of the old server as a backup. For more information, see Creating an image template.

  4. When you're ready, clean and cancel any unused resources at the old location.