Performing delta data migration -- Live DDM and Final DDM

This section provides information about how to run the delta data migration. The following topics are covered in this section:

Running Live DDM and Final DDM - a typical staged upgrade

You are migrating your cloud environment from 2.1.x to 4.x. You have a large number of CIs to migrate from your production Enterprise-AR server to your staging server. You must stage the upgrade to avoid down time in your environment and to preserve your customizations. You schedule one month to upgrade all the components. You create a schedule, based on the tasks listed in the 2.1.x to 4.x Upgrade Checklist.

When you reach the DDM tasks during the upgrade (indicated by bold font, for example, Live DDM), you run the estimator utility that you received from BMC Customer Support. You have approximately 20 hours of data to migrate. Because the DDM process creates a performance impact on production, you schedule multiple DDM runs for four hours each at least five times in non-peak times to migrate most of the CIs to the Enterprise-AR and Cloud-AR staging servers.

When you reach Final DDM, you want a delta data migration estimate not exceeding 15-30 minutes. For example, 8000 remaining CIs take approximately 5-10 minutes to migrate.

Guidelines for migrating the delta data

When you migrate the delta data, ensure that you adhere to the following guidelines:

Use the same Admin user account to log in to both the servers. The upgrade environment is a database restore of the production environment. BMC recommends that you use one user to do this migration, which will help to track and debug issues. If you use Demo, ensure that you have the same password for both the servers for that Admin account.
You can run the Delta Data Migration tool once or multiple times. BMC recommends that most customers run the tool in two stages:
- If you have a large amount of data in your production environment (for example, if Delta Data estimate is more than 15-30 minutes), run Live DDM in non-peak hours over a series of days so that there is no production outage. Here you can run DDM as many times as necessary to reduce the final amount of data that you need to migrate before you start your production outage. The first data migration moves all of the data that has been added or changed since you made the production backup.
- Run Final DDM in non-peak hours after you start production outage. Final DDM moves only the data that has changed since you started running the Live DDM. This ensures that the time required to do the data migration (your outage window) is as small as possible. You should only run Final DDM if the Delta Data estimate is less than 15-30 minutes.
If the Delta Data estimate is less than 15-30 minutes in your production environment, you only need to run Final DDM. Your environment can likely handle a small production outage.

Before you begin

To avoid missing a DLL error, perform the following steps before you start the Delta Migrations application.

Make sure that the PATH environment variable contains the Migrator installed directory path, for example, C:\Program Files\BMC Software\Migrator\migrator.
Make sure that the configuration.xml file (by default, C:\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration) has the migrator installed directory path correctly updated. The default path set is C:\Program Files\BMC Software\Migrator\migrator.
Make sure that you can connect to the production and staging servers, for example, the AR System server on the production VM is started, that the firewalls are disabled, and so on.

To migrate the delta data

The following instructions provide examples for both Enterprise-AR and Cloud-AR delta data migration.

Note

You use the same steps for Live DDM and Final DDM.

Go to the C:\Program Files\BMC Software\Migrator\migrator\DeltaDataMigration directory.
This path is the default.
For more information on the package contents, see Delta Data Migration tool package contents.
Double-click the DeltaMigration.exe file.
The Delta Migrations window appears.

Click the button to the right of the Source Server field.

Field	Description
Source Server	Source server name (production server).
User Name	User name of the source server and destination servers. The user name should be the same for both servers.
Password	Password of the source server and destination servers. The password should be the same for both servers.
TCP Port	Default value used by the script. If no port is specified, the default is 0.
Fast/List Port	Default port is 390635.

Specify the source server information in the dialog and click OK.
Open the Server dialog again by clicking the button to the right of the Destination Server field.

Specify the destination server (staging server) information and click OK.
After you provide the source and destination server information, the Delta Data Migration Tool validates the versions on your source and destination servers and provides a list of all supported BMC Remedy AR System products and applications. Applications shown in red indicate that no appropriate package was found.

Field or Button	Description
Fetch Data/Objects Created/Modified After Date field	The timestamp from when you want to transfer the data. Data in the forms that are greater than or equal to this timestamp will be migrated.
Compare (optional) button	This button optionally creates a comparison result report.This report can be used to identify all data that has been created and/or updated during the delta time period.
Migrate button	This button starts the data migration. All delta data is transferred from the source server to the destination server.
Re-run applications with previous criteria & instructions check box	This check box is checked by default and should remain checked even if you are rerunning the migration after fixing any data issues. NOTE: If you are using the multi-run approach to migration to minimize your downtime, make sure that the Re-run applications with previous criteria & instructions check box is not selected.

For Enterprise-AR, perform the following steps:
1. Select the applications for which you want to migrate the delta data.
  Select the appropriate applications that are not marked in red.
  - BMC Remedy Action Request System
  - BMC Atrium CMDB
  - Remedy Foundation Product Catalog
  - BMC Atrium Integration Engine
  - ITSM Foundation
  - ITSM Asset Management
  - ITSM Service Desk
  - ITSM Change Management
  - BMC Service Level Management
  - BMC Service Request Management
  - BMC Remedy Knowledge Management
  - Integration For Remedy Service Desk
  - BMC_PN: Class and Attribute Definitions for Service Impact Management
  - SIM: Class and Attribute Definitions for Service Impact Management
  - BMC Cloud Management Foundation
  - BMC Cloud Management Administrator
  - BMC Cloud Management User
  - BMC Cloud Enterprise Atrium CMDB
2. Clear the BMC Cloud Atrium CMDB option.
Enter the date and time when you want to migrate the data.
For example (to start Live DDM), the Start Date is the date when you created the staging server. The End Date is the current time. But to run Intermediate DDM, the Start Date is the date of the last DDM run and the current End Date.
Note
If you are migrating the delta data for First DDM, the timestamp of the production server backup is used from when you set up the staging server. If this migration is a re-run scenario, the timestamp of the previous run is used.
(Optional) If you are migrating custom forms data, select Custom in the Application Name list.
By default, Custom is not selected.
If you want to compare two or more forms to view the changes, click Compare. Otherwise, click Migrate.
The DeltaMigration window appears with the parameters that will be used by the Delta Data Migration Tool.
Click Yes to continue.
A command window is launched for each application that you are running. The windows close automatically when the process is done, or if there is an error. If you click No, the migration or comparison will be cancelled.
Tip
If you want to re-run the migration or the comparison, you must wait for all of the command prompts windows to close before executing a new run. The command output will be available as an HTML log file.
Run delta data migration for Cloud-AR:
1. Start the Delta Data Migration application and enter the logon details for the Cloud-AR production and staging servers.
2. Select the applications for which you want to migrate the delta data:
  - BMC Remedy AR System
  - BMC Atrium CMDB
  - Remedy Foundation Product Catalog
  - BMC Atrium Integration Engine
  - BMC Cloud Atrium CMDB
3. Clear the following options:
  - BMC Cloud Enterprise Atrium CMDB
  - BMC Cloud Management Foundation
  - BMC Cloud Management Administrator
  - BMC Cloud Management User
4. Run the remaining delta data migration steps.

To normalize the migrated delta data – 2.1.x to 3.0 migrations only

After you migrate the delta data, you must run the migration scripts. The scripts normalizes the data that you migrated from BMC Cloud Lifecycle Management 2.1.x to 3.0. The scripts also converts the 2.1 data to a 3.0 compatible format. To perform data migration and normalization, see the To run data migration using the maintenance tool topic.

To re-enable DSO, escalations, and database triggers after you finish DDM

After you migrated the delta data, re-enable the workflow and other functionality that you disabled in previous steps on the staging servers.

Re-enable DSO.
For more information, see the BMC Remedy Distributed Server Option on the BMC Remedy AR System 8.1 documentation portal.
1. Log on to the Enterprise-AR and Cloud-AR AR servers and open the Server Information window.
2. Click the DSO tab.
3. To enable DSO, clear Placeholder Mode and then click OK.
Re-enable escalations.
For more information, see Removing or disabling objects on the BMC Remedy AR System 8.1 documentation portal
1. Open the BMC Remedy Migrator tool.
2. Select Tools > Options.
3. Under Category, select Migration > Object Removal.
4. Clear Disable Objects and then click OK.
Work with your database administrator to re-enable the database triggers in the ARSystem schema

Where to go from here

To find the delta data in production, use the AREntryCounter utility.
After you complete the first delta data migration, manually run the DDM escalations.
After you finish Final DDM, use the post_DDM utilities to resolve important issues before you perform the migration.