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 delta data

If you continued to use your BMC Cloud Lifecycle Management 2.1.x solution while upgrading to 4.0 in a staging environment, you must migrate the delta data created in 2.1.x to 4.0. Delta data refers to the data changes that might have occurred on the production server while you upgrade the 2.1.x products to 4.0 on the staging server.

The Delta Data Migration Tool is bundled with the BMC Remedy Migrator application. The CLM package for DDM is located at <clm_core_install_directory>\Cloud_DB\extensions\clm\public\schema\ddmpackage on the Enterprise-AR host. After the delta data is migrated to 4.0, the staging server is converted to the production server. You must perform the following tasks to migrate the delta data:

Upgrading from 2.1.x to 4.0

If you are upgrading from 2.1.x to 4.0 and you created BMC Network Automation data (for example, network containers or mappings in production) in BMC Cloud Lifecycle Management, perform the following tasks before you start delta data migration. These tasks all require downtime.

Note

These steps are not valid when upgrading from 3.x to 4.0, because BMC Network Automation is backward-compatible with 3.x.

  1. Take the latest BMC Network Automation database dumps and import them on the staging area again.
  2. Run the database upgrade script that is part of BMC Network Automation.
    For example:
    /opt/bmc/bca-networks/tools/upgrade_db.sh
    This action upgrades the BMC Network Automation database.

Steps for performing the delta data migration

You must perform the following steps in the order listed to successfully complete the delta data migration.

Note

BMC recommends that you perform these tasks in a non-production environment, for validation purposes, before you perform the upgrade for the staging and production servers.

  1. Prepare the destination server, which might be the staging Cloud Database or Enterprise AR System server, for delta data migration.
  2. Run the Delta Data Migration tool to migrate the delta of data that changed during the staging server upgrade.
  3. Run the migration scripts to normalize the data for your upgraded version of BMC Cloud Lifecycle Management.

Before you begin

Before you migrate the delta data, ensure that you fulfill the following requirements.

Requirements for the delta data migration

Requirement

Description

Staging server

To upgrade the cloud products with minimum interference to your existing production environment, you should have already created a staging server. You must have this staging server function to perform the delta data migration. After the data is migrated, you will promote the staging server to the current-version production server.

Database on the staging server

A database instance on the staging server with sufficient space to be promoted to a production server. This database instance should be compatible with the current production database instance to allow for database backups and database restoration.

BMC Remedy Mid Tier server

A mid tier server with sufficient space.

Microsoft Windows Server

An environment on which to install the BMC Remedy Migrator. This server must have a minimum of 2 CPUs, 4GB memory, and 40GB disk space.

Note: You can run the Delta Data Migration Tool, which is bundled with the BMC Remedy Migrator, on the same host as your mid tier host. If the mid tier host resides outside of the Local Area Network (LAN) segment, BMC recommends that you deploy a separate server for the Delta Data Migration tool.

BMC Remedy Migrator

Ensure that you have the BMC Remedy Migrator 8.1 installed. You must:

  • Install Oracle JRE version 1.7 64-bit or later
  • Ensure that the staging server and the current production server have a BMC Remedy Migrator license.
    For more information about installing the BMC Remedy Migrator, see Installing BMC Remedy Migrator.

 

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