IBM logoEnterprise Cloud Management SupportContact Us
ArticlesArticles Most Popular ArticlesMost Popular Articles Most Helpful ArticlesMost Helpful Articles Submit A QuestionSubmit A Question
RSS Feeds
DrillDown Icon Table of Contents Back
 . . . . . . . . . . . . .
DrillDown Icon Enterprise Cloud
DrillDown Icon Release Notes
DrillDown Icon Known Issues
DrillDown Icon Policies
DrillDown Icon Registration and Login
DrillDown Icon Infinicenter Console
DrillDown Icon Environments
DrillDown Icon Compute Pools
DrillDown Icon Rename a Compute Pool
DrillDown Icon Add Compute Pools
DrillDown Icon Delete Compute Pools
DrillDown Icon Migrate Virtual Machines; Unassisted
DrillDown Icon Migrate Virtual Machines; Assisted
DrillDown Icon Resources Tab
DrillDown Icon Devices Tab
DrillDown Icon Network Tab
DrillDown Icon Cloud Services Tab
DrillDown Icon Resource Alerts
DrillDown Icon My Account
DrillDown Icon Enterprise Cloud API
DrillDown Icon Best Practices
DrillDown Icon FAQs
DrillDown Icon Troubleshooting
DrillDown Icon Enterprise Cloud Managed Edition
DrillDown Icon Sales and Support
DrillDown Icon Proprietary Statement
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
 
Migrate Virtual Machines Between Compute Pools; Assisted

Migrate Virtual Machines Between Compute Pools; Assisted

Organizations can migrate virtual machines between compute pools with assistance from Global Support Services in migrating the settings. Organizations that wish to migrate without assistance, see Migrate Virtual Machines; Unassisted.

Note: Arrange with Global Support Services for assistance before proceeding.

The anticipated use case for migrating virtual machines between compute pools is for organizations that wish to change an existing reserved compute pool into an instance-based compute pool. This article exemplifies this use case. However, this procedure does not preclude migrations between two reserved compute pools, between two instance-based compute pools, or from an instance-based compute pool to a reserved compute pool.

This procedure imposes two limitations:

  • The two compute pools must be in the same environment.
  • Potential billing adjustments can occur in the month in which the migration occurs or the following month.

Prerequisites

The organization must create and sign a contract with sales or client services for an instance-based compute pool and establish the discount tier for billing.

IBM must create a new, instance-based compute pool in the same environment as the existing reserved compute pool.

Copy the Virtual Machines

The virtual machines can be copied two ways.

Copy Between Compute Pools

The organization can choose to copy the virtual machines between compute pools. The copy identical creates the copied virtual machine configured with the IP address of the source virtual machine, which causes address conflicts on the network if both source and copied virtual machines are powered on. However, the IP address is not assigned to the copied virtual machine in the Enterprise Cloud configuration database or Infinicenter Console; this is a deliberate design feature. Once the organization copies identical the virtual machines, the organization must migrate the services and settings between the two virtual machines.

Copy the Virtual Machines to the Destination Compute Pool

Navigate to the source reserved compute pool in Infinicenter Console.

For each virtual machine in the source reserved compute pool:

  1. Shut down the source virtual machine.
  2. Rename the source virtual machine in Infinicenter Console to free the virtual machine names for the new compute pool and to enable rollback, if needed.
  3. Copy each virtual machine in the source reserved compute pool identically to the destination compute pool.
  4. Note: If snapshots are enabled on a virtual machine, the copy identical creates the new virtual machine from the current state of the virtual machine. Snapshots are not copied.

  5. Record the new name of the source virtual machine.
  6. Note: Retain the source virtual machine in the source reserved compute pool to enable rollback, if needed.

Create Inventory

Create an inventory of the virtual machines to migrate. The inventory must include:

  • Name of the source reserved compute pool.
  • Name of source virtual machines.
  • Name of destination instance-based compute pool.
  • Name of destination virtual machines.

Continue with Migrate Services and Settings.

Move Through VM Catalog

The organization can choose to move the source virtual machines through the VM Catalog. This method is always available to the organization.

Copy the Virtual Machines to VM Catalog

Navigate to the source reserved compute pool in Infinicenter Console.

For each virtual machine in the source reserved compute pool:

  1. Shut down the source virtual machine.
  2. Copy each virtual machine in the source reserved compute pool to the VM Catalog.
  3. Note: If snapshots are enabled on a virtual machine, the copy identical creates the new virtual machine from the current state of the virtual machine. Snapshots are not copied.

  4. Rename the source virtual machine in Infinicenter Console to free the virtual machine name for the create procedure.
  5. Note: Retain the source virtual machine in the source reserved compute pool and enable rollback, if needed.

  6. Record the new name of the source virtual machine.
  7. Record the row and group of the source virtual machine.

Create the Virtual Machines from VM Catalog

Navigate to the destination instance-based compute pool in Infinicenter Console.

For each catalog item created from the source reserved compute pool:

  1. Create each destination virtual machine from the VM Catalog in the row and group of the source virtual machine.
  2. Console connect to the new virtual machine and ensure that the proper network and IP settings are configured in new virtual machine.
  3. Record the name of the new virtual machine.

Create Inventory

Create an inventory of the virtual machines to migrate. The inventory must include:

  • Name of the source reserved compute pool.
  • Name of source virtual machines.
  • Name of destination instance-based compute pool.
  • Name of destination virtual machines.

Continue with Migrate Services and Settings.

Migrate Services and Settings

Provide Enterprise support with the inventory of virtual machines to migrate created in Copy the Virtual Machines.

Test Destination Virtual Machines

  1. Test each destination virtual machine.
  2. Test the services associated with each destination virtual machine.

Delete Source Virtual Machines and Catalog Items

  1. Delete the source virtual machines renamed in step 2 of Copy the Virtual Machines to the Destination Compute Pool or step 2 of Copy the Virtual Machines to VM Catalog earlier.
  2. Note: Failure to remove the source virtual machines (or, alternatively, change the IP addresses) will result in duplicate IP address errors.

  3. Delete the catalog items created in step 1 of Copy the Virtual Machines to VM Catalog earlier, if desired.