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

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 and finish DDM, 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

Note

These instructions apply to all upgrades from 3.x and 4.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 BMC CSM ENT Data 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 - Cloud Portal and Database
    • (3.x only) BMC Remedy AR System and BMC Remedy IT Service Management Suite – Primary and 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 BMC Remedy AR System - Cloud Portal and Database before you run the data migration:
  • 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 section on rogue switches Preparing-for-upgrades.
  • 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 the Platform Manager CSM service (BMC CSM), 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. 
  • If you upgraded your Platform Manager using third-party certificates, make sure that you import RootCA.crt as follows:

Migration method

Steps

Install planner with one AR System server (4.x upgrades)

Import RootCA.crt in the install planner JRE:

  1. Stop the install planner.
  2. Import the certificate:
    • Internal JRE: <CLM Core Install  Directory>\JVM_1.7.0_55\bin\keytool.exe -import -alias root -keystore <CLM Core Install  Directory>\JVM_1.7.0_55\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt
    • External JRE: <External JRE PATH>\bin\keytool.exe -import -alias root -keystore <External JRE PATH>\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt
  3. Re-start the install planner.

Install planner with two AR System servers (3.x upgrades)

Import RootCA.crt  in JRE used during Cloud-AR Install upgrade:

<External JRE PATH>\bin\keytool.exe -import -alias root -keystore <External JRE PATH>\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt

Maintenance Tool on Platform Manager host

Import RootCA.crt in JRE used during Cloud Portal upgrade by using <CLM Core Install  Directory>\Utilities\BMCCloudLifecycleManagement\Maintenencetool.cmd: 

  • Internal JRE: <CLM Core Install  Directory>\JVM_1.7.0_55\bin\keytool.exe -import -alias root -keystore <CLM Core Install  Directory>\JVM_1.7.0_55\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt
  • External JRE: <External JRE PATH>\bin\keytool.exe -import -alias root -keystore <External JRE PATH>\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt

To run data migration from the installer

If you completed the following steps:

  • Completed upgrading the Cloud Portal AR Extensions
  • Finished DDM
  • Did not exit the BMC Cloud Lifecycle Management Installer

perform the following steps to migrate the data.

  1. On the Cloud Upgrade Migration Welcome page, click Next.
  2. Take a VM snapshot and database backup, and then click Next.
  3. On the Upgrade Migration - Cloud Administrator Credentials panel, specify the cloud administrator credentials (your clmadmin user, but not Demo or appadmin), and then click Next.

  4. If you are migrating from 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.

    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.

  5. On the BMC AR System Server & IT Service Mgt. Suite user inputs panel, specify the AR System administrator credentials, and click Next.
    The data migration process begins.
  6. (Optional) During migration:
    1. Click the embedded link at the bottom of the screen to review a step-by-step HTML report of the data migration process.
      Press F5 to refresh the HTML report. You can review the report at <PlatformManagerInstalledDirectory>\migration\report\MigrationStatusReport.html.

    2. Review the Migration Status report for important details about the migration, including:

      • CLM base version
      • Time when migration was started
      • Number of tasks executed as part of migration

      The currently running task always appears first. If there is a migration failure, its status is ERROR. 
      MigrationStatus.jpg

    3. Click the embedded links to review additional details about the migration.  
      Errors appear in red text, and warnings appear in orange. The Additional details section lists all the activities during migration. 
      ImmigrationDetails.jpg 
  7. When the data migration is successfully finished, review the information, and then click Done. 
    You can click the embedded link to review a step-by-step HTML report of the data migration process.
  8. Review the progress of the current session and your overall progress, and then click Next.
  9. Click Exit the Installation to exit the installer and then click Next to end the session.
    Or click Modify Existing Deployment to install additional products or to upsize the deployment type (for example, from Small to Medium). For more information, see Changing-or-upsizing-deployment-types.
  10. In the final Installation Summary panel, review the log and then click Done to exit.

To run data migration using the Maintenance Tool on the Platform Manager

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

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

  5. If you are migrating from 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.

    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.

    The data migration process begins.

  6. During migration, click the embedded link to review a step-by-step HTML report of the data migration process.
    Press F5 to refresh the HTML report. You can review the report at <PlatformManagerInstalledDirectory>\migration\report\MigrationStatusReport.html.
    MigrationStatus.jpg 
  7. Review the log In the final Cloud Upgrade Migration Summary panel and then click Done to exit. 
    CloudUpgradeMigrationSummary.jpg 

 

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