Migrating delta data
Delta data refers to any data changes that occur on your current production Remedy system during a staged upgrade of the production system. You migrate delta data by using the Delta Data Migration tool after the upgrade of the platform, applications, and secondary servers is complete and the deployment package has been imported. The Delta Data Migration tool is installed as part of the BMC Remedy Migrator installation.
In this process, the source server refers to your current production server and the destination sever refers to your staging production server.
Supported migration paths
The following table lists the earliest version from which you can migrate product data to the current version.
Earliest supported version from which you can migrate data
BMC Remedy AR System
BMC Atrium Core
|BMC Atrium Integrator||8.0.00|
BMC Remedy ITSM applications
BMC Service Request Management
BMC Service Level Management
BMC Remedy Knowledge Management
BMC Service Impact Manager
Integration for BMC Remedy Service Desk
|BMC Process Designer||8.3.03|
BMC ProactiveNet Performance Management
Before you begin delta data migration
- Do not perform any of the tasks in the Restrictions after restoring the database on a staging system section after you restore the current production database to the production staging system. If you have performed these tasks, do not proceed with the data migration. For additional information, contact BMC Customer Support.
When you migrate data from version 9.1 and later, the Delta Data Migration utility does not migrate data for CTM:People and User forms because the encryption format for AR password (encrypted data) fields is changed.
If the Delta Data Utility migrates the data and overwrites the password field data, you need to manually fix the password.
For more information, see Migrating User form and CTM:People form data
Preparing for the delta data migration
First review the Overview of the Delta Data Migration tool and then perform the following steps to prepare your environment for migrating delta data as part of a staged upgrade.
|1.||Configure the Delta Data Migration tool prior to running DDM||Configure the PATH environment variable and count settings to improve the performance of your data migration.|
|2.||Perform server configuration adjustments|
For staged upgrade environments. you must perform the Server and DB configuration settings to improve the performance of the DDM tool. You perform these configuration adjustments on the source server (current production server) and the destination server (staging server) at various points within the delta data migration process.
After the final DDM run is complete, you will revert the previous changes to their original state.
|3.||Search for additional data changes|
You must now run the utility to search for any additional data that might have been created from the time you backed up your data and set up the staged environment.
Note: Do not start the data migration before you have identified and resolved any possible data conflict or data integrity issues with the additional data.
|4.||Estimate your data volume and plan your DDM runs by using the AREntryCounter utility||Use the AREntryCounterUtlity to estimate the total data volume for you migration and plan your DDM runs. The utility counts the number of entries in the forms that are part of a DDM package.|
|5.||Perform migration prechecks||At this stage, you already have determined the volume of your data and planned the DDM. Perform prechecks before you start your migration to resolve issues that might be applicable to you.|
|6.||Extend delta data migration to include customizations||Add custom forms to the DDM package and migrate the data for these custom forms.|
|7.||Deleting orphan records||During the delta period, if you changed the login ID, support group association, permissions groups, or the functional role for your users on the current production server, perform the steps explained in the topic.|
|8.||If your custom or backend forms have a large amount of data, use SQL to migrate data for the initial batch of data, and then use DDM for the subsequent runs.|
|9.||(optional) Migrating archived data||(Version 9.0 or later only on the source server) Perform this task if you want to also migrate your archived data.|
Performing delta data migration
Perform the following steps to run the delta data migration (DDM) as part of a .
|1.||Perform the data migration for the first time|
Run the data migration for the first time immediately after your upgrade is complete.
|2.||Review the migration results and resolve issues|
After you complete the data migration, review the migration results for issues and resolve as required. You must re-run DDM for the same product selection and date range, if you encountered any errors in your DDM run.
To successfully complete the data migration, you must rerun the DDM until no errors are generated for that date range. Do not proceed with the migration for the next date range until the previous date range data is successfully migrated without any errors.
If you first DDM run completed with errors on one or more of the following forms, you must search for and delete the orphaned records as explained in the procedure:
|4.||Perform the data migration until you go live|
To keep up with the data differences, run DDM every day after the you upgrade on the staging server.
On the day that you freeze for go live, run DDM every two to three hours prior to the outage so that the final DDM run can complete in less than an hour when the freeze starts. For a complete list of cutover activities, see Cutover activities for staged upgrade.
|5.||After every DDM run, use the utility on the source and destination servers for the specific data range to validate the counts.|
After you complete delta data migration
After you run the final DDM and the perform cutover activities for a staged upgrade, perform the postmigration activities on the production staging server during the cutover window. Ensure that you perform these postmigration tasks before you go live in the final step of the staged upgrade.