Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Migrating data for the cloud core components

Error
Warning

With Staged upgrades, always execute DDM before you run migration. If you execute DDM on top of migrated data in your staged environment, you corrupt the upgraded system.

After you upgrade the Cloud Portal AR Extensions – Primary, you must migrate any data that you created for the cloud core components, namely Cloud Portal AR Extensions, Cloud Platform Manager, and Cloud Database Extensions. When you upgrade these core components,  your data changes are not automatically migrated. For example, if you created a new attribute on the BMC_ComputerSystem class using Cloud Portal, everything except that new attribute is migrated automatically when you upgrade Cloud Portal AR Extensions.

To migrate the data for the cloud core components, perform the following steps:

Before you begin

Warning

Note

These instructions apply to all upgrades from 2.1.x and 3.x.

Before you start to migrate the cloud data, ensure that you complete the following prerequisites. Ensure that:

  • The Distributed Server Option (DSO) for the BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary and BMC Remedy AR System – Cloud Database Primary products are working after you upgrade the CLM Core components.
  • The Cloud Reconciliation Job on BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary and BMC Remedy AR System – Cloud Database Primary is running.
  • Escalations are running. For example, you must re-enable escalations after you finished Final DDM. For more information, see Performing delta data migration -- Live DDM and Final DDM.
  • All the latest BMC Atrium Orchestrator modules and adapters are activated from BMC Atrium Orchestrator – Configuration Distribution Peer console.
     For information about the list of adapters and modules installed with BMC Cloud Lifecycle Management, see Component-BMC-product-service-pack-and-patch-levels.
  • The following products are running and that you are able to connect to them from the Cloud Platform Manager host:
    • BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary
    • BMC Remedy AR System – Cloud Database Primary
    • BMC Server Automation – Application Server and Console
    • BMC Network Automation
    • BMC Atrium Orchestrator
    • Cloud Platform Manager
  • You log on to the BMC Atrium Orchestrator host, verify that the AR System user is configured, and verify that the user is able to access the BMC Remedy User.
  • Back up the databases and take snapshots for the following products before you run the data migration:
    • BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary and database
    • BMC Remedy AR System – Cloud Database Primary and database
  • If your physical server and XEN server are configured on pre-upgrade setup, edit the existing pod and container by importing pod and container XML with the rogue device information.
  • For more information, see the Upgrading rogue switches topic in the BMC Network Automation documentation.
  • Upgrade the Virtual Center RSCD agent to the same version as that of BMC Server Automation Application Server. For information about upgrading the Virtual Center Agent, see In-Place-upgrade. 
  • Make sure that any cloud administrators and cloud tenant administrators that were created in BMC Remedy IT Service Management but not previously onboarded in 3.1.x are properly associated with a provider or tenant company available in BMC Cloud Lifecycle Management. Otherwise, when administrators try to perform basic cloud administration tasks, the system will return an error that these users do not have the correct set of privileges. 
  • Stop Platform Manager, clear the cache, and delete org.eclipse.osgi:
    1. Stop the Platform Manager service (BMC CSM on Windows, bmccsm on Linux).
    2. Back up the Platform Manager cache (for example, <BMC_CLM_Installation>/Platform_Manager/cache).
    3. Delete the cache folder.
    4. Back up org.eclipse.osgi (for example, <BMC_CLM_Installation>/Platform_Manager/configuration/org.eclipse.osgi).
    5. Delete the org.eclipse.osgi folder. 
    6. Re-start the Platform Manager service.
    7. Begin data migration only when Platform Manager is successfully restarted. 

Before you begin migration from 2.1.x to 4.x

Warning

Note

These instructions apply specifically to upgrades from 2.1.x.

  1. Add the EC2-Amazon Web Server credential, Certificate, and Private Key in the CMF:AmazonEC2CredentialStore form on the BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary (Enterprise-AR) host.
  2. Open the BMC.CLOUD:BMC_Provider form on the Cloud-AR host:
    1. Search for the Amazon provider (AWS).
    2. Copy the instanceID, 
  3. Paste the instanceID into the EC2 Provider guid field on the CMF:AmazonEC2CredentialStore form.
  4. Save your changes.

To run data migration from the installer

If you completed upgrading the Cloud Portal AR Extensions – Primary product and if you have not exited the BMC Cloud Lifecycle Management Installer, perform the following steps to migrate the data:

  1. If the BMC Cloud Lifecycle Management Solution Installer is not already launched on the Cloud Portal AR Extensions – Primary host, launch the installer.
  2. From the Currently Upgrading navigation pane on the left of the panel, select Cloud Upgrade Migration, which is visible under the Cloud Portal AR Extension node.
  3. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, specify the AR System administrator credentials.
  4. Click Next.
  5. On the Upgrade Migration – Cloud Administrator Credentials panel, specify the Cloud administrator user name (your clmadmin user, but not Demo or appadmin) and password.

  6. If you are migrating from 2.1.x or 3.1.x to 4.x and AWS is available in the stack, the Cloud Upgrade Migration - Task Inputs panel appears. Enter the full path to the Amazon Web Services (AWS) account information .csv file, and then click Next.

    Warning

    Note

    The .csv file must contain values for the AWS ACCOUNT_NAME, AWS ACCESS_KEY, and the AWS SECRET_ACCESS_KEY. ACCOUNT_NAME is the AWS account name registered in BMC Cloud Lifecycle Management. For multiple AWS accounts, add new row entries to the .csv file.

    Save this file on the Platform Manager server. In the input file, provide the full path of this file in the migration utility.

     

  7. Click Next.
     The data migration process begins.

To run data migration using the Maintenance Tool

If already exited the BMC Cloud Lifecycle Management Installer after upgrading the Cloud Portal AR Extensions – Primary product, perform the following steps to migrate the data:

  1. From the <BMC Cloud Lifecycle Management installation directory>\Utilities subdirectory on the Cloud Portal AR Extensions – Primary host, double-click the BMCCloudLifeCycleManagementMaintenanceTool executable file.
  2. Select the Upgrade Migration tab.
  3. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, specify the AR System administrator credentials.
  4. Click Next.
  5. On the Upgrade Migration – Cloud Administrator Credentials panel, specify the Cloud administrator user name (your clmadmin user, but not Demo or appadmin) and password.

  6. If you are migrating from 3.1.x to 4.x and AWS is available in the 3.1.x stack, the Cloud Upgrade Migration - Task Inputs panel appears. Enter the full path to the Amazon Web Services (AWS) account information .csv file, and then click Next.

    Warning

    Note

    The .csv file must contain values for the AWS ACCOUNT_NAME, AWS ACCESS_KEY, and the AWS SECRET_ACCESS_KEY. ACCOUNT_NAME is the AWS account name registered in BMC Cloud Lifecycle Management. For multiple AWS accounts, add new row entries to the .csv file.

    Save this file on the Platform Manager server. In the input file, provide the full path of this file in the migration utility.

  7. Click Next.
     The data migration process begins.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Cloud Lifecycle Management 4.1