Online migration for Rational Quality Manager

Starting in IBM® Rational® Quality Manager 4.0.6, when you upgrade, you can migrate data to the new version while the old production server is still online.

This data migration method is called online migration. If your database contains a large amount of data, online migration reduces server downtime by running a few of the database migration tasks while the old server remains active.

Important:

Before you proceed with online migration, read this entire topic.

When to run an online migration

A fully offline migration is the preferred migration method because it is easier to recover from migration errors. If a problem occurs during fully offline migration, the database can be returned to the pre-migration state by restoring the snapshot that administrators take before the migration.
Attention:

Because online migration updates are made against a live server, the database cannot be restored to the current state of the data. If an unrecoverable error occurs during online migration, the database might need to be restored to a previous snapshot. As a result, any data that was created since the online migration was started is lost.

To determine whether to run an online migration for your repository, run the repotools -onlineMigrateEstimate command. That command retrieves the number of item states that the online migration command must process. The results are provided without altering the database schema.

The output from the repotools -onlineMigrateEstimate command shows a list of old item types to be processed and the number of states for each type. For general guidelines on the number of states that warrant online migration, see Rational Quality Manager online migration test matrix on the Deployment wiki.

Repository tools command to revert an online migration

If you need to return the state of the database to the point where online migration can be restarted from the beginning, you can run the repotools -onlineMigrateRevert command. That command removes partially migrated data that resulted from running the migration command.

Important:
  • For the command to complete successfully, you must specify an absolute path to the pre-upgrade location of the teamserver.properties file on the old server. For details, see "Repository tools command to revert an online migration" in the Information Center.
  • The repotools -onlineMigrateRevert command does not fully restore the database to its original condition. The schemas, such as new tables, indexes, and the contents of JAZZ.TABLE_MAP and JAZZ.PACKAGE_MAP, are not restored.

Online migration process overview

The high-level steps for running an online migration are as follows. For detailed steps, see the Interactive upgrade guide.
  1. To improve performance, run statistics to update the database table indexes.
  2. Determine whether to run online migration for your repository. Run the migration estimation command and then check the test results data table for guidance on the results.

    To view the testing matrix, see Rational Quality Manager online migration test matrix on the Deployment wiki.

  3. Install, but do not start, the new server.
  4. Start the online migration by entering the repotools migration command.
  5. Wait for the online migration to complete. If needed, you can cancel the migration at any time by typing repotools -onlineMigrateStop.
  6. Complete an offline migration by typing repotools -addTables. That command finishes any remaining online work. If you did not run an online migration, the command processes all of the migration work.


Have a problem or a question? Post it in the Jazz.net forum.