This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Performing the data migration

When migrating your data, observe the following guidelines:

  • Use the same Admin user account to log on to both servers. The upgrade environment is a database restore of the production environment. BMC recommends that you use one user account 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 servers for that administrator account.
  • You can run the Delta Data Migration Tool one time or multiple times. BMC recommends that you run the tool at least twice: before you start your production outage, and again after the production outage begins. The first data migration moves all of the data that has been added or changed since you made the production backup. The second migration moves only the data that has changed since you started the first data migration. This method ensures that the time required to do the data migration (your outage window) is as small as possible.

Before you begin

If you have forms that contain large amounts of data and you want to know the total number of records that are migrated or you want to improve performance, you can set the following configuration setting before running delta data migration (DDM).

The BMC Remedy Migrator Migrator Configuration.xml file (located in the *migrator* folder under <MigratorInstallDirectory>) contains the count-enabled attribute that executes select count(*) queries by default and calculates the percentage completion (for every 100 records) that is shown in the MigratorCLI command window. 
To improve performance if you have a large number of records, set the attribute to false, which means that you see only the total number of records processed instead of the percentage; for example:

<count enabled="false" />

Note

After you perform this configuration, you can no longer see the percentage of the migration that is finished while DDM is running. To see this value, set count enabled back to true.

To migrate data

Use the Delta Data Migration Tool to migrate data from the production server (the source server) to the staging server (the destination server) as follows:

  1. Go to the <MigratorInstallDirectory>\DeltaDataMigration folder.

  2. Double-click the DeltaMigration.exe file to open the Delta Migrations window.

  3. Click the button next to the Source Server field to open the Server dialog box.

  4. On the Server dialog box, complete the following fields, and then click OK.

    • Source Server — The name of the source server name (the production server)
    • User Name — The user name of the source and destination servers (same for both the servers)
    • Password — The password of the source and destination servers (same for both servers)
    • TCP Port — The default value used by the script. If no port is specified, the default is 0.
    • Fast/List Port — You can change the default value of 390635.
  5. Click the button next to the Destination Server field to open the Server dialog box.

  6. Enter the destination server (staging server) information, and click OK.
    The Delta Data Migration tool validates the versions on your source and destination servers. It provides a list of all supported BMC Remedy AR System products and applications. Applications shown in red indicate that an appropriate package was not found or is not applicable for your server.

    After you click the Migrate or Compare button, the DeltaMigration.log file is created and includes information about the source and destination servers, the products you selected, date parameters, and the option that you selected (Migrate or Compare). You can find this file in the same location from which you ran the .exe file for the Delta Data Migration Tool.

    Note

    The destination server data will probably not be consistent until all the data up to the current time is migrated. You can migrate the data in one or more "chunks" (using the Start Date and End Date fields in the Delta Data Migration Tool to specify the range of data to migrate). 
    To ensure that the destination server data is consistent, enter an empty date range (which means the current time stamp) in the End Date field to migrate the final chunk of data.

  7. Ensure that the Re-run applications with previous criteria & instructions check box is selected.

    This check box is selected by default and should remain selected even if you are re-running the migration after fixing any data issues.

    Note

    If you are using the multi-run approach to migrate to minimize your downtime, clear the Re-run applications with previous criteria & instructions check box after confirming that the previous DDM is error free and has successfully completed.
    At this point, DDM will migrate based on the new date and selection criteria that you have specified. If the previous DDM had errors, then fix the errors and run the DDM again with the Re-run applications with previous criteria & instructions check box selected.
    The DDM will then be based solely on the time stamp.

  8. Select all applications that are not shown in red.

  9.  In the Fetch Data/Objects Created/Modified After Date fields, use the Start Date and End Date fields to enter a range of dates (so that you can migrate a "chunk" of data).
    The dates allow you to migrate only those records that were modified or created in that date range. If you are not migrating custom forms data, you can clear the Custom selection in the application name list.

    1. For Start Date, enter the time from when you want to transfer the data.
      Data in the forms that are later than or same as this time stamp are migrated.

      Note

      • To account for Daylight Saving Time, enter enter the Start Date and End Date with a time stamp that is greater than midnight (for example, 1:00:00 AM).
      • If this is the first time you are running the migration, the time stamp that applies is when the production server backup was used to create the staging server. If this is a multiple-run scenario, the time stamp that applies is when you initiated the previous run.
    2. For End Date, enter the date with the time stamp to when you want to transfer the data (for example,12/20/2012 1:00:00 AM).
      You can run the migration multiple times, as needed, to finish the DDM. For the final migration, do not enter an end date.
  10. When you perform the final delta data migration, select Data count validation to generate a report.
    This field (not selected by default) validates the data count from the source and the destination servers and ensures that the counts match.

  11. When you finish the DDM, navigate to the Working\Logs folder (by default, <MigratorInstallDirectory>\DeltaDataMigration\Working\Logs) to review the Count_statistics.csv file. The report lists:

    • Source form name
    • Destination form name
    • Qualification
    • Source record count
    • Destination record count
    • Semicolon-separated string that lists the errors information with unique index field values for entries that were not migrated from source server due to the errors

    Note

    If you see errors in the report, see Reviewing migration results and resolving issues to fix them.

  12. Make one of the following selections, and then click Yes to continue with the migration or comparison.

    • Migrate — To start the data migration.
      All delta data is transferred from the source server to the destination server.
    • Compare — To create a comparison result report.
      This report can be used to identify all data that has been created or updated in the source server during the delta time period. The comparison script generates an .xml result file for each instruction xml file with the instruction name and suffix _Compare; for example: Remedy_Service_Request_Management_Compare.xml
      The script generates a compare .xml result file for each instruction .xml file. These files include all data entries that are either different (records updated in the source server during the delta period) or missing (records created in the source server during the delta period) in the destination server.
      The Delta Data Migration window appears, showing the parameters that will be used by the Migrator.
  13. One command window is launched for each application you are running. The windows close automatically when the process is completed or an error occurs.

    If you click No, the migration or comparison is cancelled.

    Note

    If you want to re-run the migration or the comparison, you must wait for all of the command prompt windows to close before executing a new run.

    The command output is available as an HTML log file.

Note

If you see errors in the report, see Reviewing migration results and resolving issues to fix them.

Was this page helpful? Yes No Submitting... Thank you

Comments